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

Groups > comp.lang.python > #93600

Re: module dependencies issues

Show all headers | View raw

On Fri, Jul 10, 2015 at 5:55 AM, Cyril Scetbon <cyril.scetbon@free.fr> wrote:
> It's just a sample. I'd like to get a general answer. So think about the worst case.

(Please don't top-post on this list.)

The worst case is virtually impossible to handle. Somewhere along the
way, you need to say "import B" and Python has to go and fetch up some
module. There has to be exactly one module under that name. This isn't
a packaging issue, it's an issue with how Python references modules:
there can be only one! Highlander: The System Modules Dictionary!

How do you expect the end result to work? Will it be that your code
imports one version of a module, but other code imports another? You
would have to rename one of them or something.

ChrisA

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: module dependencies issues Chris Angelico <rosuav@gmail.com> - 2015-07-10 05:59 +1000
  Re: module dependencies issues Marko Rauhamaa <marko@pacujo.net> - 2015-07-09 23:36 +0300
    Re: module dependencies issues Chris Angelico <rosuav@gmail.com> - 2015-07-10 06:47 +1000
      Re: module dependencies issues Marko Rauhamaa <marko@pacujo.net> - 2015-07-10 00:11 +0300
        Re: module dependencies issues Chris Angelico <rosuav@gmail.com> - 2015-07-10 07:20 +1000
          Re: module dependencies issues Marko Rauhamaa <marko@pacujo.net> - 2015-07-10 00:33 +0300
            Re: module dependencies issues Chris Angelico <rosuav@gmail.com> - 2015-07-10 07:45 +1000
              Re: module dependencies issues Marko Rauhamaa <marko@pacujo.net> - 2015-07-10 03:04 +0300
                Re: module dependencies issues Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-10 01:24 +0100

csiph-web