[issue21686] IDLE - Test hyperparser
Roundup Robot added the comment: New changeset 5063df721985 by Terry Jan Reedy in branch '2.7': Issue #21686: idlelib/HyperParser.py - Update docstrings and comments and http://hg.python.org/cpython/rev/5063df721985 New changeset ddf15cf0db72 by Terry Jan Reedy in branch '3.4': Issue #21686: idlelib/HyperParser.py - Update docstrings and comments and http://hg.python.org/cpython/rev/ddf15cf0db72 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21686 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19362] Documentation for len() fails to mention that it works on sets
Roundup Robot added the comment: New changeset 95d487abbfd8 by Terry Jan Reedy in branch '2.7': Issue #19362: Tweek len() doc and docstring to expand the indicated range of http://hg.python.org/cpython/rev/95d487abbfd8 New changeset 8fcbe41e1242 by Terry Jan Reedy in branch '3.4': Issue #19362: Tweek len() doc and docstring to expand the indicated range of http://hg.python.org/cpython/rev/8fcbe41e1242 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19362 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19362] Documentation for len() fails to mention that it works on sets
Changes by Terry J. Reedy tjre...@udel.edu: -- resolution: - fixed stage: - resolved status: open - closed versions: +Python 2.7, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19362 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21559] OverflowError should not happen for integer operations
Roundup Robot added the comment: New changeset 9ba324a20bad by Terry Jan Reedy in branch '3.4': Issue #21559: Add alternative (historical) reason for OverflowError. http://hg.python.org/cpython/rev/9ba324a20bad -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21559 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21559] OverflowError should not happen for integer operations
Changes by Terry J. Reedy tjre...@udel.edu: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21559 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21559] OverflowError should not happen for integer operations
Changes by Terry J. Reedy tjre...@udel.edu: -- resolution: - fixed stage: - resolved ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21559 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19495] Enhancement for timeit: measure time to run blocks of code using 'with'
Nick Coghlan added the comment: I'm with Guido on this one - I don't believe there's a clean sweet spot to hit. There *might* be a plausible case to be made for tracing functionality in the logging module, but even there the number of options multiplies fast enough that writing your own context manager would likely be easier than learning a new API with lots of settings to tweak. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19495 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20319] concurrent.futures.wait() can block forever even if Futures have completed
Sebastian Kreft added the comment: Any ideas how to debug this further? In order to overcome this issue I have an awful workaround that tracks the maximum running time of a successful task, and if any task has been running more than x times that maximum I consider it defunct, and increase the number of concurrent allowed tasks. However, if the problem persist, I eventually will have lot of zombie tasks, which will expose some additional problems. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20319 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21776] distutils.upload uses the wrong order of exceptions
New submission from Claudiu Popa: Hi. Currently, distutils.command.upload has this code: try: result = urlopen(request) status = result.getcode() reason = result.msg except OSError as e: self.announce(str(e), log.ERROR) return except HTTPError as e: status = e.code reason = e.msg This is wrong because HTTPError is a subclass of OSError and OSError branch will be chosen in case HTTPError is raised. The HTTPError branch was added in 4373f0e4eb21, but after a while socket.error became an alias for OSError, as well for HTTPError. This patch also adds a `return` in order to prevent an UnboundLocalError (found in issue10367 as well), but it can be removed if other solutions are preferable. -- components: Distutils files: distutils.patch keywords: patch messages: 220705 nosy: Claudiu.Popa, dstufft, eric.araujo priority: normal severity: normal status: open title: distutils.upload uses the wrong order of exceptions type: behavior versions: Python 3.5 Added file: http://bugs.python.org/file35653/distutils.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21776 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20319] concurrent.futures.wait() can block forever even if Futures have completed
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: -haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20319 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21679] Prevent extraneous fstat during open()
Bohuslav Slavek Kabrda added the comment:
So, as pointed out by haypo, blksize_t is actually signed long on Linux. This
means that my patch (as well as the current code) is not right.
Both with and without my patch, io_open function uses int to store blksize_t
and it also passes it to one of PyBuffered{Random,Reader,Writer}_Type. These
three however use Py_ssize_t, which is inconsistent with io_open, and it's not
correct, too.
I'm unsure how to proceed here - should I fix buffer size types throughout the
_io module to long and submit one big patch? It doesn't feel right to put two
not-very-related changes into one patch (I'm afraid that changing buffer sizes
to long everywhere will result in a rather large patch). Or should I first
submit a patch that fixes the long usage and then rebase the patch attached to
this issue on top of it?
Thanks a lot.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21679
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21669] Custom error messages when print exec are used as statements
Roundup Robot added the comment: New changeset 2b8cd2bc2745 by Nick Coghlan in branch '3.4': Issue #21669: Special case print exec syntax errors http://hg.python.org/cpython/rev/2b8cd2bc2745 New changeset 36057f357537 by Nick Coghlan in branch 'default': Merge issue #21669 from 3.4 http://hg.python.org/cpython/rev/36057f357537 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21669 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21669] Custom error messages when print exec are used as statements
Nick Coghlan added the comment: I went ahead and committed the v2 patch, as I think it's already an improvement over the generic message. Any further significant tweaks to the heuristics or changes to the error messages can be handled in separate issues. -- resolution: - fixed stage: - resolved status: open - closed type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21669 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9693] asynchat push_callable() patch
Giampaolo Rodola' added the comment: Yeah, I don't think this is worth it anymore. Closing as won't fix. -- assignee: - giampaolo.rodola resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9693 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19628] maxlevels -1 on compileall for unlimited recursion
Changes by Claudiu Popa pcmantic...@gmail.com: -- stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19628 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21741] Convert most of the test suite to using unittest.main()
Michael Foord added the comment: I haven't reviewed the patch in detail, but I've had a scan through and it looks *great*. A quick and dirty check that it's correct is to compare the number of tests run before and after the patch - and if the numbers differ verifying that it's for good reasons (i.e. only *extra* tests being run and none being skipped / missed). If that's the case I'd be strongly in favour of applying. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21741 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21777] Separate out documentation of binary sequence methods
New submission from Nick Coghlan: There are currently no dedicated docs for the bytes and bytearray methods - the relevant section just refers back to the str methods. This isn't sufficient, since the str methods cover of lot of stuff related to Unicode that isn't relevant to the binary sequence types, and it doesn't cleanly cover the differences either (like the fact that several methods accept integers). I've started work on a patch that documents the binary APIs explicitly, although bytes and bytearray still share docs. The methods are grouped into three categories: - work with arbitrary binary data - assume ASCII compatibility by default, but can still be used with arbitrary binary data when given suitable arguments - can only be used safely with data in an ASCII compatible format I've worked through and updated the new entries for the first category, but the latter two categories are still just copy-and-paste from the str docs. -- assignee: ncoghlan components: Documentation files: separate_binary_sequence_docs.diff keywords: patch messages: 220711 nosy: ncoghlan priority: normal severity: normal status: open title: Separate out documentation of binary sequence methods type: enhancement versions: Python 3.4, Python 3.5 Added file: http://bugs.python.org/file35654/separate_binary_sequence_docs.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21777 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20319] concurrent.futures.wait() can block forever even if Futures have completed
Glenn Langford added the comment: Any ideas how to debug this further? Wherever the cause of the problem might live, and to either work around it or gain additional information, here is one idea to consider. Do you need to submit your Futures just two at a time, and tightly loop every 15s? Why not submit a block of a larger number and wait for the block with as_completed(), logging for each completion. Then submit another block when they are all done. To control how many run at one time, create the Executor with max_workers=2 for example. (I had an app that ran 1,000 futures in this way, which worked fine). In general I suggest to only timeout when there is really a problem, not as an expected event. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20319 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21759] URL Typo in Documentation FAQ
Roundup Robot added the comment: New changeset f254ceec0d45 by Jesus Cea in branch '2.7': Closes #21759: URL Typo in Documentation FAQ http://hg.python.org/cpython/rev/f254ceec0d45 -- nosy: +python-dev resolution: - fixed stage: needs patch - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21759 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21759] URL Typo in Documentation FAQ
Jesús Cea Avión added the comment: Thanks! -- nosy: +jcea ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21759 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20319] concurrent.futures.wait() can block forever even if Futures have completed
Sebastian Kreft added the comment: I'm running actually millions of tasks, so sending them all at once will consume much more resources than needed. The issue happens no only with 2 tasks in parallel but with higher numbers as well. Also your proposed solution, has the problem that when you are waiting for the last tasks to finish you lose some parallelism. In any case, it seems to me that there's some kind of race condition preventing the task to finish, so if that's true the same could happen with as_completed. On Jun 16, 2014 2:00 PM, Glenn Langford rep...@bugs.python.org wrote: Glenn Langford added the comment: Any ideas how to debug this further? Wherever the cause of the problem might live, and to either work around it or gain additional information, here is one idea to consider. Do you need to submit your Futures just two at a time, and tightly loop every 15s? Why not submit a block of a larger number and wait for the block with as_completed(), logging for each completion. Then submit another block when they are all done. To control how many run at one time, create the Executor with max_workers=2 for example. (I had an app that ran 1,000 futures in this way, which worked fine). In general I suggest to only timeout when there is really a problem, not as an expected event. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20319 ___ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20319 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20319] concurrent.futures.wait() can block forever even if Futures have completed
Glenn Langford added the comment: Under the hood, the behaviour of as_completed is quite different. So there is no guarantee it would behave the same. In any event, with millions of tasks you might consider Celery (I haven't used it myself): http://www.celeryproject.org -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20319 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20928] xml.etree.ElementInclude does not include nested xincludes
R. David Murray added the comment: Since there is no guarantee anyone is going to tackle the job of reviewing all the changes for whatsnew entries, I prefer that we get in the habit of creating the entries as we go along. As for the versionchanged...if you can find where include is documented, that would work :) The recursion still needs to be addressed (it is addressed in the lxml version Stefan linked to). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20928 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5207] extend strftime/strptime format for RFC3339 and RFC2822
R. David Murray added the comment: Yes, I think that is appropriate. Note that you also get RFC822 parsing for datetime via email.util.parsedate_to_datetime. (I'm not sure why the OP thought that using the email utilities to parse email-standard dates was not [a] very good way.) -- superseder: - datetime: add ability to parse RFC 3339 dates and times ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5207 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5207] extend strftime/strptime format for RFC3339 and RFC2822
Changes by R. David Murray rdmur...@bitdance.com: -- resolution: - duplicate stage: test needed - resolved ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5207 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21741] Convert most of the test suite to using unittest.main()
Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21741 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21741] Convert most of the test suite to using unittest.main()
R. David Murray added the comment: +1 from me (after verification), which should probably go without saying since I'm the one that started this ball rolling by making regrtest work with unittest discovery :) I think the potential disruption to existing patches and any forward porting issues (I expect them to be minor if they occur) are worth it just for the fact that we won't be missing tests via incorrect or forgotten updates to the list of tests to run. Thanks for working on this, Zach, as well as your previous work that set up for this. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21741 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21205] Add __qualname__ attribute to Python generators and change default __name__
Roundup Robot added the comment: New changeset aa85e8d729ae by Victor Stinner in branch 'default': Issue #21205: Add a new ``__qualname__`` attribute to generator, the qualified http://hg.python.org/cpython/rev/aa85e8d729ae -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21205 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21778] PyBuffer_FillInfo() from 3.3
New submission from Armin Rigo: Following the documentation at https://docs.python.org/3/c-api/buffer.html, if we write a custom object in C with a getbufferproc that simply returns PyBuffer_FillInfo(...), then it works fine up to Python 3.2 but segfaults in Python 3.3 depending on what we do with it. The segfault is caused by memoryobject.c:last_dim_is_contiguous(), which reads from the strides array without checking that it is not NULL. Attached the simplest example of C extension module I could make. When executing this: import xy m=memoryview(bytearray(babcdef)) m[:5] = xy.gm ...it segfaults in Python 3.3. (I'm told it works fine in 3.2 and segfaults in 3.4 as well, but didn't confirm it.) -- messages: 220721 nosy: arigo priority: normal severity: normal status: open title: PyBuffer_FillInfo() from 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21778 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21778] PyBuffer_FillInfo() from 3.3
Changes by Armin Rigo ar...@users.sourceforge.net: Added file: http://bugs.python.org/file35655/xymodule.c ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21778 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21205] Add __qualname__ attribute to Python generators and change default __name__
STINNER Victor added the comment: Ok, this issue is now fixed in Python 3.5. For Python 2.7 and 3.4, it may be possible to change how the generator name is set (from the function, not from the code object). It might break the backward compatibility, even if I don't think that anyone rely on the exact name of the generator, and the function name is more useful than the code name. What do you think for Python 2.7 and 3.4: would you be ok to change also the generator name? I can write a patch which adds a new gi_name but the name would not be modifiable to limit the incompatible changes. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21205 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21205] Add __qualname__ attribute to Python generators and change default __name__
Roundup Robot added the comment: New changeset 901a8265511a by Victor Stinner in branch 'default': Issue #21205: Fix unit tests http://hg.python.org/cpython/rev/901a8265511a -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21205 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21205] Add __qualname__ attribute to Python generators and change default __name__
Antoine Pitrou added the comment: Le 16/06/2014 10:20, STINNER Victor a écrit : What do you think for Python 2.7 and 3.4: would you be ok to change also the generator name? I can write a patch which adds a new gi_name but the name would not be modifiable to limit the incompatible changes. I don't think it is worthwhile. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21205 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21205] Add __qualname__ attribute to Python generators and change default __name__
STINNER Victor added the comment: Antoine Pitrou wrote: I don't think it is worthwhile. Ok, let's keep the issue closed then ;-) Thanks for the review Antoine. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21205 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21778] PyBuffer_FillInfo() from 3.3
Stefan Krah added the comment: The flags from mb_getbuf() have to be passed to PyBuffer_FillInfo(): return PyBuffer_FillInfo(view, (PyObject *)self, internal, 5, /*readonly=*/0, flags); The flags contain the actual request that the consumer sends to the buffer provider, so they cannot be hardcoded. In this example, memoryview sends the PyBUF_FULL request to mb_getbuf(). If the request is successful, it can assume non-NULL strides. Should the documentation be improved? -- nosy: +skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21778 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21741] Convert most of the test suite to using unittest.main()
Serhiy Storchaka added the comment: Some abstract test classes now are included in testing: Lib/test/test_calendar.py: MonthCalendarTestCase Lib/test/test_csv.py: TestCsvBase Lib/test/test_funcattrs.py: FuncAttrsTest Lib/test/test_sys_setprofile.py: TestCaseBase Lib/test/test_telnetlib.py: ExpectAndReadTestCase Lib/test/test_thread.py: BasicThreadTest Lib/test/test_unicodedata.py: UnicodeDatabaseTest (and may be other) Lib/test/test_enumerate.py, Lib/test/test_functools.py, Lib/test/test_list.py, Lib/test/test_peepholer.py, Lib/test/test_sort.py verified reference counting in verbose mode. Now this code is deleted. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21741 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21205] Add __qualname__ attribute to Python generators and change default __name__
Roundup Robot added the comment: New changeset 28b3b8b22654 by Victor Stinner in branch 'default': Issue #21205: Complete the versionchanged note in inspect documentation http://hg.python.org/cpython/rev/28b3b8b22654 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21205 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21741] Convert most of the test suite to using unittest.main()
Michael Foord added the comment: Those should be turned into mixins, or someone could implement issue 14534. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21741 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21778] PyBuffer_FillInfo() from 3.3
Armin Rigo added the comment: Ah! Thanks. I systematically missed the flags arguments passed in the getbufferproc function. (I thought I had to tell PyBuffer_FillInfo() what kind of format we actually provide, but it seems that the interface is the other way around. I don't see how I would implement a getbufferproc that forces a specific format, but I don't need that, so it's fine.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21778 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21778] PyBuffer_FillInfo() from 3.3
Changes by Armin Rigo ar...@users.sourceforge.net: -- resolution: - not a bug ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21778 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5207] extend strftime/strptime format for RFC3339 and RFC2822
Iakov Davydov added the comment: ISO 8601 is meant as the standard way to provide an unambiguous and well-defined method of representing dates and times. And the fact that it is widely used in e-mails doesn't make it e-mail specific. Incorporating function parsedate_to_datetime to email.util is acceptable. But the fact that standard python datetime library doesn't have means to parse ISO-approved time format seems strange to me. Once again: ISO 8601 is not a e-mail specific format. So I do not see a reason why parsing it is possible only via email. Using different time-parsing functions in different libraries seems like a bad design to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5207 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21779] est_multiprocessing_spawn fails when ran with -Werror
New submission from Serhiy Storchaka: $ ./python -Werror -m test.regrtest -v -m test_sys_exit test_multiprocessing_spawn == CPython 3.5.0a0 (default:149cc6364180+, Jun 12 2014, 15:45:54) [GCC 4.6.3] == Linux-3.8.0-36-generic-i686-with-debian-wheezy-sid little-endian == hash algorithm: siphash24 32bit == /home/serhiy/py/cpython/build/test_python_9425 Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, verbose=0, bytes_warning=0, quiet=0, hash_randomization=1, isolated=0) [1/1] test_multiprocessing_spawn test_sys_exit (test.test_multiprocessing_spawn.WithProcessesTestSubclassingProcess) ... Exception ignored in: _io.FileIO name='@test_9425_tmp' mode='wb' ResourceWarning: unclosed file _io.TextIOWrapper name='@test_9425_tmp' mode='w' encoding='UTF-8' FAIL == FAIL: test_sys_exit (test.test_multiprocessing_spawn.WithProcessesTestSubclassingProcess) -- Traceback (most recent call last): File /home/serhiy/py/cpython/Lib/test/_test_multiprocessing.py, line 483, in test_sys_exit self.assertEqual(f.read().rstrip(), str(reason)) AssertionError: [1, 2, 3]\nException ignored in: _io.Fi[123 chars]-8' != '[1, 2, 3]' - [1, 2, 3] ? - + [1, 2, 3]- Exception ignored in: _io.FileIO name='/dev/null' mode='rb' - ResourceWarning: unclosed file _io.TextIOWrapper name='/dev/null' mode='r' encoding='UTF-8' -- Ran 1 test in 1.247s FAILED (failures=1) test test_multiprocessing_spawn failed 1 test failed: test_multiprocessing_spawn -- components: Tests messages: 220732 nosy: jnoller, sbt, serhiy.storchaka priority: normal severity: normal status: open title: est_multiprocessing_spawn fails when ran with -Werror type: behavior versions: Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21779 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21779] test_multiprocessing_spawn fails when ran with -Werror
Changes by STINNER Victor victor.stin...@gmail.com: -- title: est_multiprocessing_spawn fails when ran with -Werror - test_multiprocessing_spawn fails when ran with -Werror ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21779 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8677] Modules needing PY_SSIZE_T_CLEAN
STINNER Victor added the comment: zlibmodule_ssize_t_clean.patch: Patch to make the zlib module ssize_t clean. The patch just defines PY_SSIZE_T_CLEAN, no # format is used. ./python -m test -v test_zlib test pass on my 64-bit Linux. -- keywords: +patch nosy: +haypo Added file: http://bugs.python.org/file35656/zlibmodule_ssize_t_clean.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8677 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8677] Modules needing PY_SSIZE_T_CLEAN
STINNER Victor added the comment: I just created the issue #21780 to make the unicodedata module 64-bit safe. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8677 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21780] make unicodedata module 64-bit safe
New submission from STINNER Victor: Follow-up of issue #8677: patch to make the unicodedata module 64-bit safe. -- files: unicodedata_64bit.patch keywords: patch messages: 220734 nosy: haypo priority: normal severity: normal status: open title: make unicodedata module 64-bit safe versions: Python 3.5 Added file: http://bugs.python.org/file35657/unicodedata_64bit.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21780 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21781] make _ssl module 64-bit clean
New submission from STINNER Victor: Follow-up of issue #8677: patch to make the _ssl module 64-bit clean. -- files: ssl_64bit.patch keywords: patch messages: 220736 nosy: haypo priority: normal severity: normal status: open title: make _ssl module 64-bit clean versions: Python 3.5 Added file: http://bugs.python.org/file35658/ssl_64bit.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21781 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8677] Modules needing PY_SSIZE_T_CLEAN
STINNER Victor added the comment: I created the issue #21781 to make the _ssl module 64-bit clean. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8677 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21772] platform.uname() not EINTR safe
STINNER Victor added the comment: Here is a different but similar patch for _syscmd_uname(): - use os.fsdecode() to use the locale encoding instead of latin-1 - use subprocess.DEVNULL to redirect errors to /dev/null - use with proc: to ensure that the subprocesss is cleaned in case of error -- keywords: +patch nosy: +haypo Added file: http://bugs.python.org/file35659/platform_syscmd_uname.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21772 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5207] extend strftime/strptime format for RFC3339 and RFC2822
R. David Murray added the comment: Supporting ISO 8601 is quite different from supporting RFC2822 dates, as far as I can see, and the latter clearly belongs in the email library (especially considering that RFC2822 parsing must follow Postel's Law and accept dirty data). If you want to open an issue to add ISO 8601 support (as opposed to RFC 3339's 8601 profile+timezone-deviation that is already covered by issue 15873) to datetime, go ahead. I haven't read enough to understand the details, so I don't know quite what that would mean, or how useful it would be. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5207 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5207] extend strftime/strptime format for RFC3339 and RFC2822
Iakov Davydov added the comment: I took a closer look for #15873. Apperently it solves the issue. Thanks, David. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5207 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15873] datetime: add ability to parse RFC 3339 dates and times
Changes by Iakov Davydov da...@myths.ru: -- nosy: +davydov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21778] PyBuffer_FillInfo() from 3.3
Stefan Krah added the comment: Yes, PyBuffer_FillInfo() is a bit confusing: The canonical usage *looks* as if flags were somehow used in the Py_buffer struct to mark a buffer as having certain capabilities: Modules/_io/bufferedio.c: - if (PyBuffer_FillInfo(buf, NULL, start, len, 0, PyBUF_CONTIG) == -1) return -1; memobj = PyMemoryView_FromBuffer(buf); What really goes on since Python 3.3 is that memobj is a memoryview with (shape,strides,format), since missing Py_buffer values are reconstructed. So all memoryviews -- when acting as an exporter as in this example -- have PyBUF_FULL capabilities. To make that clear, we should actually change the PyBUF_CONTIG in the above example to PyBUF_FULL. Then the mental model is: PyBuffer_FillInfo(..., PyBUF_FULL) ^ | Request full buffer to export. memobj ^ | Request anything from PyBUF_SIMPLE to PyBUF_FULL. Note | that e.g. with PyBUF_SIMPLE the consumer's shape and | strides will be NULL! Consumer And that model is consistent with the usage of PyBuffer_FillInfo() inside a getbufferproc, where flags of course can be anything. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21778 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21778] PyBuffer_FillInfo() from 3.3
Stefan Krah added the comment: I think it's worth adding a note to the docs about passing the flags unmodified inside a getbufferproc. -- assignee: - docs@python components: +Documentation nosy: +docs@python resolution: not a bug - stage: - needs patch versions: +Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21778 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12623] universal newlines subprocess support broken with select- and poll-based communicate()
Mark Lawrence added the comment: Can we have an update on this please, I'm assuming that the priority should now be marked as normal? -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12623 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20085] Python2.7, wxPython and IDLE 2.7
Mark Lawrence added the comment: Presumably set to languishing by mistake so please close. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20085 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21773] Fix a NameError in test_enum
Ethan Furman added the comment: Right, I had copied that code from test_pydoc which is where 'print_diffs' is defined. A comment there says to use the now-included functionality in unittest, and some digging in the docs revealed that assertEqual uses diffs by default. -- assignee: - ethan.furman stage: - patch review type: enhancement - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21773 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21782] hashable documentation error: shouldn't mention id
New submission from Giacomo Alzetta: The documentation for hashable in the glossary (https://docs.python.org/3.4/reference/datamodel.html#object.__hash__) is incorrect: they all compare unequal (except with themselves), **and their hash value is their id().** It is *not* true that their hash is their id (see relevant SO question: http://stackoverflow.com/questions/24249729/user-defined-class-hash-and-id-and-doc) Also the documentation for __hash__ (https://docs.python.org/3.4/reference/datamodel.html#object.__hash__) doesn't even mention id(). -- assignee: docs@python components: Documentation messages: 220746 nosy: Giacomo.Alzetta, docs@python priority: normal severity: normal status: open title: hashable documentation error: shouldn't mention id type: enhancement versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21782 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7687] Bluetooth support untested
Mark Lawrence added the comment: I'm assuming that this still needs some TLC. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7687 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9456] Apparent memory leak in PC/bdist_wininst/install.c
Mark Lawrence added the comment: There is a simple patch to free memory which at a quick glance appears okay. I've not tried to apply it as the line numbers tie up with those in the existing code. -- nosy: +BreamoreBoy versions: +Python 2.7, Python 3.4, Python 3.5 -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9456 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21782] hashable documentation error: shouldn't mention id
R. David Murray added the comment: The statement is poorly worded. The id() is the *input* to the hash function used to compute the default __hash__. This is a CPython implementation detail, though, so perhaps all mention of it should indeed be dropped. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21782 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21782] hashable documentation error: shouldn't mention id
Giacomo Alzetta added the comment: their hash value is their id() seems quite clearly stating that: class A: pass ... a = A() hash(a) == id(a) should be true, but: hash(a) == id(a) False (both in python2 and in python3) The python 2 documentation for the __hash__ special method *does* state that the default implementation returns a value derived by id(). I believe there is an inconsistency. In the python2 glossary it should say: their hash value is derived from their id() While in python3 it shouldn't mention id() at all, since the documentation for __hash__ doesn't mention it at all. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21782 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20085] Python2.7, wxPython and IDLE 2.7
Changes by Berker Peksag berker.pek...@gmail.com: -- status: languishing - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20085 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15786] IDLE code completion window can hang or misbehave with mouse
Ned Deily added the comment: Investigating a user report of IDLE freezing on OS X when mouse clicking on the code completion menu led me to this issue. The behavior I see varies depending on the Tk variant in use. The basic test case is: 1. launch IDLE with an IDLE shell window open 2. open an IDLE edit window for a new file 3. in the edit window, press a then TAB 4. the code completion window opens as expected 5. using the mouse, click on a selection in the code completion list With two different X11 Tk's (Debian Linux 8.5.x and OS X X11 8.6.x), clicking on the selection causes the code completion window to disappear but the code completion text does not appear in the edit window. Further, then pressing Return, a, and Tab to try a new code completion results in the code completion window momentarily appearing then disappearing. If one uses the mouse to click on and change focus to another IDLE window (e.g. the shell window), then click on and return focus to the edit window, the code completion window starts working again, at least, until using the mouse to click on a selection again. With the current Cocoa Tk 8.5.x on OS X (the most commonly used Tk there), the behavior is even more confusing to the user. After mouse-clicking on a code completion menu item, the code completion menu disappears but then the edit window becomes unresponsive to either the keyboard or the mouse until focus is moved, again by clicking on another IDLE window and then returning to the hung edit window. Oddly enough, the older Carbon Tk 8.4.x on OS X (used with 32-bit-only Pythons) seems to handle this all correctly. I did not try this with a Windows Tk. I also did not systematically check all current versions of IDLE with all of those Tk variants but spot checking saw similar behavior on current dev (pre-3.5), 3.4.1, and 2.7.x. -- nosy: +ned.deily title: IDLE code completion window does not scroll/select with mouse - IDLE code completion window can hang or misbehave with mouse versions: +Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15786 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21679] Prevent extraneous fstat during open()
Antoine Pitrou added the comment: I think it's ok to keep the block size an int for now. It would be surprising for a block size to be more than 2 GB, IMO. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21679 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21782] hashable documentation error: shouldn't mention id
R. David Murray added the comment: Yes, I should have been clearer. By poorly worded I meant id is involved, but the sentence does not correctly describe *how* id is involved. That is, the sentence is wrong as written. The implementation is the same in both Python2 and Python3, though the source code organization and how it becomes the default hash is a bit different. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21782 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10740] sqlite3 module breaks transactions and potentially corrupts data
Changes by Benjamin Kircher benjamin.kirc...@gmail.com: -- nosy: +bkircher ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10740 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21783] smtpd.py does not allow multiple helo/ehlo commands
New submission from Milan Oberkirch: Sending HELO or EHLO more then once causes smtpd.SMTPChannel to respond with b'503 Duplicate HELO/EHLO\r\n' (see Lib/test/test_smtpd.py:124 for an example). My interpretation of RFC 821, section 4.1.1.5 is that multiple HELO commands are fine outside a mail transaction and a second HELO is eauivalent to a RSET during a mail transaction (undoing any changes made by previous greetings). I would propose to reject greetings during mail transactiond (thats what RSET is for) and else accept them. The question is how we should handle backwards compatibility here. I am willing to work on this right after #21725. -- components: email messages: 220754 nosy: barry, jesstess, pitrou, r.david.murray, zvyn priority: normal severity: normal status: open title: smtpd.py does not allow multiple helo/ehlo commands versions: Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21783 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21686] IDLE - Test hyperparser
Terry J. Reedy added the comment: Coverage is now '99%'. Unless I see problems that are more than trivial, I am going to polish the patch and commit. I believe partial coverage of for context in editwin.num_context_lines: is because the iterable is never empty. But it never will be in practice and I believe the code is not intended to work if it is. So I ignore this. I believe partial coverage of deeply nested if rawtext[pos] in '\: is because this is reached with rawtext[pop] *not* in '\. Reading up, to reach this point, rawtext[pos] must also not be in ([:, bracketing[brck_index][0] == brck_limit must never become true inside the while look (because it breaks), and pos == brck_limit must be true. I don't know if this is all possible. Tal, if you find a triggering test case after I commit, it can be added later. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21686 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7982] extend captured_output to simulate different stdout.encoding
Mark Lawrence added the comment: Seems like a good idea but it'll go nowhere without a patch, anybody up for it? -- nosy: +BreamoreBoy versions: +Python 2.7, Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7982 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11056] 2to3 fails for inner __metaclass__ class definition
Mark Lawrence added the comment: @Benjamin what do you think of the proposed fix? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11056 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21697] shutil.copytree() handles symbolic directory incorrectly
Eduardo Seabra added the comment: Berker Peksag, I don't think your patch is okay. When symlinks is set to true, it should copy the symbolic link of the directory. Your code is calling copytree instead. I think the following patch is working, no errors on regression tests. -- nosy: +Eduardo.Seabra Added file: http://bugs.python.org/file35660/issue21697.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21697 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11097] MSI: Remove win32com dependency from installer generator
Mark Lawrence added the comment: If this report is (still) true I'd assume that we'd want to eventually action it. Otherwise can we close this as out of date? -- nosy: +BreamoreBoy type: - enhancement versions: +Python 3.5 -Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11097 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21773] Fix a NameError in test_enum
Roundup Robot added the comment: New changeset 1536085d4a94 by Victor Stinner in branch '3.4': Issue #21773: Fix TestStdLib.test_pydoc() of test_enum. Patch written by http://hg.python.org/cpython/rev/1536085d4a94 New changeset e82ba67d7472 by Victor Stinner in branch 'default': (Merge 3.4) Issue #21773: Fix TestStdLib.test_pydoc() of test_enum. Patch http://hg.python.org/cpython/rev/e82ba67d7472 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21773 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21773] Fix a NameError in test_enum
STINNER Victor added the comment: Fixed. Thanks for the patch. -- nosy: +haypo resolution: - fixed status: open - closed versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21773 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16587] Py_Initialize breaks wprintf on Windows
STINNER Victor added the comment: If I understood correctly, supporting the wide mode for wprintf() requires to modify all calls to functions like printf() in Python and so it requires to change a lot of code. Since this issue was the first time that I heard about wprintf(), I don't think that we should change Python. I'm not going to fix this issue except if much more users ask for it. -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16587 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4
STINNER Victor added the comment: I don't think that Windows XP is officially no more supported in Python. I would prefer an explicit mention in the PEP 11. So please don't use this argument to close an issue. -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6926 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11394] Tools/demo, etc. are not installed
Mark Lawrence added the comment: msg139889 states so I think this report is invalid so I suggest we close this. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11394 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4887] environment inspection and manipulation API is buggy, inconsistent with Python philosophy for wrapping native APIs
Mark Lawrence added the comment: Is the OP interested in taking this forward? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4887 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5877] Add a function for updating URL query parameters
Mark Lawrence added the comment: This won't go anywhere without a patch, is the OP willing to provide one? -- nosy: +BreamoreBoy versions: +Python 2.7, Python 3.5 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5877 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5888] mmap ehancement - resize with sequence notation
Mark Lawrence added the comment: @Brian this will go nowhere without a patch covering code, tests and documentation, are you interested in providing one? -- nosy: +BreamoreBoy versions: +Python 2.7, Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5888 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17888] docs: more information on documentation team
Mark Lawrence added the comment: In recent months people have been doing some great work on the docs, is this something that one of them could pick up? I'm sorry that I can't remember any names. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17888 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21772] platform.uname() not EINTR safe
STINNER Victor added the comment:
Calling f.read() on naked os.open() output can produce IOError: [Errno 4]
Interrupted system call. Attached is a suggested fix.
I cannot reproduce your issue. What is your exact Python version and OS?
I tried to run 100 threads calling 100 times platform._syscmd_uname('-p'). I
didn't reproduce the issue on Python 2.7 or 3.5.
---
import platform
import threading
def test():
for x in range(100):
p = platform._syscmd_uname('-p')
threads = [threading.Thread(target=test) for n in range(100)]
for thread in threads:
thread.start()
for thread in threads:
thread.join()
---
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21772
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15955] gzip, bz2, lzma: add option to limit output size
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15955 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6926] socket module missing IPPROTO_IPV6, IPPROTO_IPV4
Mark Lawrence added the comment: It looks as if we're talking at cross purposes. PEP11 will not be updated any more for Windows releases, we will be following the Microsoft support life cycle. That is clearly of interest to anybody wishing to make code changes against this issue. I do not want, and did not wish to imply, that this issue should be closed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6926 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5888] mmap ehancement - resize with sequence notation
Josh Rosenberg added the comment: I see a few issues with this: 1. Changing the default behavior is a compatibility issue. I've written code that depends on exceptions being raised if slice assignment sizes don't match. 2. The performance cost is high; changing from rewriting in place to shrinking or expanding slice assignment requires (in different orders for shrink/expand) truncating the file to the correct length, memcpy-ing data proportionate to the data after the end of the slice (not proportionate to the slice size) and probably remapping the file (which causes problems if someone has a buffer attached to the existing mapping). At least with non-file backed sequences, when we do work like this it's all in memory and typically smallish; with a file, most of it has to be read from and written to disk, and I'd assume the data being worked with is largish (if it's reliably small, the advantages of mmap-ing are small). 3. Behavior in cases where the whole file isn't mapped is hard to intuit or define reasonably. If I map the first 1024 bytes of a 2 GB file, and I add 20 bytes in the middle of the block, what happens? Does data from the unmapped portions get moved? Overwritten? What about removing 20 bytes from the middle of the block? Do we write 0s, or copy down the data that appears after? And remember, for all but the shrink and write 0s option, we're moving or modifying data the user explicitly didn't mmap. -- nosy: +josh.rosenberg ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5888 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6270] Menu deletecommand fails if command is already deleted
Mark Lawrence added the comment: I've tried to reproduce this on Windows 7 with Python 3.4.1 and failed. Would somebody else please give it a go. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6270 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21679] Prevent extraneous fstat during open()
Changes by Josh Rosenberg shadowranger+pyt...@gmail.com: -- nosy: +josh.rosenberg ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21679 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16136] Removal of VMS support
Changes by STINNER Victor victor.stin...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16136 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8822] datetime naive and aware types should have a well-defined definition that can be cross-referenced
Mark Lawrence added the comment: I like the wording in the patch as it's clearer than the original and so think it should be applied. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8822 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21772] platform.uname() not EINTR safe
Tor Colvin added the comment: 2.7.6 or 3.4.1 with OS X 10.8. I can only reproduce it an automated test environment when the load is high on the machine. I've also seen it with 10.6/10.7. It's definitely inconsistently reproducible. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21772 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9341] allow argparse subcommands to be grouped
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +paul.j3 versions: +Python 2.7, Python 3.5 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9341 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2943] Distutils should generate a better error message when the SDK is not installed
Lars H added the comment: +1 vote for fixing this problem. Matt Hickford said it very well... the error message is very cryptic, not giving the user a clue as to what domain the problem lies in. -- nosy: +Lars.H ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2943 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2943] Distutils should generate a better error message when the SDK is not installed
Mark Lawrence added the comment: @Steve could this be included with the work you're doing with the Windows installers? -- components: +Windows nosy: +BreamoreBoy, dstufft, eric.araujo, steve.dower ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2943 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21763] Clarify requirements for file-like objects
Nikolaus Rath added the comment: On 06/15/2014 06:26 PM, Raymond Hettinger wrote: Before creating more tracker items, please take time to learn about how Python's history, [...] It'd be nice if you would have at least followed the link to http://article.gmane.org/gmane.comp.python.devel/148199 before commenting. In case you still can't spare the time for that: I explicitly asked on python-dev about this *before* I opened a tracker item. Apart from that, I think your remarks are neither appropriate nor do they belong in the tracker. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21763 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1635217] Warn against using requires/provides/obsoletes in setup.py
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1635217 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9350] add remove_argument_group to argparse
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +paul.j3 versions: +Python 2.7, Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9350 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1446619] extended slice behavior inconsistent with docs
Mark Lawrence added the comment: The attached patch is simple enough, surely it's a simple decision as to whether or not to commit it? -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1446619 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11695] Improve argparse usage/help customization
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +paul.j3 versions: +Python 2.7, Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11695 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11176] give more meaningful argument names in argparse documentation
Mark Lawrence added the comment: If we've got some meaningful changes can we please get them committed. However I'd like to state that with over 4000 issues open we've got better things to do than change docs because somebody doesn't like the use of foo, bar and baz in examples. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11176 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
