Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.015 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'fixes': 0.05; 'cc:addr :python-list': 0.09; 'forcing': 0.09; 'subject:dependencies': 0.09; 'subject:module': 0.09; 'received:212.27': 0.16; 'received:212.27.42': 0.16; 'received:free.fr': 0.16; 'subject:issues': 0.16; 'worst': 0.16; 'wrote:': 0.16; 'case.': 0.18; 'module,': 0.18; '2015': 0.20; 'cc:2**0': 0.20; 'cc:addr:python.org': 0.20; 'issue.': 0.20; 'am,': 0.23; 'header :In-Reply-To:1': 0.24; 'module': 0.25; 'chris': 0.26; 'fri,': 0.27; 'too.': 0.30; 'url:mailman': 0.30; 'code': 0.30; "i'd": 0.31; 'another': 0.32; 'url:python': 0.33; 'url:listinfo': 0.34; 'handle': 0.34; 'too': 0.36; 'there': 0.36; 'url:org': 0.36; 'modules': 0.36; 'subject:: ': 0.37; 'charset:us-ascii': 0.37; 'version': 0.38; 'shared': 0.38; 'sure': 0.39; 'does': 0.39; 'received:192': 0.39; 'url:mail': 0.40; 'your': 0.60; 'header :Message-Id:1': 0.61; 'sample': 0.63; 'answer.': 0.72; 'jul': 0.72; '*really*': 0.84; 'chrisa': 0.84; 'off,': 0.84 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: module dependencies issues From: Cyril Scetbon In-Reply-To: Date: Thu, 9 Jul 2015 21:55:30 +0200 Cc: "python-list@python.org" Content-Transfer-Encoding: quoted-printable References: <10ADE079-3F0F-4EA8-9312-06F7FCDB6130@free.fr> To: Chris Angelico X-Mailer: Apple Mail (2.2102) X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 21 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1436471733 news.xs4all.nl 2962 [2001:888:2000:d::a6]:54672 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:93599 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 wrote: >=20 > On Fri, Jul 10, 2015 at 5:08 AM, Cyril Scetbon = wrote: >> Forcing my-module to use B=3D1.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 :( >>=20 >=20 > First off, does your module *really* need B=3D=3D1.0, or can it handle > B>=3D1.0? If it can, the solution is easy. >=20 > ChrisA > --=20 > https://mail.python.org/mailman/listinfo/python-list