On 7/22/2011 4:26 AM, Lars Gustäbel wrote:
On Thu, Jul 21, 2011 at 08:46:05PM -0700, rantingrick wrote:
PS: I will be posting more warts very soon. This stdlib is a gawd
awful mess!
I do not agree. Although I come across one or two odd things myself from time
to time, I think the stdlib as a
On 07/22/2011 03:26 AM, Lars Gustäbel wrote:
On Thu, Jul 21, 2011 at 08:46:05PM -0700, rantingrick wrote:
Tarfile is missing the attribute "fp" and instead exposes a
boolean "closed". This mismatching API is asinine! Both
tarfile and zipfile should behave EXACTLY like file objects
What do you
On 22/07/11 05:46, rantingrick wrote:
> PS: I will be posting more warts very soon. This stdlib is a gawd
> awful mess!
Please don't. Not here.
There's a wonderful bug tracker at python.org. Use that. That's where
this kind of thing belongs. And, please, be concise.
What's the point of shouting
On Thu, Jul 21, 2011 at 08:46:05PM -0700, rantingrick wrote:
> I may have found the mother of all inconsitency warts when comparing
> the zipfile and tarfile modules. Not only are the API's different, but
> the entry and exits are differnet AND zipfile/tarfile do not behave
> like proper file objec
Excerpts from rantingrick's message of Thu Jul 21 23:46:05 -0400 2011:
>
> I may have found the mother of all inconsitency warts when comparing
> the zipfile and tarfile modules. Not only are the API's different, but
> the entry and exits are differnet AND zipfile/tarfile do not behave
> like prop
