make this even more unlikely, but it still smells
bad. :-(
Hope this helps.
Best regards,
Jurko Gospodnetić
Below, I've included a few script outputs (tracebacks included) from
instances where Python interpreter crashed due to pressing Ctrl-C soon
after an empty Python scri
block SIGINT handling and allow user code to enable its own or default
Python handling as it wishes and then unblock SIGINT handling. Note that
by 'blocking' a signal I do not mean losing/ignoring it but delaying its
handling until signal handling
regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Hi.
I just noticed that the way help() function displays a function
signature changed between Python 3.3 & 3.4 but I can not find this
documented anywhere. Here's a matching example in both Python 3.3 &
Python 3.4 for comparison:
Python 3.3.3 (v
before filing an issue... but if this is an
issue I hope it can be resolved before the final 3.4 release.
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
f those run the same interpreter when they
have been installed 'for the current user only'.
Is this as issue or desired behaviour? Should I open an issue for it?
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing li
the latest 3.4rc3 release and nothing related to
this seems to have been included yet.
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.
tlib/__init__.py stdlib module?
As I recall, I first learned that not all loaded modules need to have
their __file__ attribute set by researching a failure in some package
when installed as a zipped-egg using setuptools. Admittedly though, that
was some old setu
Hi Paul.
On 10.3.2014. 14:54, Paul Moore wrote:
On 10 March 2014 13:03, Jurko Gospodnetić wrote:
Is this as issue or desired behaviour? Should I open an issue for it?
Sounds like a bug, but a pretty long-standing one. I can't think that
the registry schema Python uses would *ever*
4).
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
2 as the latest 'testing release' (and does not mention the
final Python 3.4.0 release at all).
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/pytho
Hi.
On 17.3.2014. 11:35, Ned Deily wrote:
Thanks for the report. That and other download pages should now be
up-to-date.
Something similar - does PEP 429 (Python 3.4 Release Schedule) need
to be updated? It still lists 3.4.0rc3 as a 'future release'.
Best regards,
nstaller version, but I have not rebuilt CPython, and its MSI
installer to test this theory out.
Anyone have any more information on this?
Should I open a 'Add/Remove Programs' dialog related issue in the
CPython issue tracker? And possibly a separate one for making CPython
Hi.
On 19.3.2014. 16:38, "Martin v. Löwis" wrote:
> Am 17.03.14 22:10, schrieb Jurko Gospodnetić:
>> Fixing
>> this required manually cleaning up leftover CPython 3.4.0rc3 windows
>> installer registry entries. Note that the issue could not be fixed
>> by
ols
packages but that can be done easily by hand and so can be filed as a
minor enhancement issue for the future.
This minor problem reported as issue #20983.
http://bugs.python.org/issue20983
Best regards,
Jurko Gospodnetić
___
Python-
Hi.
On 19.3.2014. 16:38, "Martin v. Löwis" wrote:
Am 17.03.14 22:10, schrieb Jurko Gospodnetić:
Fixing
this required manually cleaning up leftover CPython 3.4.0rc3 windows
installer registry entries. Note that the issue could not be fixed by
using the CPython 3.4.0rc3 installer as
y this out by any chance?
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
ly
> from the private wheel files.
Hope this helps.
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/py
being used from their Python
sources.
OK... just my 2 cents worth... :-)
Best regards,
Jurko Gospodnetić
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.pyt
Hi.
On 17.4.2014. 20:15, Mark Young wrote:
I think he meant modifying the source files themselves for debugging
purposes (e.g. putting print statements in itertools.py).
Exactly! :-)
Best regards,
Jurko Gospodnetić
___
Python-Dev
Hi.
On 17.4.2014. 19:57, Guido van Rossum wrote:
On Thu, Apr 17, 2014 at 10:33 AM, Jurko Gospodnetić
mailto:jurko.gospodne...@pke.hr>> wrote:
I would really love to have better startup times in production,
What's your use case? I understand why startup time is important
Hi.
On 6.6.2014. 21:46, Guido van Rossum wrote:
A reminder:
https://lh5.googleusercontent.com/-d4rF0qJPskQ/U0qpNjP5GoI/PW0/4RF_7zy3esY/w1118-h629-no/Python28.jpg
*ROFL*
Subtle, ain't he? *gdr*
Best regards,
Jurko Gospod
22 matches
Mail list logo
