[issue29652] Fix evaluation order of keys/values in dict comprehensions
janzert <janz...@janzert.com> added the comment: Just as a note so the email discussion isn't forever lost to the void. In an unrelated thread on python-dev recently there was a short discussion on this topic in which both Guido van Rossum[1] and Tim Peters[2] gave the opinion that this should change should probably be made. 1: https://mail.python.org/pipermail/python-dev/2018-April/153122.html 2: https://mail.python.org/pipermail/python-dev/2018-April/153134.html -- nosy: +janzert ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue29652> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1191964] asynchronous Subprocess
Changes by janzert janz...@janzert.com: -- nosy: +janzert ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1191964 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19435] Directory traversal attack for CGIHTTPRequestHandler
Changes by janzert janz...@janzert.com: -- nosy: +janzert ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19435 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19055] Regular expressions: * does not match as many repetitions as possible.
janzert added the comment: The documentation on the | operator in the re module pretty explicitly covers this. http://docs.python.org/2/library/re.html A|B, where A and B can be arbitrary REs, creates a regular expression that will match either A or B. An arbitrary number of REs can be separated by the '|' in this way. This can be used inside groups (see below) as well. As the target string is scanned, REs separated by '|' are tried from left to right. When one pattern completely matches, that branch is accepted. This means that once A matches, B will not be tested further, even if it would produce a longer overall match. In other words, the '|' operator is never greedy. -- nosy: +janzert ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19055 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19037] mailbox module modifies maildir file times after moving from tmp directory
janzert added the comment: Thanks for committing the fix. Figured I should finally get it done and signed the online CLA when I submitted this issue. I assume it just takes a while for someone to go through and apply the appropriate flag? This change seems rather insubstantial for an ACKS line so I certainly don't mind waiting. Since a certain Birkenfeld became Brandl I know names are a bit sensitive for some python core devs. So while my personal preference would go to Janzert* the one that fits Python custom is Brian Haskin. * Janzert is the most widely used and distinct identifier for my open source and online activity. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19037 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19037] mailbox module modifies maildir file times after moving from tmp directory
New submission from janzert: The Maildir.add and Maildir.__setitem__ methods in the mailbox module attempts to change the file mtime after moving the file into the new directory. This allows a race condition since other programs are can move or otherwise modify the file as soon as it is placed in the new directory. If the file is moved from the new directory before the mtime is set this results in an unexpected OSError exception. The fix seems to simply be setting the file mtime before moving the file into its final position. -- components: Library (Lib) messages: 197930 nosy: janzert, petri.lehtinen priority: normal severity: normal status: open title: mailbox module modifies maildir file times after moving from tmp directory type: behavior versions: Python 2.7, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19037 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19037] mailbox module modifies maildir file times after moving from tmp directory
janzert added the comment: I can certainly write a patch if wanted. It should be simply moving and modifying two lines in each of the two methods. My understanding is that it should be against 2.7 so it can be applied there first then merged forward? Unfortunately while I can consistently reproduce the problem, with a script using pyinotify, I'm pretty lost how to write a test that would catch this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19037 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19037] mailbox module modifies maildir file times after moving from tmp directory
Changes by janzert janz...@janzert.com: -- keywords: +patch Added file: http://bugs.python.org/file31802/mailbox.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19037 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18606] Add statistics module to standard library
janzert added the comment: Seems that the discussion is now down to implementation issues and the PEP is at the point of needing to ask python-dev for a PEP dictator? -- nosy: +janzert ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18606 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17174] Posix os.path.join should raise TypeError when passed unusable type
Janzert added the comment: While the current error message is a bit generic, I rather like that it tells you exactly why the type/object passed couldn't be used. -- nosy: +Janzert ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17174 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
