[issue24132] Direct sub-classing of pathlib.Path

Change by Torsten Bronger : -- nosy: +bronger ___ Python tracker <https://bugs.python.org/issue24132> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22005] datetime.__setstate__ fails decoding python2 pickle

Changes by Torsten Bronger : -- nosy: +bronger ___ Python tracker <http://bugs.python.org/issue22005> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22570] Better stdlib support for Path objects

Torsten Bronger added the comment: Please be conservative with adding methods to Path. FWIW, my own experiences with pathlib have shown that utility methods have the disadvantage of duplicating well-established Python idioms. This reduces code readability in my opinion. While it is

[issue22570] Better stdlib support for Path objects

Changes by Torsten Bronger : -- nosy: +bronger ___ Python tracker <http://bugs.python.org/issue22570> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20362] longMessage attribute is ignored in unittest.TestCase.assertRegexpMatches etc

Changes by Torsten Bronger : -- nosy: +bronger ___ Python tracker <http://bugs.python.org/issue20362> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger added the comment: Sorry, after having had another look at it, I realised that I have a different SSMTP issue now, non-Python-related. So for me, Ubuntu 13.04 indeed solves my old issue. -- ___ Python tracker <h

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger added the comment: For five Ubuntu releases now, I apply this patch. In contrast to Catalin's statement, it is not solved for me unless the upstream changes of two years ago haven't yet found their way into Ubuntu. I'm currently using Python 2.7.4 on Ubuntu 13

[issue9400] multiprocessing.pool.AsyncResult.get() messes up exceptions

Changes by Torsten Bronger : -- nosy: +bronger ___ Python tracker <http://bugs.python.org/issue9400> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger added the comment: My Python version is "Python 2.7.1+" and the package is called "python2.7 2.7.1-5ubuntu2" (Ubuntu Natty). -- ___ Python tracker <http://bu

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger added the comment: Sorry, it must be: import smtplib s = smtplib.SMTP_SSL("relay-auth.rwth-aachen.de") s.login("***", "***") s.sendmail("bron...@physik.rwth-aachen.de", ["bronger.ran...@google

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger added the comment: No, I don't know how to do that. All I can provide is a minimal version of my code that triggers the above mentioned traceback. It is: import smtplib s = smtplib.SMTP_SSL("relay-auth.rwth-aachen.de") s.login("***", "***&quo

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger added the comment: I still have to apply Catucci's patch (or a modification of) after every Ubuntu installation or upgrade. Otherwise, I get ... File "/usr/lib/python2.7/smtplib.py", line 752, in __init__ SMTP.__init__(self, host, port, local_hostname,

[issue1596321] KeyError at exit after 'import threading' in other thread

Changes by Torsten Bronger : -- nosy: +bronger ___ Python tracker <http://bugs.python.org/issue1596321> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Torsten Bronger added the comment: The "problem" is the pickle result. It's not about debugging the pickler itself. -- ___ Python tracker <http://bugs.py

[issue992389] attribute error after non-from import

Torsten Bronger added the comment: Maybe it's better to leave it open, waiting for someone to pick it up, even if this is some time in the future? In my opinion, this is suprising behaviour without an actual rationale, and a current implementation feature. I'd be a pitty for me

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Torsten Bronger added the comment: Well, Django doesn't story binary data at all but wants you to store image files etc in the file system. Whether this was a good design decision, is beyond the scope of this issue. My points actually are only these: a) the docs strongly suggest

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Torsten Bronger added the comment: "protocol 8" --> "protocol 0" of course. ___ Python tracker <http://bugs.python.org/issue2980> ___ ___

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Torsten Bronger added the comment: I ran into this problem today when writing python data structures into a database. Only ASCII is safe in this situation. I understood the Python docs that protocol 0 was ASCII-only. I use pickle+base64 now, however, this makes debugging more difficult

[issue2504] Add gettext.pgettext() and variants support

Changes by Torsten Bronger <[EMAIL PROTECTED]>: -- nosy: +bronger __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2504> __ ___ Python-bugs

[issue992389] attribute error after non-from import

Torsten Bronger <[EMAIL PROTECTED]> added the comment: I dare to make a follow-up although I have no idea at all about the internal processes in the Python interpreter. But I've experimented with circular imports a lot recently. Just two points: First, I think that circular im

[issue992389] attribute error after non-from import

Torsten Bronger <[EMAIL PROTECTED]> added the comment: I have a very similar issue (maybe the same?) at the moment. Assume the follwing package structure: main.py package/ __init__.py [empty] moduleX.py moduleY.py main.py says: from package import moduleX moduleX.p