module dependencies issues

Cyril Scetbon cyril.scetbon at
Thu Jul 9 21:55:30 CEST 2015

It's just a sample. I'd like to get a general answer. So think about the worst case.
> On Jul 9, 2015, at 21:50, Chris Angelico <rosuav at> wrote:
> On Fri, Jul 10, 2015 at 5:08 AM, Cyril Scetbon <cyril.scetbon at> wrote:
>> Forcing my-module to use B=1.1 fixes the issue. However it's just a sample and my code is using a lot of modules that use other shared modules too. Is there a way to let dependencies use their own version of the modules they need while the current use another version ?
>> Currently every time we need to upgrade one module, we need to make sure dependencies use this new version too :(
> First off, does your module *really* need B==1.0, or can it handle
> B>=1.0? If it can, the solution is easy.
> ChrisA
> -- 

More information about the Python-list mailing list