Thanks for the comments,
in my particular case we're actually on a provisioning /framework/, so
we chose the easy (lazy?) way, i.e initializing miscellaneous modules at
loading times (like Django or others do, I think), rather than building
an proper initialization dispatcher to be called from
On 3 Jul 2013 04:34, "Pascal Chambon" wrote:
>
> Hello everyone,
>
> I'd like to bring your attention to this issue, since it touches the
fundamentals of python's import workflow:
> http://bugs.python.org/issue17716
>
> I've tried to post it on the python-import ML for weeks, but it must
still be
On 3 Jul 2013 05:44, "R. David Murray" wrote:
>
> On Tue, 02 Jul 2013 20:31:48 +0200, Pascal Chambon
wrote:
> > I agree that a module loading should be, as much as possible, "side
> > effects free", and thus shouldn't have temporary errors. But well, in
> > practice, module loading is typically t
On Tue, 02 Jul 2013 20:31:48 +0200, Pascal Chambon wrote:
> I agree that a module loading should be, as much as possible, "side
> effects free", and thus shouldn't have temporary errors. But well, in
> practice, module loading is typically the time where process-wide
> initialization are done (
Hello everyone,
I'd like to bring your attention to this issue, since it touches the
fundamentals of python's import workflow:
http://bugs.python.org/issue17716
/I've tried to post it on the python-import ML for weeks, but it must
still be blocked somewhere in a moderation queue, so here I co
