rest2web-develop

RE: [Rest2web-develop] Docs revision, "length" removal

[Michael F. <mi...@pc...>]

Hello Nicola,


-----Original Message-----
   >From: "Nicola Larosa"<ni...@te...>
   >Sent: 21/08/05 09:57:04
   >To: "res...@li..."<res...@li...>
   >Subject: [Rest2web-develop] Docs revision, "length" removal
     >Completed revising configobj.txt, committed it in two steps: in the first
   >one there's only trailing spaces removal, the real changes are in the

The docutils spec. Seemed to indicate that a trailing (or leading) space was needed where you break a line. I freely admit to not having tested this of course !

   >second one. This way it may be easier reviewing the changes. Now I'm
   >looking at validate.txt .
   >

Great - are you making big changes ?

I made a few changes myself - but they should be easy enough to merge.

Nice one - thanks.

As I mention in my other email - I've been working on the other pythonutils modules and their docs.

   >I'd like to remove the "length" argument for lists (and strings). It's
   >redundant (one may set "min" and "max" to the same value), and probably it
   >isn't used often to warrant special-casing it.
   >
   >Moreover, it prevents being able to write "list(1)" or "list(1,4)", forcing
   >explicit specification: "list(min=1)", "list(min=1, max=4)", and making it
   >incoherent with "integer" check definition.
   >
   >What do you think?
   >

Ok - fine with me. Just do appropriate changes in docstrings/docs. I'm sure you would have anyway.

All the Best,

Fuzzyman 
http://www.voidspace.org.uk/python 

   >-- 
   >Nicola Larosa - ni...@te...
   >
   >PHP is such a load of crap, right down to the standard library, that it
   >creates a culture where it's acceptable to write horrible code. [...]
   >Maybe with PHP 5 they are trying to clean up the neighborhood, but that
   >doesn't change the fact when you program in PHP you are programming in
   >a dump. -- Ian Bicking, July 2005
   >
   >
   >
   >   >

[Message truncated. Tap Edit->Mark for Download to get remaining portion.]

Re: [Rest2web-develop] Docs revision, "length" removal

[Michael F. <mi...@pc...>]

Hello Nicola (and others),

-----Original Message-----
   >From: "Nicola Larosa"<ni...@te...>
   >Sent: 21/08/05 11:08:39
   >To: "res...@li..."<res...@li...>
   >Subject: Re: [Rest2web-develop] Docs revision, "length" removal
   >
   >>> Completed revising configobj.txt, committed it in two steps: in the first
   >>> one there's only trailing spaces removal, the real changes are in the
   >
   >> The docutils spec. seemed to indicate that a trailing (or leading) space
   >> was needed where you break a line. I freely admit to not having tested
   >> this of course !
   >
   >Mmh... I don't remember reading anything of the sort. Docutils seems to
   >like these files just fine. The trailing spaces removal is done
   >automatically by the Kate editor, and is rather handy, since I don't
   >maintain on docs the same, rather nutty, level of white space control I do
   >on code. :-)
   >
There has been a very recent debate on the 'docutils-users' list about this. Where long lines (paragraphs) are broken by newlines - adding an implicit space is wrong for character sets (like the Chinese ones) that *don't* use spaces to separate words.

David Goodger (docutils lead) thought that docutils didn't and shouldn't add an implicit space.

I believed him without testing - hence the multitude of single trailing spaces.

(Oh, by the way - apparently O'Reilly are bringing out a book on Twisted. I saw via a Daily-Python post).

   >
[snip...]
   >> As I mention in my other email - I've been working on the other
   >> pythonutils modules and their docs.
   >
   >Not enough time to work on those too, at the moment. :-(
   >

No - problem didn't expect your help on this.

   >
   >>> What do you think?
   >
   >> Ok - fine with me. Just do appropriate changes in docstrings/docs. I'm
   >> sure you would have anyway.
   >
   >Of course. Made the changes to code, docstrings and docs, and committed:
   >"length" is no more. :-) I also removed a leftover caseless import in
   >__init__.py . (Those "from ... import *" are ugly!)
   >

I'm implementing __all__ in all the sub-modules. They're there so you can import directly from the ``pythonutils`` namespace.

   >ConfigObj and validate are now ready to be moved back into the trunk, docs
   >included, and to be released, as soon as you're satisfied with the rest of
   >pythonutils, if you prefer releasing them together. I'd separate them,
   >though, I think ConfigObj deserves autonomous distribution.
   >

Yes - I'll package ConfigObj and validate for release ASAP. 

I'm working towards a Pythonutils release as soon after that as possible.

I'd rather be able to move the pythonutils stuff in one go. Really it ought to be in it's own repository.

Maybe I ought to look at setting up subversion and trac :-)

   >BTW, validate.py in the branch is long more than double the one in the
   >trunk, because of all those doctests. Instead, configobj.py in the branch
   >is *shorter* than the one in the trunk (v.3), *despite* all the added
   >doctests, which is remarkable. :-)
   >

