[issue24132] Direct sub-classing of pathlib.Path

Change by Torsten Bronger <bron...@physik.rwth-aachen.de>: -- nosy: +bronger ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue22005] datetime.__setstate__ fails decoding python2 pickle

Changes by Torsten Bronger <bron...@physik.rwth-aachen.de>: -- nosy: +bronger ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue22570] Better stdlib support for Path objects

Changes by Torsten Bronger <bron...@physik.rwth-aachen.de>: -- nosy: +bronger ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

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

Changes by Torsten Bronger bron...@physik.rwth-aachen.de: -- nosy: +bronger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20362 ___ ___ Python

[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.04. That said

[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 rep...@bugs.python.org

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

Changes by Torsten Bronger bron...@physik.rwth-aachen.de: -- nosy: +bronger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9400 ___ ___ Python-bugs

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger bron...@physik.rwth-aachen.de 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(***, ***) s.sendmail

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger bron...@physik.rwth-aachen.de 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...@googlemail.com], Hello) (A bracket was missing

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger bron...@physik.rwth-aachen.de 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 rep...@bugs.python.org http://bugs.python.org/issue4470

[issue4470] smtplib SMTP_SSL not working.

Torsten Bronger bron...@physik.rwth-aachen.de 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

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

Changes by Torsten Bronger bron...@physik.rwth-aachen.de: -- nosy: +bronger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1596321 ___ ___ Python

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

Torsten Bronger bron...@physik.rwth-aachen.de added the comment: The problem is the pickle result. It's not about debugging the pickler itself. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2980

[issue992389] attribute error after non-from import

Torsten Bronger bron...@physik.rwth-aachen.de 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

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

Torsten Bronger bron...@physik.rwth-aachen.de 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

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

Torsten Bronger bron...@physik.rwth-aachen.de added the comment: protocol 8 -- protocol 0 of course. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2980

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

Torsten Bronger bron...@physik.rwth-aachen.de 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

[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-list mailing list Unsubscribe

[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 imports don't