On Sun, 17 Jul 2011 19:19:59 -0700
Brett Cannon br...@python.org wrote:
Just so people know, I went ahead and fixed this for 3.3 (but not for
3.2 since it changes the API in a subtle way).
Yeah, but that shouldn't break anything.
Anyway, thanks a lot for your help, I'm happy it's in 3.3.
On Wed, Jul 20, 2011 at 23:05, lekmalek lekma...@gmail.com wrote:
On Sun, 17 Jul 2011 19:19:59 -0700
Brett Cannon br...@python.org wrote:
Just so people know, I went ahead and fixed this for 3.3 (but not for
3.2 since it changes the API in a subtle way).
Yeah, but that shouldn't break
On 7/21/2011 2:15 PM, Brett Cannon wrote:
It won't break any _existing_ code, but it could cause compatibility for
_future_ code. Imagine I wrote some code for 3.2.2 where this change was
backported and worked *only* with this fix. That would mean my code
would fail in any Python 3.2.1 or
Just so people know, I went ahead and fixed this for 3.3 (but not for 3.2
since it changes the API in a subtle way).
On Sat, Jul 16, 2011 at 01:33, lekmalek lekma...@gmail.com wrote:
Hello all,
Can any of you core devs have a look at
http://bugs.python.org/issue10271. It seems Brett is
Hello all,
Can any of you core devs have a look at
http://bugs.python.org/issue10271. It seems Brett is really busy right
now and this uncontroversial (AFAICT) one liner only needs someone to
review it and commit it. The pb is, it's holding me back a little bit,
and I really would like to have it
