Brett Cannon wrote:
Really? Without really digging into the code too much I see that if
warnings were set on the command-line it's loaded, otherwise it's
skipped.
You are right. It's not loaded by pythonrun.c. The io module is
importing warnings w/o using it. I fixed it in r65694
./python -S
On Fri, Aug 15, 2008 at 1:09 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
>>
>> Speaking with my importlib hat on, I need a function that can easily
>> return the encoding of a file, so I have another legit use-case for
>> the functionality where exposing it through some bu
Brett Cannon wrote:
Speaking with my importlib hat on, I need a function that can easily
return the encoding of a file, so I have another legit use-case for
the functionality where exposing it through some built-in fashion
would be REALLY appreciated (I have one hacked together as
imp.source_open
Le vendredi 15 août 2008 à 00:13 +0200, "Martin v. Löwis" a écrit :
> > Any thoughts?
>
> That is http://bugs.python.org/issue586680, right?
>
> As a work-around, test_cmd_line should set PYTHONPATH to include
> the build directory (i.e. what addbuilddir has added).
Thanks a lot for the suggesti
On Thu, Aug 14, 2008 at 5:32 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Antoine Pitrou wrote:
>>
>> I feel stupid for not thinking of such an obvious solution.
>> (by the way, is _thread always available?)
>
> _thread is a builtin module. It's available on every platform that supports
> thre
Antoine Pitrou wrote:
I feel stupid for not thinking of such an obvious solution.
(by the way, is _thread always available?)
_thread is a builtin module. It's available on every platform that
supports threading (which should be all platforms we support). If you
want to be extra carefully then
Christian Heimes cheimes.de> writes:
>
> Couldn't you use "from _thread import allocate_lock as Lock" instead?
I feel stupid for not thinking of such an obvious solution.
(by the way, is _thread always available?)
___
Python-3000 mailing list
Python-
Antoine Pitrou wrote:
Well, it looks like I underestimated the consequences of making io.py depend on
the threading module. Is it ok if I add itertools, operator, _collections and
time to the list of statically compiled modules? They are needed by threading,
and thus necessary for running setup.p
Well, it looks like I underestimated the consequences of making io.py depend on
the threading module. Is it ok if I add itertools, operator, _collections and
time to the list of statically compiled modules? They are needed by threading,
and thus necessary for running setup.py on a blank checkout.
> Any thoughts?
That is http://bugs.python.org/issue586680, right?
As a work-around, test_cmd_line should set PYTHONPATH to include
the build directory (i.e. what addbuilddir has added).
Regards,
Martin
___
Python-3000 mailing list
Python-3000@python.o
Hello,
I have a problem with "python -S". When python is launched from its build dir,
the extension build dir is not added to sys.path, and thus importing some
modules fails:
$ ./python -S -c "import threading"
Traceback (most recent call last):
File "", line 1, in
File "/home/antoine/py3k/p
11 matches
Mail list logo
