@carlton Some of my Ruby and Node friends feel Python's package management will never be adequate if this problem isn't addressed.

Assuming you don't mean multiple versions of the same package available everywhere but instead one per package, I think we'd basically need a separate site-packages directory location per package for this. 😬

@brettcannon @treyhunner @carlton

@mitsuhiko Has a blog post from earlier this year with thought on that - and it would be feasible without changes in the language and a lot of hackish stuff.

Me? just put the calls needing a different package version on the other end of a Celery-managed call.

(Actually - it could be done with subinterpreters now as well, in a way that would be a lot cleaner)