Georg Brandl, 19.02.2011 21:53:
BTW, I haven't seen an issue yet.
http://bugs.python.org/issue11254
Stefan
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mail
On Sun, Feb 20, 2011 at 6:53 AM, Georg Brandl wrote:
> Given that we are only hours from the final, I'm quite unwilling to
> call this a blocker, seeing that running from the .py file works well
> (and I'm not really of Antoine's opinion that that is such a big
> performance hit).
How significant
Am 19.02.2011 14:29, schrieb Nick Coghlan:
> On Sat, Feb 19, 2011 at 11:14 PM, Antoine Pitrou wrote:
>> On Sat, 19 Feb 2011 23:07:17 +1000
>> Nick Coghlan wrote:
>>>
>>> While this is definitely untidy, it doesn't strike me as a release
>>> blocker. More of a "fix it in 3.2.1", since the status q
Le samedi 19 février 2011 à 14:27 +0100, "Martin v. Löwis" a écrit :
> Am 19.02.2011 14:14, schrieb Antoine Pitrou:
> > On Sat, 19 Feb 2011 23:07:17 +1000
> > Nick Coghlan wrote:
> >>
> >> While this is definitely untidy, it doesn't strike me as a release
> >> blocker. More of a "fix it in 3.2.1",
On Sat, Feb 19, 2011 at 11:14 PM, Antoine Pitrou wrote:
> On Sat, 19 Feb 2011 23:07:17 +1000
> Nick Coghlan wrote:
>>
>> While this is definitely untidy, it doesn't strike me as a release
>> blocker. More of a "fix it in 3.2.1", since the status quo will
>> *work*, it just means the precompiled f
Am 19.02.2011 14:14, schrieb Antoine Pitrou:
> On Sat, 19 Feb 2011 23:07:17 +1000
> Nick Coghlan wrote:
>>
>> While this is definitely untidy, it doesn't strike me as a release
>> blocker. More of a "fix it in 3.2.1", since the status quo will
>> *work*, it just means the precompiled file will be
On Sat, 19 Feb 2011 23:07:17 +1000
Nick Coghlan wrote:
>
> While this is definitely untidy, it doesn't strike me as a release
> blocker. More of a "fix it in 3.2.1", since the status quo will
> *work*, it just means the precompiled file will be ignored on first
> execution with newer Python versi
On Sat, Feb 19, 2011 at 10:37 PM, Stefan Behnel wrote:
> What I think is happening here, is that the normal import mechanism byte
> compiles the 2to3 converted sources into the __pycache__ directory (when
> invoked at extension building time), but then distutils' byte compilation
> seems to decide
> sorry for asking here instead of filing a bug, but given that 3.2 final
> is pretty close, I wanted to make sure this gets considered.
If you want it decided before the 3.2 release, it must be a
release-critical bug report in the tracker. Posting it here does not
make sure
it gets considered.
R
Hi,
sorry for asking here instead of filing a bug, but given that 3.2 final is
pretty close, I wanted to make sure this gets considered.
A Cython user noticed that the installation (setup.py install or bdist)
puts several .pyc files into the installed source directory, instead of
moving them
10 matches
Mail list logo