Yeah - it's very good. Cutting out ``writein`` helped - but the core parser in version 3 was character by character, so pretty heavy duty.

Best Regards, 


Fuzzyman 
http://www.voidspace.org.uk/python 

   >-- 
   >Nicola Larosa - ni...@te...
   >
   >PHP is such a load of crap, right down to the standard library, that it
   >creates a culture where it's acceptable to write horrible code. [...]
   >Maybe with PHP 5 they are trying to clean up the neighborhood, but that
   >doesn't change the fact when you program in PHP you are programming in
   >a dump. -- Ian Bicking, July 2005
   >
   >
   >
   >-------------------------------------------------------
   >SF.Net email is Sponsored by the Better Software Conference & EXPO
   >September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
   >Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
   >Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
   >_______________________________________________
   >Rest2web-develop mailing list
   >Res...@li...
   >https://lists.sourceforge.net/lists/listinfo/rest2web-develop
   >
   >

Re: [Rest2web-develop] Docs revision, "length" removal

[Nicola L. <ni...@te...>]

>>> The docutils spec. seemed to indicate that a trailing (or leading) space
>>> was needed where you break a line. I freely admit to not having tested
>>> this of course !

>> Mmh... I don't remember reading anything of the sort. Docutils seems to
>> like these files just fine. The trailing spaces removal is done
>> automatically by the Kate editor, and is rather handy, since I don't
>> maintain on docs the same, rather nutty, level of white space control I do
>> on code. :-)

> There has been a very recent debate on the 'docutils-users' list about
> this. Where long lines (paragraphs) are broken by newlines - adding an
> implicit space is wrong for character sets (like the Chinese ones) that
> *don't* use spaces to separate words.

Oh, that one, didn't think it was relevant (still don't :-) ).


> David Goodger (docutils lead) thought that docutils didn't and shouldn't
> add an implicit space.

It's well and good.


> I believed him without testing - hence the multitude of single trailing
> spaces.

This is quite a wide jump to conclusions. The spaces docutils does not add
are not needed: HTML converts newlines to spaces anyway.

Didn't you wonder how it could have worked all this time without trailing
spaces? :-)


> (Oh, by the way - apparently O'Reilly are bringing out a book on Twisted.
> I saw via a Daily-Python post).

Yeah, there was an announcement on the Twisted mailing list a few weeks ago.


>> (Those "from ... import *" are ugly!)

> I'm implementing __all__ in all the sub-modules. They're there so you can
> import directly from the ``pythonutils`` namespace.

Oh yes, one of the few legitimate uses of it Silly me. :-)


>> ConfigObj and validate are now ready to be moved back into the trunk, docs
>> included, and to be released, as soon as you're satisfied with the rest of
>> pythonutils, if you prefer releasing them together. I'd separate them,
>> though, I think ConfigObj deserves autonomous distribution.

> Yes - I'll package ConfigObj and validate for release ASAP. 

That's great!


> I'm working towards a Pythonutils release as soon after that as possible.

Will it still include ConfigObj? I suppose not.


> I'd rather be able to move the pythonutils stuff in one go. Really it
> ought to be in it's own repository.

It[no_quote]s ;-) own top directory would be enough.


> Maybe I ought to look at setting up subversion and trac :-)

That's quite a good idea. :-)

-- 
Nicola Larosa - ni...@te...

PHP is such a load of crap, right down to the standard library, that it
creates a culture where it's acceptable to write horrible code. [...]
Maybe with PHP 5 they are trying to clean up the neighborhood, but that
doesn't change the fact when you program in PHP you are programming in
a dump. -- Ian Bicking, July 2005

