On Dec 28, 2004, at 4:30 PM, [EMAIL PROTECTED] wrote:
Update of /cvsroot/python/python/dist/src/Mac/OSX
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9229
Modified Files:
fixapplepython23.py
Log Message:
Just passing -undefined dynamic_lookup isn't enough: we also need to
set
the MACOSX_D
Scott David Daniels wrote:
I'm hoping to add BZIP2 compression to zipfile for 2.5. My primary
motivation is that Project Gutenberg seems to be starting to use BZIP2
compression for some of its zips. What other wish list things do
people around here have for zipfile? I thought I'd collect input h
Scott David Daniels wrote:
I'm hoping to add BZIP2 compression to zipfile for 2.5. My primary
motivation is that Project Gutenberg seems to be starting to use BZIP2
compression for some of its zips. What other wish list things do
people around here have for zipfile? I thought I'd collect input h
Chris Barker wrote:
This really doesn't work well for complex packages. I was quite involved
with the debate about versioning for wxPython (and helped drive it
happening) and that was what I originally proposed. The problem is that
you have a whole pile of modules and libs and user code that all
Eric> Unless you are doing comparison tests, where it would be nice to
Eric> be able to state in a generic way that the new implementation
Eric> should not change answers. May be something like:
Eric> import spam[1] as spamnext# next version
Eric> import spam[0]
Martin v. Löwis wrote:
Eric Nieuwland wrote:
Would it be an idea to submit a PEP for extending the 'import'
keyword?
No. Normally, packages should aim for backwards compatibility, so that
applications would only want to specify a minimum version, such as
import xml
assert xml.version_info > (0,8,2
