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


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

Re: reloading code and multiprocessing

Started byChris Angelico <rosuav@gmail.com>
First post2012-07-24 00:15 +1000
Last post2012-07-24 00:15 +1000
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: reloading code and multiprocessing Chris Angelico <rosuav@gmail.com> - 2012-07-24 00:15 +1000

#25875 — Re: reloading code and multiprocessing

FromChris Angelico <rosuav@gmail.com>
Date2012-07-24 00:15 +1000
SubjectRe: reloading code and multiprocessing
Message-ID<mailman.2472.1343052959.4697.python-list@python.org>
On Mon, Jul 23, 2012 at 11:51 PM, andrea crotti
<andrea.crotti.0@gmail.com> wrote:
> Anyway the only other problem which I found is that if I start the
> subprocesses after many other things are initialised, it might happen
> that the reloading doesn't work correctly, is that right?
>
> Because sys.modules will get inherited from the subprocesses and it
> will not reimport what has been already imported as far as I
> understood..
>
> So or I make sure I import everything only where it is needed or (and
> maybe better and more explicit) I remove manually from sys.modules all
> the modules that I want to reload, what do you think?

That would probably be correct. However, I still think you may be
fighting against the language instead of playing to its strengths.

I've never fiddled with sys.modules like that, but I know some have,
without problem.

ChrisA

[toc] | [standalone]


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


csiph-web