[issue11181] TLS end connection not detected properly in retrbinary
Changes by Georg Brandl ge...@python.org: -- assignee: - giampaolo.rodola nosy: +giampaolo.rodola priority: normal - high ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11180] More efficient nlargest()/nsmallest()
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: The current routines are designed to consume only k elements of memory. That is the way it should remain. Manifesting the entire input iterable into memory is unnecessary and is not cache friendly. Also, I question your assertions about running time. In the worst case where the entire input in reverse sorted, it does take O(log k) for each insertion. For other cases, like random orderings, it takes much less because many of the inputs only need to compare to the very top element of the heap. In practice for small k and large n, running time close to O(n) is not uncommon. - class Int(int): def __lt__(self, other): global cmps cmps += 1 return int.__lt__(self, other) from random import shuffle from heapq import nsmallest n = 1 k = 16 data = list(map(Int, range(n))) for i in range(10): shuffle(data) cmps = 0 result = nsmallest(k, data) print(cmps, result) -- test run -- 10485 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10560 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10584 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10518 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10582 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10650 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10409 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10577 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10499 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] 10603 [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15] -- assignee: - rhettinger components: +Library (Lib) resolution: - rejected status: open - closed versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11180 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6721] Locks in python standard library should be sanitized on fork
Charles-Francois Natali neolo...@free.fr added the comment: I was clearly wrong about a release being done in the child being the right thing to do (issue6643 proved that, the state held by a lock is not usable to another process on all platforms such that release even works). Yeah, apparently OS-X is one of them, the reporter in #11148 is experiencing segfaults under OS-X. Are you suggesting to use pthread_atfork to call pthread_mutex_init on all mutexes created by Python in the child after a fork? I'll have to ponder that some more. Given the mutexes are all useless post fork it does not strike me as a bad idea. Yes, that's what I was thinking. Instead of scattering the lock-reclaiming code all over the place, try to use a more standard API specifically designed with that in mind. Note the base issue is that we're authorizing things which are forbidden : in a multi-threaded process, only sync-safe calls are authorized between fork and exec. 2011/2/10 Gregory P. Smith rep...@bugs.python.org: Gregory P. Smith g...@krypto.org added the comment: Yeah, I'm trying to figure out what I was thinking then or if I was just plain wrong. :) I was clearly wrong about a release being done in the child being the right thing to do (issue6643 proved that, the state held by a lock is not usable to another process on all platforms such that release even works). Part of it looks like I wanted a way to detect it was happening as any lock that is held during a fork indicates a _potential_ bug (the lock wasn't registered anywhere to be released before the fork) but not everything needs to care about that. -- versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6721 ___ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6721 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11181] TLS end connection not detected properly in retrbinary
Changes by Antoine Pitrou pit...@free.fr: -- priority: high - normal stage: - needs patch type: crash - behavior versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11183] Finer-grained exceptions for the ssl module
New submission from Antoine Pitrou pit...@free.fr: pyOpenSSL (*) has the good idea of defining exception subclasses for the various OpenSSL error codes (ZeroReturnError, WantReadError, etc.). The ssl module could do the same. (*) http://packages.python.org/pyOpenSSL/openssl-ssl.html -- components: Library (Lib) messages: 128370 nosy: exarkun, giampaolo.rodola, pitrou priority: normal severity: normal status: open title: Finer-grained exceptions for the ssl module type: feature request versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11183 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11076] Iterable argparse Namespace
Steven Bethard steven.beth...@gmail.com added the comment: There's no argparse in 3.1, so it should only go into 2.7, 3.2 and 3.3. But yes, the patch looks great to me too. -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11076 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10423] s/args/options in arpgarse Upgrading optparse code
Steven Bethard steven.beth...@gmail.com added the comment: The request was for the latter: just make it stronger in the mentioned line that what was called previously 'option' is now called 'args'. As far as adding the parentheses or not, I never once used the parentheses back when I was using optparse, so it didn't even strike me to put them in there. But you're right - the optparse docs do that, so I'm fine if you'd like to make the argparse discussion of optparse match up better with the optparse docs. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10423 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11181] TLS end connection not detected properly in retrbinary
Giampaolo Rodola' g.rod...@gmail.com added the comment: Please provide more information. Have you actually seen this happen? retrlines method isn't currently looking for EOF. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
New submission from Sébastien Sablé sa...@users.sourceforge.net: I get 2 errors when running test_io.py with trunk on AIX. == ERROR: test_large_file_ops (__main__.CIOTest) -- Traceback (most recent call last): File ./Lib/test/test_io.py, line 418, in test_large_file_ops self.large_file_ops(f) File ./Lib/test/test_io.py, line 321, in large_file_ops self.assertEqual(f.seek(self.LARGE), self.LARGE) OverflowError: Python int too large to convert to C long == ERROR: test_large_file_ops (__main__.PyIOTest) -- Traceback (most recent call last): File ./Lib/test/test_io.py, line 418, in test_large_file_ops self.large_file_ops(f) File ./Lib/test/test_io.py, line 321, in large_file_ops self.assertEqual(f.seek(self.LARGE), self.LARGE) OverflowError: Python int too large to convert to C long -- Ran 395 tests in 27.958s FAILED (errors=2, skipped=8) thanks in advance -- components: IO messages: 128374 nosy: sable priority: normal severity: normal status: open title: test_io error on AIX versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11185] test_wait4 error on AIX
New submission from Sébastien Sablé sa...@users.sourceforge.net: I get an error when running test_wait4 with trunk on AIX: test_wait (__main__.Wait4Test) ... FAIL == FAIL: test_wait (__main__.Wait4Test) -- Traceback (most recent call last): File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/fork_wait.py, line 72, in test_wait self.wait_impl(cpid) File ./Lib/test/test_wait4.py, line 23, in wait_impl self.assertEqual(spid, cpid) AssertionError: 0 != 1486954 -- Ran 1 test in 12.030s FAILED (failures=1) Traceback (most recent call last): File ./Lib/test/test_wait4.py, line 32, in module test_main() File ./Lib/test/test_wait4.py, line 28, in test_main run_unittest(Wait4Test) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/support.py, line 1145, in run_unittest _run_suite(suite) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/support.py, line 1128, in _run_suite raise TestFailed(err) test.support.TestFailed: Traceback (most recent call last): File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/fork_wait.py, line 72, in test_wait self.wait_impl(cpid) File ./Lib/test/test_wait4.py, line 23, in wait_impl self.assertEqual(spid, cpid) AssertionError: 0 != 1486954 Thanks in advance -- messages: 128375 nosy: sable priority: normal severity: normal status: open title: test_wait4 error on AIX versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11185 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Antoine Pitrou pit...@free.fr added the comment: Hmm, strange. Is it a 32-bit build? Is HAVE_LARGEFILE_SUPPORT defined in pyconfig.h? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Antoine Pitrou pit...@free.fr added the comment: Apparently AIX needs a specific #define to enable large file support: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.genprogc/doc/genprogc/prg_lrg_files.htm Python defines _LARGEFILE_SOURCE by default. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11180] More efficient nlargest()/nsmallest()
Mark Dickinson dicki...@gmail.com added the comment: [Raymond] Also, I question your assertions about running time. [...] Interesting observation. I wonder what the average number of comparisons actually is, for random inputs. A quick back-of-the-envelope calculation suggests that O(max(k*log(k)*log(n), n)) might be a tighter upper bound. Anyway, I agree with Benjamin that you (newacct) would need to implement the algorithm and demonstrate an obvious improvement. Even then, it would be hard to swallow changing the algorithms to require O(n) space. -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11180 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11149] [PATCH] Configure should enable -fwrapv for clang
Ismail Donmez ism...@namtrac.org added the comment: I think the patch is good to go, any comments/questions ? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11149 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11082] ValueError: Content-Length should be specified
Senthil Kumaran orsent...@gmail.com added the comment:
Thanks. Committed in r88394.
Regarding the encoding information. An explanation of this sort might be
helpful.
The string can be encoded using ISO-8859-1 which is the default encoding for
POST data or the user can also encode using a custom encoding , in which case,
Content-Type: header should specify the encoding value in addition to
'application/x-www-form-urlencoded' which is specified for POST data. For
Example:, if one has to use utf-8
sdata = urllib.parse.urlencode({ሀ:ሢ})
bytesdata = sdata.encode('utf-8')
reqheaders=dict([(Content-Type, application/x-www-form-urlencoded ;
charset=utf-8)])
urllib.request.Request('http://www.example.com',bytesdata,reqheaders)
--
resolution: - fixed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11082
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7330] PyUnicode_FromFormat segfault
STINNER Victor victor.stin...@haypocalc.com added the comment:
It looks like your patch fixes #10829: you should add tests for that, you can
just reuse the tests of my patch (attached to #10829).
---
unicode_format() looks suboptimal.
+memset(buffer, ' ', width);
+width_unicode = PyUnicode_FromStringAndSize(buffer, width);
You should avoid this byte string (buffer) and use memset() on the Unicode
string directly. Something like:
Py_UNICODE *u;
Py_ssize_t i;
width_unicode = PyUnicode_FromUnicode(NULL, width);
u = PyUnicode_AS_UNICODE(width_unicode);
for(i=0; i width; i++) {
*u = (Py_UNICODE)' ';
u++;
}
You should also avoid the creation of a temporary unicode object (it can be
slow if precision is large) using PySequence_GetSlice(). Py_UNICODE_COPY() does
already truncate the string because you can pass an arbitrary length.
---
I don't like unicode_format function name: it sounds like str.format() in
Python. A suggestion: unicode_format_align
---
With your patch, %.200s truncates the input string to 200 *characters*, but I
think that it should truncate to 200 *bytes*, as printf does.
---
-n += PyUnicode_GET_SIZE(str);
+n += width PyUnicode_GET_SIZE(str) ? width :
PyUnicode_GET_SIZE(str);
I don't like this change because I hate having to compute manually strings
length. It should that it would be easier if you format directly strings with
width and precision at step 3, instead of doing it at step 4: so you can just
read the length of the formatted string, and it avoids having to handle
width/precision in two steps (which may be inconsistent :-/).
---
Your patch implements %.100s (and %.100U): we might decide what to do with
#10833 before commiting your patch.
---
In my opinion, the patch is a little bit too big. We may first commit the fix
on the code parsing the width and precision: fix #10829?
---
Can you add tests for %.s? I would like to know if %.s is different than
%s :-)
---
- must be a sequence, not %200s,
+ must be a sequence, not %.200s,
Hum, I think that they are many other places where such fix should be done.
Nobody noticed this typo before because %.200s nor %200s were implemented
(#10833).
---
Finally, do you really need to implement %200s, %2.5s and %.100s? I don't know,
but I would be ok to commit the patch if you fix it for all of my remarks :-)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7330
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11186] pydoc: HTMLDoc.index() doesn't support PEP 383
New submission from STINNER Victor victor.stin...@haypocalc.com: If you have an undecodable filenames on UNIX, Python 3 escapes undecodable bytes using surrogates. pydoc: HTMLDoc.index() uses indirectly os.listdir() which does such operation, and later filenames are encoded to UTF-8 (the whole HTML content is encoded to UTF-8). In practice, you cannot import such .py file, you run them using python script.py, so we can maybe just ignore modules with undecodable filenames. For example: def isUndecodableFilename(filename): return any((0xD800 = ord(ch) = 0xDFFF) for ch in filename) Or we can escape the surrogate characters, but I don't know how. Write \uDC80 in a HTML document is not a good idea, especially in an URL (e.g. Firefox replaces \ by / in URLs). -- assignee: docs@python components: Documentation, Library (Lib) messages: 128382 nosy: docs@python, haypo priority: normal severity: normal status: open title: pydoc: HTMLDoc.index() doesn't support PEP 383 versions: Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11186 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11186] pydoc: HTMLDoc.index() doesn't support PEP 383
STINNER Victor victor.stin...@haypocalc.com added the comment: Oops, my isUndecodableFilename() example is wrong. PEP 383 only uses U+DC80..U+DCFF range: def isUndecodableFilename(filename): return any((0xDC80 = ord(ch) = 0xDCFF) for ch in filename) Example of undecodable filename: b'bla\xe9\xff.py' with UTF-8 filesystem encoding is decoded as 'bla\uDCE9\uDCFF.py'. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11186 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11187] PyUnicode_AsEncodedString: the bootstrap hack is no more needed
New submission from STINNER Victor victor.stin...@haypocalc.com: Since version 3.2, Python uses the locale encoding in PyUnicode_EncodeFSDefault() using _Py_wchar2char() and _Py_char2wchar() until the codec registry is initialized and the locale codec is loaded (until initfsencoding() is done). Before Python 3.2, Python used ASCII in PyUnicode_AsEncodedString() at bootstrap (before the codec registry was initialized): we don't need this hack anymore and it is bad to use ASCII instead of the locale encoding (encode/decode can fail). This ticket is just a reminder for me: I am waiting Python 3.3 to remove PyUnicode_AsEncodedString() bootstrap hack ;-) -- components: Interpreter Core files: unicode_asencodedstring_bootstrap.patch keywords: patch messages: 128384 nosy: haypo priority: normal severity: normal status: open title: PyUnicode_AsEncodedString: the bootstrap hack is no more needed versions: Python 3.3 Added file: http://bugs.python.org/file20744/unicode_asencodedstring_bootstrap.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11187 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11187] PyUnicode_AsEncodedString: the bootstrap hack is no more needed
Changes by STINNER Victor victor.stin...@haypocalc.com: -- components: +Unicode ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11187 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Sébastien Sablé sa...@users.sourceforge.net added the comment: OK, so the following patch should help: Index: configure.in === --- configure.in(revision 88393) +++ configure.in(working copy) @@ -1375,6 +1375,8 @@ if test $use_lfs = yes; then # Two defines needed to enable largefile support on various platforms +AC_DEFINE(_LARGEFILES, 1, +[This must be defined on some systems to enable large file support.]) # These may affect some typedefs AC_DEFINE(_LARGEFILE_SOURCE, 1, [This must be defined on some systems to enable large file support.]) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Sébastien Sablé sa...@users.sourceforge.net added the comment: the error is different now that _LARGEFILES is defined: == ERROR: test_large_file_ops (__main__.CIOTest) -- Traceback (most recent call last): File ./Lib/test/test_io.py, line 418, in test_large_file_ops self.large_file_ops(f) File ./Lib/test/test_io.py, line 321, in large_file_ops self.assertEqual(f.seek(self.LARGE), self.LARGE) IOError: [Errno 22] Invalid argument == ERROR: test_large_file_ops (__main__.PyIOTest) -- Traceback (most recent call last): File ./Lib/test/test_io.py, line 418, in test_large_file_ops self.large_file_ops(f) File ./Lib/test/test_io.py, line 321, in large_file_ops self.assertEqual(f.seek(self.LARGE), self.LARGE) IOError: [Errno 22] Invalid argument -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Antoine Pitrou pit...@free.fr added the comment:
Hmm, interesting. Can you post the results of the two following snippets:
f = open('foo', 'wb')
f.seek(2**32)
# should be 4294967296
f = open('foo', 'wb')
f.truncate(2**32)
# should be 4294967296
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11184
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Sorry I made a mistake in my previous patch (_LARGEFILES instead of
_LARGE_FILES).
Here is a better one:
Index: configure.in
===
--- configure.in(révision 88395)
+++ configure.in(copie de travail)
@@ -1376,6 +1376,14 @@
if test $use_lfs = yes; then
# Two defines needed to enable largefile support on various platforms
# These may affect some typedefs
+case $ac_sys_system/$ac_sys_release in
+AIX*)
+AC_DEFINE(_LARGE_FILES, 1,
+[This must be defined on AIX systems to enable large file support.])
+ ;;
+*)
+;;
+esac
AC_DEFINE(_LARGEFILE_SOURCE, 1,
[This must be defined on some systems to enable large file support.])
AC_DEFINE(_FILE_OFFSET_BITS, 64,
The test fails in a different way now:
==
ERROR: test_large_file_ops (__main__.CIOTest)
--
Traceback (most recent call last):
File ./Lib/test/test_io.py, line 418, in test_large_file_ops
self.large_file_ops(f)
File ./Lib/test/test_io.py, line 323, in large_file_ops
self.assertEqual(f.write(bxxx), 3)
IOError: [Errno 27] File too large
==
ERROR: test_large_file_ops (__main__.PyIOTest)
--
Traceback (most recent call last):
File ./Lib/test/test_io.py, line 418, in test_large_file_ops
self.large_file_ops(f)
File ./Lib/test/test_io.py, line 323, in large_file_ops
self.assertEqual(f.write(bxxx), 3)
IOError: [Errno 27] File too large
--
Ran 395 tests in 27.958s
Here is your trace:
phenix:~/.buildbot/python-aix6/3.x.phenix.xlc/build\ ./python
Python 3.2rc2+ (py3k:88393M, Feb 11 2011, 14:56:34) [C] on aix6
Type help, copyright, credits or license for more information.
f = open('foo', 'wb')
[55983 refs]
f.seek(2**32)
4294967296
[55987 refs]
f = open('foo', 'wb')
__main__:1: ResourceWarning: unclosed file _io.BufferedWriter name='foo'
[55994 refs]
f.truncate(2**32)
Traceback (most recent call last):
File stdin, line 1, in module
IOError: [Errno 27] File too large
[56027 refs]
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11184
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
R. David Murray rdmur...@bitdance.com added the comment: The finally was doing a _sync_close, which flushes the tmp file and closes it. The except Exception is checking if any non-BaseException error occurs, *removing* the tmp file, and re-raising the exception. There's nothing to flush/close in that case. Then, the else: clause of the exception deals with doing the _sync_close if, eg, we had a keyboard interrupt. That may or may not leave the mailbox in a sensible state, but it is no worse than the previous behavior. Certainly for any non-BaseException exception the new code is better; previously you'd most likely wind up with an empty or partially written message tmp file. I'm open to changing to BaseException, though, if you think that would be better (I can see the argument for that). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Antoine Pitrou pit...@free.fr added the comment: Thanks for the patch. The test fails in a different way now: [...] IOError: [Errno 27] File too large This seems to mean that your file system isn't configured for large files. According to http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.genprogc/doc/genprogc/prg_lrg_files.htm : For the JFS, the maximum file size is determined by the parameters used at the time the file system was made. For JFS file systems that are enabled for large files, the maximum file size is slightly less than 64 gigabytes (0xff840). For all other JFS file systems, the maximum file size is 2Gb-1 (0x7fff). Attempts to write a file in excess of the maximum file size in any file system format will fail, and errno will be set to EFBIG. (I'm not under AIX, but EFBIG is 27 here) What does test_largefile output? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] test_io error on AIX
Sébastien Sablé sa...@users.sourceforge.net added the comment: test_largefile complains about the filesystem having no largefile support. It is probably the case, I will ask a sysadmin, and see if he can get me a file system with large file support so that I can test this feature. ./python -Wd -E -bb ./Lib/test/test_largefile.py Traceback (most recent call last): File ./Lib/test/test_largefile.py, line 163, in test_main f.write(b'x') IOError: [Errno 27] File too large During handling of the above exception, another exception occurred: Traceback (most recent call last): File ./Lib/test/test_largefile.py, line 192, in module test_main() File ./Lib/test/test_largefile.py, line 168, in test_main raise unittest.SkipTest(filesystem does not have largefile support) unittest.case.SkipTest: filesystem does not have largefile support [81125 refs] In the meantime, this test should probably be skipped just like in test_largefile.py and the patch with _LARGE_FILES should probably be applied too. Merci pour l'aide -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] Broken large file support on AIX
Changes by Sébastien Sablé sa...@users.sourceforge.net: -- title: test_io error on AIX - Broken large file support on AIX ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] Broken large file support on AIX
Antoine Pitrou pit...@free.fr added the comment: Yes, I think the skipping code in test_largefile should be factored out and used both in test_io and test_largefile (to be honest I don't know why test_io has large file tests as well; perhaps I should merge them together). -- stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
R. David Murray rdmur...@bitdance.com added the comment: Duh. After writing all that you'd think I'd have seen my mistake. That's what reviews are for. So I guess it should be BaseException, since the most likely one is keyboard interrupt and this would prevent a corrupted mailbox in that case. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] Broken large file support on AIX
Sébastien Sablé sa...@users.sourceforge.net added the comment: Also: is it OK if I open a new issue for each broken unit test on AIX even if I have not investigated them at the moment? I have a dozen broken unit tests on AIX that need to be investigated, but I don't want to spam the bug tracker followers too much. So tell me if it is a good thing to report each problem as soon as possible or if I should do it step by step. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11184] Broken large file support on AIX
Antoine Pitrou pit...@free.fr added the comment: is it OK if I open a new issue for each broken unit test on AIX even if I have not investigated them at the moment? Yes. That way they get recorded somewhere and other people can chime in. If you plan to investigate them you can add a sentence saying so. Thanks! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11184 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11188] test_time error on AIX
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following errors on test_time on AIX:
==
ERROR: test_mktime (test.test_time.TestAsctime4dyear)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_time.py,
line 351, in test_mktime
self.assertEqual(time.mktime(tt), t)
OverflowError: mktime argument out of range
==
ERROR: test_mktime (test.test_time.TestStrftime4dyear)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_time.py,
line 351, in test_mktime
self.assertEqual(time.mktime(tt), t)
OverflowError: mktime argument out of range
==
ERROR: test_mktime (test.test_time.Test4dyearBool)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_time.py,
line 351, in test_mktime
self.assertEqual(time.mktime(tt), t)
OverflowError: mktime argument out of range
==
FAIL: test_negative (test.test_time.TestStrftime4dyear)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_time.py,
line 337, in test_negative
self.assertIn(text, ('-1', '-001'))
AssertionError: '000/' not found in ('-1', '-001')
--
Ran 42 tests in 1.217s
FAILED (failures=1, errors=3)
Haven't investigated yet.
--
messages: 128396
nosy: sable
priority: normal
severity: normal
status: open
title: test_time error on AIX
versions: Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11188
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11189] test_resource error on AIX
New submission from Sébastien Sablé sa...@users.sourceforge.net: I have the following error on test_resource on AIX: test_resource test test_resource failed -- Traceback (most recent call last): File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_resource.py, line 28, in test_fsize_ismax self.assertEqual(resource.RLIM_INFINITY, max) AssertionError: 2147483647 != 1073741312 I haven't investigated yet. -- messages: 128397 nosy: sable priority: normal severity: normal status: open title: test_resource error on AIX versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11189 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11190] test_locale error on AIX
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following errors on test_locale on AIX:
==
FAIL: test_strcoll_with_diacritic (test.test_locale.TestEnUSCollation)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_locale.py,
line 364, in test_strcoll_with_diacritic
self.assertLess(locale.strcoll('à', 'b'), 0)
AssertionError: 1 not less than 0
==
FAIL: test_strxfrm_with_diacritic (test.test_locale.TestEnUSCollation)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_locale.py,
line 367, in test_strxfrm_with_diacritic
self.assertLess(locale.strxfrm('à'), locale.strxfrm('b'))
AssertionError: '\u01e2\u0100' not less than '\u0164\u0100'
--
Ran 35 tests in 0.020s
FAILED (failures=2)
I haven't investigated yet.
--
messages: 128398
nosy: sable
priority: normal
severity: normal
status: open
title: test_locale error on AIX
versions: Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11190
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11191] test_search_cpp error on AIX (aith xlc)
New submission from Sébastien Sablé sa...@users.sourceforge.net: I have the following error in distutils on AIX. == ERROR: test_search_cpp (distutils.tests.test_config_cmd.ConfigTestCase) -- Traceback (most recent call last): File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/unixccompiler.py, line 166, in preprocess self.spawn(pp_args) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/ccompiler.py, line 911, in spawn spawn(cmd, dry_run=self.dry_run) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/spawn.py, line 34, in spawn _spawn_posix(cmd, search_path, dry_run=dry_run) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/spawn.py, line 138, in _spawn_posix % (cmd[0], exit_status)) distutils.errors.DistutilsExecError: command 'xlc' failed with exit status 40 During handling of the above exception, another exception occurred: Traceback (most recent call last): File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/tests/test_config_cmd.py, line 47, in test_search_cpp match = cmd.search_cpp(pattern='xxx', body='// xxx') File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/command/config.py, line 203, in search_cpp src, out = self._preprocess(body, headers, include_dirs, lang) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/command/config.py, line 126, in _preprocess self.compiler.preprocess(src, out, include_dirs=include_dirs) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/distutils/unixccompiler.py, line 168, in preprocess raise CompileError(msg) distutils.errors.CompileError: command 'xlc' failed with exit status 40 I haven't investigated yet. -- assignee: tarek components: Distutils messages: 128399 nosy: eric.araujo, sable, tarek priority: normal severity: normal status: open title: test_search_cpp error on AIX (aith xlc) versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11191 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11191] test_search_cpp error on AIX (with xlc)
Changes by Sébastien Sablé sa...@users.sourceforge.net: -- title: test_search_cpp error on AIX (aith xlc) - test_search_cpp error on AIX (with xlc) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11191 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11192] test_socket error on AIX
New submission from Sébastien Sablé sa...@users.sourceforge.net: I have the following error in test_socket on AIX: == FAIL: testGetaddrinfo (__main__.GeneralModuleTests) -- Traceback (most recent call last): File ./Lib/test/test_socket.py, line 640, in testGetaddrinfo self.assertEqual(socktype, socket.SOCK_STREAM) AssertionError: 0 != 1 -- Ran 158 tests in 16.904s FAILED (failures=1, skipped=4) Traceback (most recent call last): File ./Lib/test/test_socket.py, line 2012, in module test_main() File ./Lib/test/test_socket.py, line 2008, in test_main support.run_unittest(*tests) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/support.py, line 1145, in run_unittest _run_suite(suite) File /san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/support.py, line 1128, in _run_suite raise TestFailed(err) test.support.TestFailed: Traceback (most recent call last): File ./Lib/test/test_socket.py, line 640, in testGetaddrinfo self.assertEqual(socktype, socket.SOCK_STREAM) AssertionError: 0 != 1 [119732 refs] I haven't investigated yet. -- messages: 128400 nosy: sable priority: normal severity: normal status: open title: test_socket error on AIX versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11192] test_socket error on AIX
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11189] test_resource error on AIX
Sébastien Sablé sa...@users.sourceforge.net added the comment: This is a duplicate of issue 678264. -- resolution: - duplicate status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11189 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11193] test_subprocess error on AIX
New submission from Sébastien Sablé sa...@users.sourceforge.net:
The following tests fail in test_subprocess on AIX:
==
FAIL: test_undecodable_env (test.test_subprocess.POSIXProcessTestCase)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_subprocess.py,
line 1039, in test_undecodable_env
self.assertEqual(stdout.decode('ascii'), ascii(value))
AssertionError: 'abc\\xff' != 'abc\\udcff'
- 'abc\xff'
? ^
+ 'abc\udcff'
? ^^^
==
FAIL: test_undecodable_env (test.test_subprocess.ProcessTestCasePOSIXPurePython)
--
Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_subprocess.py,
line 1039, in test_undecodable_env
self.assertEqual(stdout.decode('ascii'), ascii(value))
AssertionError: 'abc\\xff' != 'abc\\udcff'
- 'abc\xff'
? ^
+ 'abc\udcff'
? ^^^
--
Ran 267 tests in 366.280s
FAILED (failures=2, skipped=22)
I haven't investigated yet.
--
messages: 128402
nosy: sable
priority: normal
severity: normal
status: open
title: test_subprocess error on AIX
versions: Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11193
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11193] test_subprocess error on AIX
Antoine Pitrou pit...@free.fr added the comment: Perhaps related to the test_locale failure in issue11190. -- nosy: +haypo, pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11193 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11188] test_time error on AIX
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +belopolsky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11188 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9298] binary email attachment issue with base64 encoding
R. David Murray rdmur...@bitdance.com added the comment: Yves: thanks for the patches. If you feel like redoing the test one as a patch against Lib/email/test/test_email.py, that would be great. I'd suggest having the test just split the lines and do assertLessEqual(max([len(x) for x in lines]), 76) or something along those lines. As for the fix, encoders used to use encodebytes, but it tacks on a trailing newline that, according to the old code (see r57800) is unwanted. So perhaps we need to revert that part of r57800 instead. -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9298 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9920] test_cmath on atan fails on AIX
Mark Dickinson dicki...@gmail.com added the comment: Here's a patch. -- keywords: +patch Added file: http://bugs.python.org/file20745/issue9920.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9920 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11193] test_subprocess error on AIX
STINNER Victor victor.stin...@haypocalc.com added the comment: test_undecodable_code() in test_cmd_line had a similar issue: on FreeBSD, Solaris and Mac OS X, even if the locale is C (and nl_langinfo(CODESET) announces ASCII), _Py_char2wchar() (mbstowcs) decoded b'\xff' as '\xff' (use ISO-8859-1 encoding). To fix the test, I just patched the test to accept both results: b'\xff' may be decoded as '\udcff' or '\xff'. test_undecodable_env does something like: os.environb[b'test']=b'abc\xff', but os.getenv() decodes b'abc\xff' as 'abc\xff' instead of 'abc\udcff' even if LC_ALL=C. I don't understand why the test pass on FreeBSD, Solaris and Mac OS X, but not on AIX. It would be interesting to get the locale encoding of the child process using LC_ALL=C. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11193 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11190] test_locale error on AIX
STINNER Victor victor.stin...@haypocalc.com added the comment: See also issue #11193 (another locale issue on AIX). -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11190 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1602] windows console doesn't print or input Unicode
Changes by Andrew Dunbar hippytr...@gmail.com: -- nosy: +hippietrail ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1602 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2504] Add gettext.pgettext() and variants support
Changes by Sascha Silbe sascha-web-bugs.python@silbe.org: -- nosy: +sascha_silbe ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2504 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
R. David Murray rdmur...@bitdance.com added the comment: Revised patch using BaseException. -- Added file: http://bugs.python.org/file20746/mailbox_cleanup2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11194] lock.__exit__ == lock.release should be False
New submission from O.C. oc-spa...@laposte.net: Hello, if 'lock' is a threading.Lock, the functions lock.__exit__() and lock.release() are different. The former takes 3 arguments, while the latter takes no argument. However, lock.__exit__ == lock.release returns True. Shouldn't it return False ? Best regards, O.C. Details: In [20]: lock=threading.Lock() In [21]: lock.acquire() In [22]: lock.__exit__(None,None,None) In [23]: lock.locked() Out[23]: False In [24]: lock.acquire() In [25]: lock.release(None,None,None) TypeError: release() takes no arguments (3 given) In [26]: lock.__exit__==lock.release Out[26]: True -- components: Library (Lib) messages: 128409 nosy: dghjfrdj priority: normal severity: normal status: open title: lock.__exit__ == lock.release should be False type: behavior versions: Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11194 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1704474] optparse tests fail under Jython
Éric Araujo mer...@netwok.org added the comment: Hi Sandro. I think you may have closed too fast here: optparse is deprecated in docs only, it’s not the recommendation anymore, but IIUC bugs should still be fixed. A year and a half is sadly not a very long time for a Python bug, time is usually not a criterion for closing. David, please correct any inaccuracy in my message :) -- nosy: +eric.araujo, r.david.murray -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1704474 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
SilentGhost ghost@gmail.com added the comment: compileall.rst diff doesn't seem to belong in that patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11195] next fixer fooled by trailing cheracters
New submission from Daniele Varrazzo p...@develer.com: An expression such as x = i.next()[0] is not fixed by 2to3 in Python 3.1. x = (i.next())[0] works instead. https://github.com/dvarrazzo/psycopg/commit/9e9c22163706b0fffb9da67fe50ea23f91fe1c72 -- components: 2to3 (2.x to 3.0 conversion tool) messages: 128412 nosy: piro priority: normal severity: normal status: open title: next fixer fooled by trailing cheracters versions: Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11195 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
R. David Murray rdmur...@bitdance.com added the comment: Woops. Thanks for catching that. Will fix before commit. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11194] lock.__exit__ == lock.release should be False
R. David Murray rdmur...@bitdance.com added the comment: Well, under the (C) hood, it is in fact the same method, it just takes a variable number of arguments (and ignores them, in the __exit__ case). The fact that the arguments are rejected in the 'release' case is because of how the C function is defined as a Python method using the C API. So the result of the boolean test is more accurate than a False report would be, although not precise. I don't *think* there is any bug to fix here. Do you have a use case that this impacts? -- nosy: +r.david.murray versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11194 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1704474] optparse tests fail under Jython
R. David Murray rdmur...@bitdance.com added the comment: Making the tests pass on Jython is certainly worthwhile, if anyone wants to do it. At a quick glance it looks like the optparse tests just need to be updated and made a bit more lenient. Since Jython is lagging CPython by so much a fix isn't going to help them for a quite a while even if it gets done now. Really, this is a candidate bug to be moved to the library tracker if/when the CPython/library split happens. So I suppose we should leave it open in anticipation of that move happening some day :) -- resolution: wont fix - status: closed - open type: feature request - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1704474 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11196] add possibility for returning value the way Matlab does it
New submission from Geza kge...@gmail.com: It would be nice if you could write a function like this (besides, of course, the current way): def result=functionname(params): ... result=something It would suffice for most functions, since you usually always return one type of value, and it can be very convenient in certain cases. This is the way it is done e.g. in Matlab. Advantages: - You can easily see what the function returns (e.g. by writing a tuple as the return value), without having to read the function body, or without hoping to find it in the comments. - You can initialize the return values, and then care about the cases where they change. - If you change the setup of the return value (e.g. insert a new item into the tuple), you do not need to change the return statement at possibly several places in the function body. Disadvantages: - I suggest it as an addition, so there isn't really. One person may decide to use one way, one the other. - Of course, if you mix using the two ways, you may need to look at the function header to see which one you used. Some more details to the idea: - The return values are initialized to None. - You can use the return statement just as before, but without arguments, to return from anywhere in the code. - If you specify arguments to the return statement, Python stops with an exception. The idea at this stage of Python development may be surprising, but I hope that nevertheless you will consider the idea seriously. Thanks, and best regard! -- components: Interpreter Core messages: 128416 nosy: Geza priority: normal severity: normal status: open title: add possibility for returning value the way Matlab does it type: feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11196 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11196] add possibility for returning value the way Matlab does it
Brian Curtin cur...@acm.org added the comment: A change like this would need to go through, at the least, the python-ideas mailing list. Please submit your idea there first. -- nosy: +brian.curtin resolution: - rejected stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11196 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11195] next fixer fooled by trailing cheracters
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11195 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10423] s/args/options in arpgarse Upgrading optparse code
Sandro Tosi sandro.t...@gmail.com added the comment: I've prepared a simple patch: what do you think about it? -- stage: needs patch - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10423 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10423] s/args/options in arpgarse Upgrading optparse code
Sandro Tosi sandro.t...@gmail.com added the comment: now even with patch attached :) -- keywords: +patch Added file: http://bugs.python.org/file20747/issue10423.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10423 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11197] information leakage with SimpleHTTPServer
New submission from Brett Cannon br...@python.org: As reported to the PSRT: Python's SimpleHTTPServer class is a simple HTTP server, documented as serving up the content of the pwd and below readonly via GET and HEAD commands: $ python -m SimpleHTTPServer Serving HTTP on 0.0.0.0 port 8000 ... However, by inserting ../ path fragments within the path section of the URL, it's possible to traverse other directories within the filesystem. For example: lynx localhost:8000/../../../../.. shows 5 directories above in the directory structure. I was also able to browse /proc and /sys on this example using: lynx localhost:8000/../../../../../../../../proc lynx localhost:8000/../../../../../../../../sys (by browsing to find the correct number of .. entries to locate the root directory); arguable this could be leaking much more information about the host than the administrator might be expecting (e.g. other programs being executed on the host, command-line arguments of those programs etc) This has been fixed in CGIHTTPServer; see http://bugs.python.org/issue2254 and: http://svn.python.org/view?view=revrevision=71303 Guido recommended to not make this secret since no one should be using SimpleHTTPServer in production. He also said this should get fixed. -- components: Library (Lib) messages: 128420 nosy: barry, benjamin.peterson, brett.cannon, dmalcolm, georg.brandl, gps priority: release blocker severity: normal stage: needs patch status: open title: information leakage with SimpleHTTPServer type: security versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11197 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11169] compileall doesn't support PEP 383 (undecodable paths/filenames)
Éric Araujo mer...@netwok.org added the comment: I agree that quotes help debugging, so +1 for repr (or !r, not sure which ones reads better). Not sure this can make it into stable branches. -- nosy: +eric.araujo title: compileall doesn't support the PEP 383 (undecodable paths/filenames) - compileall doesn't support PEP 383 (undecodable paths/filenames) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11169 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11164] xml shouldn't use _xmlplus
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11164 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11198] re sub subn backreferrence too few replacements
New submission from muxum mxgn...@gmx.de: #download/try this: http://ideone.com/QA6Fg from re import * s = 'a-b\na-b\nc-b\nc-b\na-d\na-d\ne-b\ne-b\na-f\na-f\ng-b\ng-b\na-h\na-h\ni-b\ni-b\na-j\na-j\nk-b\nk-b\n' res = subn(r(.*\n)(\1)+,rreplaced:\1,s,M) print(output: + res[0]) print(replace count: %d % res[1]) # if it works right the next print wont show if res[1] == 8: print(WEIRD: too few replacements (+str(res[1])+)) #i'd expect this to replace all ocurrences not only the first 8 times -- components: Regular Expressions messages: 128422 nosy: muxum priority: normal severity: normal status: open title: re sub subn backreferrence too few replacements type: behavior versions: Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11198 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11197] information leakage with SimpleHTTPServer
Dave Malcolm dmalc...@redhat.com added the comment: CVE-2011-0705 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11197 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11197] information leakage with SimpleHTTPServer
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11197 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11126] Wave.py does not always write proper length in header
Terry J. Reedy tjre...@udel.edu added the comment: I agree that the _sampwidth multiplier is needed regardless of endianness. The simplest option would be to pull the _datawritten statement out of the alternation, making the code read if self._sampwidth 1 and big_endian: import array data = array.array(_array_fmts[self._sampwidth], data) data.byteswap() data.tofile(self._file) else: self._file.write(data) self._datawritten = self._datawritten + len(data) * self._sampwidth Note: while _sampwidth is initialized to 0, _ensure_header_written() checks that it is not 0, and it is used elsewhere as a divisor. The above adds a usually unneeded multiply by 1, but the alternative requires duplication of _file.write and two _datawritten statements if self._sampwidth 1: if big_endian: import array data = array.array(_array_fmts[self._sampwidth], data) data.byteswap() data.tofile(self._file) else: # little_endian self._file.write(data) self._datawritten = self._datawritten + len(data) * self._sampwidth else: # _sampwidth == 1 self._file.write(data) self._datawritten = self._datawritten + len(data) This module is new to me. Can you think of any way to test this issue, perhaps by writing to StringIO file? This is not a heavily tested module ;-) In 3.3, the openfp synonym for open could perhaps be deprecated. -- nosy: +terry.reedy versions: +Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11126 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11194] lock.__exit__ == lock.release should be False
O.C. oc-spa...@laposte.net added the comment: Do you have a use case that this impacts? No, I can live with it. It was rather a point about clarity and consistency. For example, the difference between Lock and RLock: lock.__exit__==lock.release- True rlock.__exit__==rlock.release - False We came on that topic when using 'with' statements with exceptions and 'returns'. I wanted to check and understand the details, and I was confused by the fact that: - three arguments will be given to lock.__exit__() - lock.__exit__ is the same as lock.release - lock.release takes no argument These propositions are all true, but seem contradictory. The meaning of the same is not obvious in this case. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11194 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11188] test_time error on AIX
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11188 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10423] s/args/options in arpgarse Upgrading optparse code
Steven Bethard steven.beth...@gmail.com added the comment: Looks good to me. This is a doc fix, so it could go into 3.2 and 2.7 as well as 3.3. -- versions: +Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10423 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11135] Redundant doc field in TypeSpec
Martin v. Löwis mar...@v.loewis.de added the comment: Thansk for the review. Committed as r88400. -- resolution: - accepted status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11135 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11134] Add missing type slots
Martin v. Löwis mar...@v.loewis.de added the comment: Thanks for the review. Committed as r88401. -- resolution: - accepted status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11134 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11182] pydoc.Scanner class not used by anything
Terry J. Reedy tjre...@udel.edu added the comment: After saying that pydoc is used by help(), its documentation only tells how to run it standalone. help(pydoc) basically says the same, and does not mention any internals, because of __all__ = ['help'], which the author understood to define the public interface. So it seems to me that everything other than help() can be considered private and changeable. Scanner does look like a leftover orphan. -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11182 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11180] More efficient nlargest()/nsmallest()
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: FWIW, I've attached benchmarking code for all three approaches (the current approach and the two proposals). -- Added file: http://bugs.python.org/file20748/heapq_benchmark.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11180 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11194] lock.__exit__ == lock.release should be False
R. David Murray rdmur...@bitdance.com added the comment: Yeah, sometimes you just have to read the source. Previous to Python3.2, RLock was implemented in Python, and the two methods are actually different methods there. In Python3.2, rlock.release == rlock.__exit__ is True. -- resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11194 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
R. David Murray rdmur...@bitdance.com added the comment: Committed in r88403. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
R. David Murray rdmur...@bitdance.com added the comment: Decided to backport the fix to 2.7, even though the tests won't backport. r88406. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11171] Python 2.7.1 does not start when ./configure is used with --prefix != --exec-prefix
Changes by Barry A. Warsaw ba...@python.org: -- assignee: tarek - barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11171 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11171] Python 2.7.1 does not start when ./configure is used with --prefix != --exec-prefix
Barry A. Warsaw ba...@python.org added the comment: The suggested change works for me, both when prefix == exec_prefix and when it doesn't. All standard tests pass, so the fix should be committed. I'm holding off on doing that to see whether it's applicable to other versions, though if 3.2 is affected, Georg will have to pronounce on the patch. (My opinion is that it can easily wait for 3.2.1). -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11171 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11198] re sub subn backreferrence too few replacements
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +mrabarnett ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11198 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11198] re sub subn backreferrence too few replacements
Matthew Barnett pyt...@mrabarnett.plus.com added the comment: Argument 4 of re.subn(...) is 'count', the maximum number of replacements to perform, but you're passing in the MULTILINE flag, which happens to have the integer value 8, hence you're limiting the maximum number of replacements to 8. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11198 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11197] information leakage with SimpleHTTPServer
Changes by Gregory P. Smith g...@krypto.org: -- assignee: - gregory.p.smith nosy: +gregory.p.smith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11197 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11198] re sub subn backreferrence too few replacements
Changes by R. David Murray rdmur...@bitdance.com: -- resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11198 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10999] os.chflags refers to stat constants, but the constants are not documented in the stat module
Michal Nowikowski godf...@gmail.com added the comment: Is this patch ok? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10999 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11171] Python 2.7.1 does not start when ./configure is used with --prefix != --exec-prefix
Georg Brandl ge...@python.org added the comment: That is my opinion as well. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11171 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11116] mailbox and email errors
Georg Brandl ge...@python.org added the comment: Thanks! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11197] information leakage with SimpleHTTPServer
Georg Brandl ge...@python.org added the comment: This would be nice to fix in 3.2; however, since SimpleHTTPServer is not meant to be used in production, and it's not a regression, I will not hold up the release schedule for it. I'd need to see a patch for deciding. -- priority: release blocker - deferred blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11197 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11082] ValueError: Content-Length should be specified
Georg Brandl ge...@python.org added the comment: Lowering priority and making a doc issue now that the code change has been made. -- components: +Documentation -Library (Lib) priority: deferred blocker - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11082 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1028] Tkinter binding involving Control-spacebar raises unicode error
Michael Strein mgstr...@gmail.com added the comment: Do we know the status of this issue? Have not seen update in four months. Currently is a major headache on my linux box. -- nosy: +mgstrein ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1028 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
