Mailman 3 January 2008 - Python-Dev

Re: [Python-Dev] Contributing to Python
by Arash Ferdowsi 04 Jan '08

04 Jan '08

how about that py 2.5.2 release. anybody? =D On Jan 3, 2008 2:05 PM, Bill Janssen <janssen(a)parc.com> wrote: > > > 3.x fixes, because there's no schedule for 2.6. > > > > Eh? PEP 3000 has a schedule that includes 2.6: > > OK, no schedule that I knew about :-). I'll get back to work on it. > > Bill > > _______________________________________________ > Python-Dev mailing list > Python-Dev(a)python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/arashf%40mit.edu > -- Arash Ferdowsi CTO, Dropbox 913.707.5875 (m)

1 0

Re: [Python-Dev] Contributing to Python
by Guido van Rossum 04 Jan '08

04 Jan '08

On Jan 3, 2008 12:17 PM, Bill Janssen <janssen(a)parc.com> wrote: > > My main gripe is with code contributions to Py3k and 2.6; Py3k is > > mostly done by a handful of people, and almost nobody is working much > > on 2.6. > > There's a great Duke Ellington quote: ``Without a deadline, baby, I > wouldn't do nothing.'' > > The SSL code in 2.6 is out-of-date (buggy) compared to the code in the > 3.x branch, for instance. I just haven't prioritized backporting the > 3.x fixes, because there's no schedule for 2.6. Eh? PEP 3000 has a schedule that includes 2.6: * August 2007: release 3.0a1. * December 2007: release 3.0a2. * Early 2007 (pre-PyCon): release 2.6a1. * May 2008 (post-PyCon): full feature freeze for 3.0 and 2.6. * July 2008: release 2.6 (final). * August 2008: release 3.0 (final). -- --Guido van Rossum (home page: http://www.python.org/~guido/)

2 1

Re: [Python-Dev] Return type of round, floor, and ceil in 2.6
by Raymond Hettinger 04 Jan '08

04 Jan '08

[GvR] > We're thin on contributors as it is (have you noticed > how few people are submitting anything at all lately?). The people who are contributing are doing a nice job. Also, it was nice that the change was discussed on the list. > 2.6 should be extremely compatible with 2.5 by default. Good to hear that is still a primary goal. Along the way, I worried that that sentiment had been lost and that little incompatibilities were sneaking in (iirc, the proposed transition plan for leading zeroes was headed down this path). > The incentive for upgrading will be "you can reach 3.0 > easier via 2.6" and perhaps "the latest version of 3rd > party software X runs best on 2.6". Does the 2to3 tool work from 2.5 or from 2.6 or does it make difference? If it works from 2.5, I'm thinking my company will make the jump all at once (after the 3.x series stabilizes, gets optimized, and key third-party packages have been migrated). I'm also expecting that some chuck of users will be left in the 2.x world and that they would like highest version to be as clean as possible (with migration features going into the category of things that don't provide them any benefit). > Right now, in the trunk, math.float(1) returns 1, > where it should return 1.0 for compatibility with 2.5. > Jeffrey, can you fix this and similar incompatibilities > you introduced? Thanks for zapping this. Raymond

3 2

Re: [Python-Dev] Syntax suggestion for imports
by Terry Jones 03 Jan '08

03 Jan '08

>>>>> "John" == John Barham <jbarham(a)gmail.com> writes: >> * import readline or emptymodule John> This I find more problematic as "emptymodule" seems too magical. John> Even now any code that wants to use a module that might not have been John> successfully imported needs to check if that's the case. E.g., a John> fuller current use-case would be: John> try: John> readline = None John> import readline John> except ImportError: John> pass John> if readline is not None: John> readline.foo() John> Conceivably emptymodule could act as a Null object but that could John> create more problems than it solves. How about import readline or None as readline This is just for cases where you don't want to trigger ImportException on import and do want the symbol set to None for later testing. A standalone "import None" could have no effect. Terry

1 0

Tkinter problems with Tcl/Tk 8.5
by George Peter Staplin 02 Jan '08

02 Jan '08

Hello, I am a Tcl/Tk core developer. I'm trying to resolve some bugs that have surfaced in Tkinter with Tcl/Tk 8.5. 8.5.0 is very near release, and I'm hoping we can determine where the problem is, and resolve it soon. http://sourceforge.net/tracker/index.php?func=detail&aid=1851526&group_id=1… It seems very peculiar how the text widget's bbox is returning a Python-like list and therefore breaking the Tcl callback. I haven't thus far been able to determine which python method is causing that, or if it's something related to the hooks you have added. The same problem doesn't occur with 8.4. It also has been suggested by some on the Tcl core team (during discussions about this bug) that you probably shouldn't be using Tcl_GetObjType and relying on the registered Tcl_ObjTypes, however I'm not sure of a way to get what you need otherwise. Tcl 8.5 now supports big integers, so I think some changes may be needed in _tkinter.c for that. The list internal rep has changed as well, and I'm not sure if that will affect you. Another developer also pointed out that the text widget is returning a Tcl_Obj with a list type, rather than a string for the bbox subcommand, so that could be related to this bug. I hope that we can work together to resolve the issues you may have with Tk. George -- http://www.xmission.com/~georgeps/ http://whim.linuxsys.net http://code.google.com/p/megapkg/ http://code.google.com/p/opennexx/

2 2