From: <Ar...@co...> - 2007-03-16 21:34:53
|
> > P.S.: I know this is quite a political issue, but is there a chance to > > change from tabs to spaces in Webware code? > > I think this question should go directly to Chuck, our BDFL who had been > strongly against this in the past. I vote for a change as well. > > -- Christoph What if you stayed with tabs and then added a converter, so that you can quickly convert the tabs to the number of spaces that you want? In fact, this might be a good idea for a lot of free source Python projects distributed on the web -- though I would suspect it would be better to use tabs as the default and offer the ability to convert to space because sometimes it's possible it might not look quite right converting a project coded for spaces to tabs. |
From: Jeremy K. <jk...@st...> - 2007-03-19 00:27:08
|
This is good stuff. Any idea when a 0.9.3 version will be available for use? I'd like to sneak this into my current schedule, but need to plan for managing risk, etc. jd -----Original Message----- From: web...@li... [mailto:web...@li...] On Behalf Of Christoph Zwerschke Sent: Friday, March 16, 2007 7:25 PM To: Discussion of Webware for Python including feedback and proposals. Subject: Re: [Webware-discuss] Possible bug? Stephan Diehl wrote: > catching the Error in ThreadedAppServer (as in your suggestion) does=20 > not supress the Traceback. It looks like the Traceback is generated in > Application.py within the 'handleExceptionInTransaction'. > For my special case it's probably best, to put my response.write=20 > inside some try/except. You're right, that did not suffice. It worked only for pages < 8192 bytes, and the the transaction resources were not closed properly. I have now checked in a much cleaner and complete fix. -- Christoph ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Webware-discuss mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Christoph Z. <ci...@on...> - 2007-03-19 00:53:02
|
Jeremy Kaplan wrote: > This is good stuff. Any idea when a 0.9.3 version will be available > for use? I'd like to sneak this into my current schedule, but need to > plan for managing risk, etc. There are still some issue on my list for the release, but I'm up to do it very soon, maybe next weekend. And I think we'll skip a beta version this time. I also though about, if that version turns out to be stable, we should publish a 1.0 version. I had planned to make some fundamental changes before 1.0, but now I think, maybe we should publish the 1.0 first, and then make the big changes in a new 1.1 or 2.0 branch. So contrary to the usual software practice, we would have a stable 1.0 ;-) One of the larger changes I had in mind was requiring Python 2.3 or 2.4 (currently Webware is backward compatible down to Python 2.0!) and then getting rid of a lot of workarounds and ballast and suboptimal code. But this will also bring in new instability, so now I think this should be done after version 1.0. Your thoughts? -- Chris |
From: Chuck E. <chu...@gm...> - 2007-03-19 15:54:57
|
On 3/18/07, Christoph Zwerschke <ci...@on...> wrote: > Jeremy Kaplan wrote: > > This is good stuff. Any idea when a 0.9.3 version will be available > > for use? I'd like to sneak this into my current schedule, but need to > > plan for managing risk, etc. > > There are still some issue on my list for the release, but I'm up to do > it very soon, maybe next weekend. And I think we'll skip a beta version > this time. > > I also though about, if that version turns out to be stable, we should > publish a 1.0 version. I had planned to make some fundamental changes > before 1.0, but now I think, maybe we should publish the 1.0 first, and > then make the big changes in a new 1.1 or 2.0 branch. So contrary to the > usual software practice, we would have a stable 1.0 ;-) > > One of the larger changes I had in mind was requiring Python 2.3 or 2.4 > (currently Webware is backward compatible down to Python 2.0!) and then > getting rid of a lot of workarounds and ballast and suboptimal code. But > this will also bring in new instability, so now I think this should be > done after version 1.0. Your thoughts? Agreed with all. -Chuck |
From: Christoph Z. <ci...@on...> - 2007-03-17 00:33:08
|
Ar...@co... wrote: > What if you stayed with tabs and then added a converter, so that you > can quickly convert the tabs to the number of spaces that you want? That would get us into a mess when people send in patches etc. I'd prefer to make the transition to spaces; which I think has become the de-facto standard. Maybe we can do that by the mercy of our BDFL together with the change of the required Python version (2.3 or 2.4). But that will not happen in 0.9.3 which will be merely a bugfix release. -- Christoph |