The tests prove that r85874 does not break the build.
On Fri, Oct 29, 2010 at 12:49 AM, Éric Araujo mer...@netwok.org wrote:
Le 28/10/2010 22:52, anatoly techtonik a écrit :
Can anybody summarize the outcome?
Is it that renaming BadZipfile to BadZipFile with backward compatible
alias and
Can anybody summarize the outcome?
Is it that renaming BadZipfile to BadZipFile with backward compatible
alias and deprecation note breaks something?
--
anatoly t.
___
Python-Dev mailing list
Python-Dev@python.org
From: *Boštjan Mejak* bostjan.me...@gmail.com
Since Python 3.2 accepts feature requests, take this fix as a feature
request. Please forget about preserving the compatibility with old pickles.
You can reopen #7351 as a feature request for 3.2. A serious proposal
has to take compatibility into
Hello
[Sorry if this comes twice, connection errors here]
(A bit of context: The original message comes from bug #2775, “Implement
PEP 3108”, a meta-bug tracking stdlib reorganization for py3k.)
I am very glad you're reorganizing the Standard Library. Thumbs up! I
hope everything will comply
On Mon, Oct 18, 2010 at 10:45 PM, Éric Araujo mer...@netwok.org wrote:
(A note about PEP 8 compliance: Module names have been mostly fixed, but
not all function/method names, for example in logging and unittest. If
I recall correctly, readability did not seem to make all the rewrites
worth
Hello
(A bit of context: The original message comes from bug #2775, “Implement
PEP 3108”, a meta-bug tracking stdlib reorganization for py3k.)
I am very glad you're reorganizing the Standard Library. Thumbs up! I
hope everything will comply to PEP 8 after you're done.
You may have missed the
I am very glad you're reorganizing the Standard Library. Thumbs up! I
hope everything will comply to PEP 8 after you're done.
Since you're reorganizing, I have my own contribution. I have attached
a patch. The issue7351 http://bugs.python.org/issue7351 was not
accepted at the time, so I hope
