Fred Drake wrote:
Even simple cases present issues with regard to this. For example, I
work on a project that relies on the uuid module, so we declare a
dependency on Ka-Ping Ye's uuid module (since we're using Python 2.4).
How should we write that in a version-agnostic way if we want to use the
standard library version of that module with newer Pythons?
Well, that could be done be getting standard library modules to:
- declare what version they are
- be overridable why installed packages
That way, the fact that the standard library's development moves at the
speed of frozen tar wouldn't stop packages in it being developed and
released seperately for people who want to use newer versions of them
and aren't in a situation where they need "batteries included"...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
