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
Martin v. Löwis wrote:
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)
Well, yes, but life is not always so simple, and while, as a rule,
version 2.3 should be bac
Martin> If you really want side-by-side installation of different
Martin> versions, and a mechanism to select between them, the package
Martin> could support
Martin> import xml_0_8_2 as xml
Martin> IOW, "import-as" should be sufficient for what you want to achieve.
That's mo
On Dec 27, 2004, at 8:45 PM, Chris Barker wrote:
The versioning system that wxPython now has is quite nice, and seems
to fit most people's needs well. However, it's also quite new, and who
know what problems will arise. For those interested, here's a
synopsis.
http://wiki.wxpython.org/index.cgi
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)
If you really want sid
Hi all,
On 27 dec 2004, at 19:27, Chris Barker wrote:
Robin has added versioning to the latest wxPython, and I. for one am
ecstatic. It works great for me. I am generally using 2.5.3, but have
2.4.2 installed, and a number of my apps depend on it (on Linux
anyway, it's pretty useless on OS-X)
