Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #93599 > unrolled thread

Re: module dependencies issues

Started byCyril Scetbon <cyril.scetbon@free.fr>
First post2015-07-09 21:55 +0200
Last post2015-07-09 21:55 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: module dependencies issues Cyril Scetbon <cyril.scetbon@free.fr> - 2015-07-09 21:55 +0200

#93599 — Re: module dependencies issues

FromCyril Scetbon <cyril.scetbon@free.fr>
Date2015-07-09 21:55 +0200
SubjectRe: module dependencies issues
Message-ID<mailman.369.1436471733.3674.python-list@python.org>
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@gmail.com> wrote:
> 
> On Fri, Jul 10, 2015 at 5:08 AM, Cyril Scetbon <cyril.scetbon@free.fr> 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
> -- 
> https://mail.python.org/mailman/listinfo/python-list

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web