Woops. In case, you were wondering, here are the rel notes:
- 0.6.1 changes
All bug fixes:
- WebKit
- "File" is the new default session store, since "Dynamic" has
concurrency issues.
- The webkit unix init script
- now works
I'm just going to cut this out of HEAD since only 0.6.1 changes exist
there. I should have 0.6.1b1 out tonight. Since the changes are
minimal, I'll cut the final probably 48 hours later.
-Chuck
___
Webware-devel mailing list
[EMAIL PROTECTED]
https:
On Sunday 09 December 2001 17:45, Chuck Esterbrook wrote:
> On Sunday 09 December 2001 02:54 pm, Tavis Rudd wrote:
> > 1) require the first LINE (not parag.) to be a synopsis of the
> > method.
>
> Won't this violate the margin? eg, my first line descriptions will
> sometimes exceed column 79.
I
On Sunday 09 December 2001 02:54 pm, Tavis Rudd wrote:
> 1) require the first LINE (not parag.) to be a synopsis of the
> method.
Won't this violate the margin? eg, my first line descriptions will
sometimes exceed column 79.
Is there a special reason to break after the first sentence? I know
p
On Sunday 09 December 2001 02:40 pm, Tavis Rudd wrote:
> I'd forgotten about that pystats module, but I was planning to use
> checksrc.
>
> > Regarding new components, I was planning on making an EmptyKit that
> > people could just duplicate and then fill out.
>
> Same idea, but I'd like to made t
Hi,
I think we should update the existing Style Guidelines and
incorporate them into a Developers' Guide document (on the Wiki to
start with).
The Developers Guide would:
* provide a brief history of development
* provide a philosophical perspective
* provide a methodology (emphasizin
On Sun, 2001-12-09 at 15:18, Chuck Esterbrook wrote:
> On Sunday 09 December 2001 02:24 pm, Tavis Rudd wrote:
> > On Sunday 09 December 2001 12:58, Chuck Esterbrook wrote:
> > > I wish editors would pick up a .foorc in the directory of the
> > > edited file. This would pay off much larger.
> >
> >
On Sun, Dec 09, 2001 at 02:54:22PM -0800, Tavis Rudd wrote:
> def foo(self):
> """
> Returns foo
>
> More detailed info ...
> """
There's also the three-more-spaces convention:
def foo(self):
"""First line...
Second line...
Third line.
Looks good. I like the 'first word is verb' bit and like how you
capitalize the synopsis.
Two things I'd change:
1) require the first LINE (not parag.) to be a synopsis of the method.
2) suggest, rather than require, that the """ be on a line by itself.
Emacs will automatically suck out the n
On Sunday 09 December 2001 13:17, Chuck Esterbrook wrote:
> I'm totally against cluttering up the main source directory with
> all the test files. As with examples, docs, admin, etc. they should
> just go in their own folder. (Frankly, I'd prefer if Python
> packages also had Code/ and ByteCode/ b
On Sunday 09 December 2001 13:24, Chuck Esterbrook wrote:
> On Sunday 09 December 2001 02:28 pm, Tavis Rudd wrote:
> > Do you think such a tool would be worthwhile? Each command would
> > be implemented as separate class that parses its own options and
> > args, etc. The main script would just d
On Sunday 09 December 2001 02:28 pm, Tavis Rudd wrote:
> Do you think such a tool would be worthwhile? Each command would be
> implemented as separate class that parses its own options and args,
> etc. The main script would just dispatch the commands.
Sure. Please visit Webware's bin/checksrc.p
This is my proposal:
Quick example:
def foo(self):
"""
Returns foo.
"""
pass
Mutiple paragraphs & word wrapping example:
def foo(self):
"""
Python isn't perfect, but it's
On Sunday 09 December 2001 02:24 pm, Tavis Rudd wrote:
> On Sunday 09 December 2001 12:58, Chuck Esterbrook wrote:
> > I wish editors would pick up a .foorc in the directory of the
> > edited file. This would pay off much larger.
>
> I wish we had an extensible editor written in Python and Qt. Th
On Sunday 09 December 2001 12:47, you wrote:
> I wasn't aware of this. We're not supposed to be mixing tabs and
> spaces at all. I'll run checksrc.py soon and at least fix that.
BTW, I've started working on a little command line tool, called
"/usr/bin/webware" for the time-being, that will give
On Sunday 09 December 2001 02:13 pm, Tavis Rudd wrote:
> Hi,
> the folks over at the PyScons project have a guideline 'requiring'
> that every single module in their codebase be accompanied by
> Tests.py that explicitly tests all functionality in that
> module.
>
> I'd like to propose that we incl
On Sunday 09 December 2001 12:58, Chuck Esterbrook wrote:
> I wish editors would pick up a .foorc in the directory of the
> edited file. This would pay off much larger.
I wish we had an extensible editor written in Python and Qt. Then
we'd just be able to configure to our hearts extent! With Q
Hi,
the folks over at the PyScons project have a guideline 'requiring'
that every single module in their codebase be accompanied by
Tests.py that explicitly tests all functionality in that
module.
I'd like to propose that we include 'request' in the Webware
guidelines that all modules that
On Sunday 09 December 2001 12:42 pm, Mike Orr wrote:
> Regarding tabs vs spaces, I don't know, there's no one ideal answer.
> Universal compatibility argues for using tabs--that is what the tab
> key and \t are for anyway---with tabstops at 8 columns. On the other
> hand, this encourages mixing t
On Saturday 08 December 2001 12:27 pm, Clark C . Evans wrote:
> So. If you set your tab-stop every 4 columns, it
> can cause you no end of grief. Some of the
> recent webware code i've used relies on above
> rules..., there are numerous "\n \t" lines.
> If you do a tab expansion
On Sunday 09 December 2001 12:21, Chuck Esterbrook wrote:
> On Sunday 09 December 2001 01:11 pm, Tavis Rudd wrote:
> > Chuck,
> > I'd be happy to go with 90, or even 100, as a standard maximum
> > line width for Webware so we can end this debate and get back to
> > more productive things. Either
On Sun, Dec 09, 2001 at 11:00:11AM -0800, Chuck Esterbrook wrote:
> Also, instead of changing how I code in Python, shouldn't editors like
> emacs do the right thing? Python is the first language I've used where
> I was expected to cater to a single editor (and one with source)
> instead of exp
On Sunday 09 December 2001 08:17 am, Darryl VanDorp wrote:
> There was a previous message about the link to
> Webware v.5 on the webware site. It's the right hand
> Side where it gives a little description of webware
> Then points to v.5 download.
>
> Regards,
> Darryl
Thanks! I always flip bits
On Sunday 09 December 2001 01:11 pm, Tavis Rudd wrote:
> Chuck,
> I'd be happy to go with 90, or even 100, as a standard maximum line
> width for Webware so we can end this debate and get back to more
> productive things. Either would be better than the no-wrapping
> situation in the current code
Chuck,
I'd be happy to go with 90, or even 100, as a standard maximum line
width for Webware so we can end this debate and get back to more
productive things. Either would be better than the no-wrapping
situation in the current codebase.
Tavis
__
On Sun, 2001-12-09 at 13:00, Chuck Esterbrook wrote:
> Scaling everything down to the most extreme people (the guy using an 80
> column terminal who prints and e-mails all of his code) hurts for those
> who aren't (those with the space, the friendly editor and the
> inclination to use them). Wh
---> I'd be happy to settle for 90 columns.
On Sunday 09 December 2001 11:28, Chuck Esterbrook wrote:
> On Sunday 09 December 2001 11:57 am, Tavis Rudd wrote:
> > On Sunday 09 December 2001 08:13, Chuck Esterbrook wrote:
> > > On Saturday 08 December 2001 12:16 pm, Tavis Rudd wrote:
> > > > Th
On Sunday 09 December 2001 11:57 am, Tavis Rudd wrote:
> On Sunday 09 December 2001 08:13, Chuck Esterbrook wrote:
> > On Saturday 08 December 2001 12:16 pm, Tavis Rudd wrote:
> > > That's the whole point, many tools are designed on this
> > > assumption and have dockbars down the left side or use
On Sunday 09 December 2001 10:36 am, Ian Bicking wrote:
> And why should I? And not just me, but everyone else? There's
> *nothing wrong* with standard Python conventions! Why can't we just
> use those?
>
> I am going to keep writing my code pretty much to Python coding
> standards, because I t
On Sunday 09 December 2001 08:13, Chuck Esterbrook wrote:
> On Saturday 08 December 2001 12:16 pm, Tavis Rudd wrote:
> > That's the whole point, many tools are designed on this
> > assumption and have dockbars down the left side or use multiple
> > vertical frames. 80 might be a bit zealous, but c
On Sun, 2001-12-09 at 10:13, Chuck Esterbrook wrote:
> In general, I'm not seeing that tools are designed around the
> assumption that text files stop at 80 columns.
>
> In all three products, sizing the window to be wide enough for 130
> characters actually felt excessive to me, but 110-120 fe
There was a previous message about the link to
Webware v.5 on the webware site. It's the right hand
Side where it gives a little description of webware
Then points to v.5 download.
Regards,
Darryl
___
Webware-devel mailing list
[EMAIL PROTECTED]
h
On Saturday 08 December 2001 10:03 am, Ian Bicking wrote:
> tell that there were semantic differences in some instances. In the
> case of Emacs, wrapped lines get cut off at exactly 80 (or whatever
> width your window is), without any attention to word boundaries. I
> imagine lots of editors are
On Saturday 08 December 2001 06:07 am, Geoffrey Talvola wrote:
> On Friday December 07, 2001 04:43 pm, Chuck Esterbrook wrote:
> > On Thursday 06 December 2001 12:04 pm, Love, Jay wrote:
> > > From memory, with cgi, if there is a location header, a redirect
> > > is assumed. With mod_webkit, you n
34 matches
Mail list logo
