Re: [Python-Dev] Deadlock by a second import in a thread

2007-10-20 Thread Brett Cannon
On 10/20/07, Facundo Batista <[EMAIL PROTECTED]> wrote: > 2007/10/19, Christian Heimes <[EMAIL PROTECTED]>: > > > I know a possible solution. You could write a patch that moves the > > imports in C code to the module init function and stores the modules in > > a global static variable. > > I though

[Python-Dev] New chapter "Using Python" in the docs

2007-10-20 Thread Georg Brandl
Hi, as you may have seen in the checkins, I just created a new chapter in the docs called "Using Python." We, the doc team, would like that section to contain, roughly, information how to install Python on different platforms, how to configure it, how to invoke it, what extra things and quirks yo

Re: [Python-Dev] Python developers are in demand

2007-10-20 Thread Michael Kent
Guido van Rossum python.org> writes: > I wonder if we should start maintaining a list of Python developers > for hire somewhere on python.org, beyond the existing Jobs page. Is > anyone interested in organizing this? I would be definitely interested in putting my name on such a list. __

Re: [Python-Dev] Deadlock by a second import in a thread

2007-10-20 Thread Facundo Batista
2007/10/20, Nick Coghlan <[EMAIL PROTECTED]>: > bb.py is broken - importing a module should never spawn a new thread as > a side effect (precisely because it will deadlock if the spawned thread > tries to do an import, which can happen in a myriad of ways). Agreed. But if we move the import of t

Re: [Python-Dev] Deadlock by a second import in a thread

2007-10-20 Thread Facundo Batista
2007/10/19, Christian Heimes <[EMAIL PROTECTED]>: > I know a possible solution. You could write a patch that moves the > imports in C code to the module init function and stores the modules in > a global static variable. I thought about this. It even will have the good side efect of not shooting