Re: [Rest2web-develop] Docs revision, "length" removal

[Michael F. <mi...@pc...>]

Nicola Larosa wrote:
[snip..]
> 
>>I believed him without testing - hence the multitude of single trailing
>>spaces.
> 
> 
> This is quite a wide jump to conclusions. The spaces docutils does not add
> are not needed: HTML converts newlines to spaces anyway.
> 
> Didn't you wonder how it could have worked all this time without trailing
> spaces? :-)
> 

Me - no, I tend to use line wrap (wonderful invention ;-)

So docutils maintains the new line in the output HTML ? In which case
the problem that the user reports will still be a problem (despite
docutils) - which no one pointed out in the thread.

[snip..]
> 
>>>ConfigObj and validate are now ready to be moved back into the trunk, docs
>>>included, and to be released, as soon as you're satisfied with the rest of
>>>pythonutils, if you prefer releasing them together. I'd separate them,
>>>though, I think ConfigObj deserves autonomous distribution.
> 
> 
>>Yes - I'll package ConfigObj and validate for release ASAP. 
> 
> 
> That's great!
> 
> 
> 
>>I'm working towards a Pythonutils release as soon after that as possible.
> 
> 
> Will it still include ConfigObj? I suppose not.
> 

Yes - ConfigObj is an 'integral' part of pythonutils.

> 
> 
>>I'd rather be able to move the pythonutils stuff in one go. Really it
>>ought to be in it's own repository.
> 
> 
> It[no_quote]s ;-) own top directory would be enough.
> 

I'll move the whole pythonutils directory into trunk when ready.

No possessive apostrophe (quote ?) -
http://www.voidspace.org.uk/gallery/silly/bobsqu.jpg

;-) ^ 2 ?

> 
> 
>>Maybe I ought to look at setting up subversion and trac :-)
> 
> 
> That's quite a good idea. :-)
> 

Will do, possibly in 'due' course. Would be nice.

Fuzzball
http://www.voidspace.org.uk/python

Re: [Rest2web-develop] Docs revision, "length" removal

[Nicola L. <ni...@te...>]

>> Completed revising configobj.txt, committed it in two steps: in the first
>> one there's only trailing spaces removal, the real changes are in the

> The docutils spec. seemed to indicate that a trailing (or leading) space
> was needed where you break a line. I freely admit to not having tested
> this of course !

Mmh... I don't remember reading anything of the sort. Docutils seems to
like these files just fine. The trailing spaces removal is done
automatically by the Kate editor, and is rather handy, since I don't
maintain on docs the same, rather nutty, level of white space control I do
on code. :-)


>> second one. This way it may be easier reviewing the changes. Now I'm
>> looking at validate.txt .

> Great - are you making big changes ?

Many small changes, mostly.


> I made a few changes myself - but they should be easy enough to merge.
> 
> Nice one - thanks.
> 
> As I mention in my other email - I've been working on the other
> pythonutils modules and their docs.

Not enough time to work on those too, at the moment. :-(


>> What do you think?

> Ok - fine with me. Just do appropriate changes in docstrings/docs. I'm
> sure you would have anyway.

Of course. Made the changes to code, docstrings and docs, and committed:
"length" is no more. :-) I also removed a leftover caseless import in
__init__.py . (Those "from ... import *" are ugly!)

ConfigObj and validate are now ready to be moved back into the trunk, docs
included, and to be released, as soon as you're satisfied with the rest of
pythonutils, if you prefer releasing them together. I'd separate them,
though, I think ConfigObj deserves autonomous distribution.

BTW, validate.py in the branch is long more than double the one in the
trunk, because of all those doctests. Instead, configobj.py in the branch
is *shorter* than the one in the trunk (v.3), *despite* all the added
doctests, which is remarkable. :-)

-- 
Nicola Larosa - ni...@te...

PHP is such a load of crap, right down to the standard library, that it
creates a culture where it's acceptable to write horrible code. [...]
Maybe with PHP 5 they are trying to clean up the neighborhood, but that
doesn't change the fact when you program in PHP you are programming in
a dump. -- Ian Bicking, July 2005