Mailman 3 October 2009 - Python-Dev

Initialization of __builtins__
by Vinay Sajip Oct. 10, 2009

Oct. 10, 2009

>I'm not top-posting, but gmane is giving me a hard time :-( In the py3k branch, logging has the line _unicode = 'unicode' in dir(__builtins__) to determine the existence of Unicode support. The code in trunk, being 1.5.2 compatible, used hasattr(types, 'UnicodeType') I wanted to eliminate the types import and modernise the trunk code a bit, so I copied the py3k line to the trunk version of logging. It didn't work as expected! So I added the line print dir(__builtins__) in logging … [View More]

4 4

transitioning from % to {} formatting
by Steven Bethard Oct. 10, 2009

Oct. 10, 2009

There's a lot of code already out there (in the standard library and other places) that uses %-style formatting, when in Python 3.0 we should be encouraging {}-style formatting. We should really provide some sort of transition plan. Consider an example from the logging docs: logging.Formatter("%(asctime)s - %(name)s - %(levelname)s - %(message)s") We'd like to support both this style as well as the following style: logging.Formatter("{asctime} - {name} - {levelname} - {message}") Perhaps we'… [View More]

26 131

Re: [Python-Dev] eggs now mandatory for pypi?
by Senthil Kumaran Oct. 10, 2009

Oct. 10, 2009

On Mon, Oct 05, 2009 at 10:43:22AM +0200, Fredrik Lundh wrote: > it's revews like this that makes me wonder if releasing open source is > a good idea: > no egg - worst seen ever, remove it from pypi or provide an egg > (jensens, 2009-10-05, 0 points) > Greetings effbot. :) As you might already know, "eggs" are not mandatory for pypi. No where in the documentation it mentions so. Also many good packages in pypi are not eggs (MaL's egenix packages for e.g) and we have known … [View More]

9 29

Re: [Python-Dev] a new setuptools release?
by P.J. Eby Oct. 9, 2009

Oct. 9, 2009

At 12:16 PM 10/6/2009 -0700, Guido van Rossum wrote: >I think at this point the community should not be forced wait for you >to get a new supply of round tuits. The wait has been too long >already. You can stay on in an advisory role, but I don't think it's >reasonable to block development or decisions until you have time. Tarek didn't think so either, which is why he created a fork, called Distribute. So I'm not really clear on what you're trying to say here (or in the rest of … [View More]

9 11

Howto handle multilib conflict?
by Neal Becker Oct. 9, 2009

Oct. 9, 2009

Just received: https://bugzilla.redhat.com/show_bug.cgi?id=528237 yum install libotf-devel.i586 libotf-devel.x86_64 yields: Transaction Check Error: file /usr/bin/libotf-config from install of libotf-devel-0.9.8-2.fc11.i586 conflicts with file from package libotf-devel-0.9.8-2.fc11.x86_64 file /usr/share/doc/libotf-devel-0.9.8/example/Makefile from install of libotf-devel-0.9.8-2.fc11.i586 conflicts with file from package libotf-devel-0.9.8-2.fc11.x86_64 What is the recommended way to resolve this?

1 1

Summary of Python tracker Issues
by Python tracker Oct. 9, 2009

Oct. 9, 2009

ACTIVITY SUMMARY (10/02/09 - 10/09/09) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 2444 open (+44) / 16471 closed (+14) / 18915 total (+58) Open issues with patches: 976 Average duration of open issues: 670 days. Median duration of open issues: 420 days. Open Issues Breakdown open 2410 (+44) pending 33 ( +0) Issues Created Or Reopened (59) … [View More]

1 0

Re: [Python-Dev] [New-bugs-announce] [issue7064] Python 2.6.3 / setuptools 0.6c9: extension module builds fail with KeyError
by skip＠pobox.com Oct. 9, 2009

Oct. 9, 2009

Ned> Due to a change in distutils released with Python 2.6.3, packages Ned> that use setuptools (version 0.6c9, as of this writing), or the Ned> easy_install command, to build C extension modules fail ... ... Ned> Among the packages known to be affected include lxml, Ned> zope-interface, jinja2, and, hence, packages dependent on these Ned> packages (e.g. sphinx, twisted, etc.). Maybe the Python test suite should include tests with a small number of … [View More]

4 3

Logging, Unicode and sockets
by Vinay Sajip Oct. 8, 2009

Oct. 8, 2009

> Thanks to http://bugs.python.org/issue7077 I've noticed that the socket-based logging handlers - SocketHandler, DatagramHandler and SysLogHandler - aren't Unicode-aware and can break in the presence of Unicode messages. I'd like to fix this by giving these handlers an optional (encoding=None) parameter in their __init__, and then using this to encode on output. If no encoding is specified, is it best to use locale.getpreferredencoding(), sys.getdefaultencoding(), sys.… [View More]

3 3

PEP 389: argparse - new command line parsing module
by Steven Bethard Oct. 8, 2009

Oct. 8, 2009

On Sun, Sep 27, 2009 at 8:41 PM, Benjamin Peterson <benjamin(a)python.org> wrote: > 2009/9/27 Steven Bethard <steven.bethard(a)gmail.com>: >> The first release where any real deprecation message would show up is >> Python 3.4, more than 3 years away. If you think 3 years isn't long >> enough for people to be over the Python 3 transition, let's stick in >> another version in there and make it 4.5 years. > > So, why even bother deprecating it if nobody … [View More]

27 72

locals() different behaviour when tracing?
by Anders Waldenborg Oct. 8, 2009

Oct. 8, 2009

Is it intentional that locals() returns a copy/snapshot of the local variables sometimes, and sometimes a reference? Like when enabling tracing, such as in the code pasted below. The documentation ("Update and return a dictionary containing the current scope's local variables.") is pretty unclear. import sys def X(): l = locals() i = "foo" print "Is 'i' in stored locals()? ", ('i' in l) print "Running normally" X() print "Enabling tracing" def t(*a): return t sys.settrace(t) X()

3 2