Best practices for simultaneously installed versioned packages?

Larry Hastings larry at hastings.org
Mon Jan 4 12:09:32 CET 2010


I'm writing a package for Python 3--let's call it "spacegoblin".  I fear someday I may need multiple versions installed and available simultaneously, even within one version of Python.  So I want to plan ahead for that possibility.  What would be the best way to allow this?  Right now I install the package with the version in the name, like "spacegoblin_1_0" and "spacegoblin_1_1".  But I have an uneasy sense that I'm doing something stupid... mainly because I've never seen anyone do this before.

A coworker said they did it like "spacegoblin.1_0" and "spacegoblin.1_1" at a previous employer.  That seems like an improvement, though not the "yes that's obviously right" answer I'm holding out for.  Your thoughts?

Thanks,


/larry/

p.s. Before you ask: no, I don't want to use "virtualenv" for this.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20100104/c2fe1e41/attachment.html>


More information about the Python-list mailing list