[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-distutils-sig
Subject:    [Distutils] Module Versioning.
From:       distutils-sig () claytonbrown ! net (distutils-sig () claytonbrown ! net)
Date:       2004-05-17 9:08:41
Message-ID: 000001c43c10$3d87a6a0$0a07a8c0 () ab1tch
[Download RAW message or body]

I noticed a Module Versioning import technique in a module
PythonMegaWidgets(http://pmw.sourceforge.net/)

Is there any reason as to why this technique could not be applied to the
site-packages directory to allow more control of which version of a
module is used.
Does anyone know if anyone else come up with a more appropriate solution
to this problem.

Perhaps this could be improved with a versionmodule.py <module-name>,
which could sniff a module sugesting/allowing user input of a module
major_minor_patch, moving it into a versioned directory. Allowing
setup.py's to behave as they do.

Are there any other standard practices which allow specification of a
modules version at time of import / site-packages with module versions,
that is known not to introduce problems when using disutils/p2exe etc.

Clay.



[prev in list] [next in list] [prev in thread] [next in thread]