[issue23016] uncaught exception in lib/warnings.py when executed with pythonw
Arfrever Frehtes Taifersar Arahesis added the comment: +# sys.stderr is None when ran with pythonw.exe - warnings get lost s/ran/run/ -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23016 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23016] uncaught exception in lib/warnings.py when executed with pythonw
Roundup Robot added the comment: New changeset 70b6fe58c425 by Serhiy Storchaka in branch '3.4': Fixed a typo in a comment (issue #23016). https://hg.python.org/cpython/rev/70b6fe58c425 New changeset da1ec8e0e068 by Serhiy Storchaka in branch 'default': Fixed a typo in a comment (issue #23016). https://hg.python.org/cpython/rev/da1ec8e0e068 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23016 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23016] uncaught exception in lib/warnings.py when executed with pythonw
Serhiy Storchaka added the comment: Thanks Arfrever. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23016 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23049] Fix functools.reduce code equivalent.
Serhiy Storchaka added the comment: I think it would be good to add Python implementation in functools.py and test they equivalence in tests. -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23049 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23048] abort when jumping out of a loop
Xavier de Gaye added the comment: Building on OS X 10.10 with the head of the code tree (as of today), I cannot reproduce this. Also the disassembly looks fine: I should have mentionned that I am running a debug build of python. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23048 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23030] lru_cache manual get/put
Constantin added the comment: I understand your decision. Even though it makes my life a little bit harder, it is definitely not the end of the world, the end of Python or even the end for my libtco project. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23030 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23004] mock_open() should allow reading binary data
Aaron Hill added the comment: Thanks, I've fixed that. Not sure why I thought decoding and re-encoding would work with any binary data. I've also updated one of the tests to use non-utf8-decodeable binary data, to prevent a future regression. -- Added file: http://bugs.python.org/file37446/mock-open-allow-binary-without-coerce.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23004 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23050] Add Japanese legacy encodings
New submission from Tetsuya Morimoto: This patch adds Japanese legacy encodings as below. https://bitbucket.org/t2y/cpython/branches/compare/japanese-legacy-encoding..default * eucjp_ms (euc-jp compatible with cp932) * iso2022_jp_ms (yet another iso-2022-jp compatible with cp932, similar to cp50220) * cp50220 (http://www.iana.org/assignments/charset-reg/CP50220) * cp50221 (a variant of cp50220) * cp50222 (a variant of cp50220) * cp51932 (http://www.iana.org/assignments/charset-reg/CP51932) Originally, these character encodings patch was created as result in IPA project in 2005, by Masayuki Moriyama. The result was contributed to several community: libiconv, glibc, perl, PHP, Ruby, PostgreSQL, MySQL, nkf. He had made a patch for Python 2.4.3 at that time, but somehow, no one worked to integrate. That's a crying shame. These character encodings are legacy, but are still used. Lots of end-user don't care the character encoding. Unfortunately, for historical reason, e-mails are encoded with these legacy encodings on Japanese Windows platform. Actually, my customer recently reported about Mojibake since its e-mail data would be encoded with cp50220 (iso-2022-jp-ms). References: * About IPA: http://www.ipa.go.jp/english/about/summary.html * Mojibake: http://en.wikipedia.org/wiki/Mojibake * Java encoding names: http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html References in Japanese: * Japanese Legacy Encoding Project: http://legacy-encoding.sourceforge.jp/wiki/ * Project details: http://www.ipa.go.jp/about/jigyoseika/05fy-pro/open/2005-1467d.pdf -- components: Library (Lib) files: add-japanese-legacy-encoding1.patch hgrepos: 285 keywords: patch messages: 232638 nosy: ishimoto, naoki, t2y priority: normal severity: normal status: open title: Add Japanese legacy encodings type: enhancement versions: Python 3.5 Added file: http://bugs.python.org/file37447/add-japanese-legacy-encoding1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23050 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23050] Add Japanese legacy encodings
R. David Murray added the comment: In emails these are labeled as, say, iso-2022-jp-ms? See also issue 8898 with regards to email encodings. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23050 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23050] Add Japanese legacy encodings
Tetsuya Morimoto added the comment: On Mon, Dec 15, 2014 at 1:04 AM, R. David Murray rep...@bugs.python.org wrote: In emails these are labeled as, say, iso-2022-jp-ms? No. These are labeled just 'iso-2022-jp' and we (japanese) choose proper charset encoding to decode the encoded text. You can see several variants of iso-2022-jp. Yes, that's a very strange, but it's a historical reason. http://en.wikipedia.org/wiki/ISO/IEC_2022#ISO.2FIEC_2022_character_sets See also issue 8898 with regards to email encodings. Therefore, this is different issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23050 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22955] Pickling of methodcaller, attrgetter, and itemgetter
Serhiy Storchaka added the comment: Here is revised Josh's patch. Added tests for consistency between both implementations, fixed inconsistencies and bugs. I still hesitate about pickling format of methodcaller. First, there is asymmetry between positional and keyword arguments. Second, for now methodcaller is not inheritable, but if it will be in future (as functools.partial is), it would be harder to extend pickling format to support instance attributes. -- stage: needs patch - patch review Added file: http://bugs.python.org/file37448/pickle_getter_and_caller3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22955 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23050] Add Japanese legacy encodings
Changes by Serhiy Storchaka storch...@gmail.com: -- nosy: +lemburg, loewis, serhiy.storchaka stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23050 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23049] Fix functools.reduce code equivalent.
Terry J. Reedy added the comment: Background: the OP of #19202 proposed equivalent code for all the functool functions, including two versions for reduce. Georg combined the two versions into the one that Raymond pushed. Both agreed that reduce was the only function that really needed this. I called Georg's code 'excellent'. I have changed my mind slightly because people use such code equivalents not only for understanding but also as models for writing code, and because some people have had problems when by doing the same as this model, which ignores the empty iterable case. If you do not want to 'uglify' the doc code by making it exactly equivalent, how about qualifying the claim instead? Change 'equivalent' to 'equivalent for non-empty iterables'. -- keywords: +patch nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23049 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
New submission from Alon Diamant: When imap() or imap_unordered() are called with the iterable parameter set as a generator function, and when that generator function raises an exception, then the _task_handler thread (running the method _handle_tasks) dies immediately, without causing the other threads to stop and without reporting the exception to the main thread (that one that called imap()). I saw this issue in Python 2.7.8, 2.7.9 and 3.4.2. Didn't check other versions, but I assume this is a bug in all Python versions since 2.6. I will be attaching examples that reproduce this issue, as well as patches for both Python 2.7 and Python 3.4. -- components: Library (Lib) messages: 232643 nosy: advance512 priority: normal severity: normal status: open title: multiprocessing.pool methods imap() and imap_unordered() cause deadlock type: behavior versions: Python 2.7, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
Changes by Alon Diamant diamant.a...@gmail.com: Added file: http://bugs.python.org/file37449/Issue_23051_reproducer_v2_7.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
Changes by Alon Diamant diamant.a...@gmail.com: -- keywords: +patch Added file: http://bugs.python.org/file37450/Issue_23051_fix_v2_7.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
Changes by Alon Diamant diamant.a...@gmail.com: Added file: http://bugs.python.org/file37451/Issue_23051_reproducer_v3_4.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
Changes by Alon Diamant diamant.a...@gmail.com: Added file: http://bugs.python.org/file37452/Issue_23051_fix_v3_4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
Changes by Alon Diamant diamant.a...@gmail.com: Removed file: http://bugs.python.org/file37452/Issue_23051_fix_v3_4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
Changes by Alon Diamant diamant.a...@gmail.com: Added file: http://bugs.python.org/file37453/Issue_23051_fix_v3_4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23051] multiprocessing.pool methods imap() and imap_unordered() cause deadlock
Alon Diamant added the comment: The patches I attached do 2 things: 1. A deadlock is prevented, wherein the main thread waits forever for the Pool thread/s to finish their execution, while they wait for instructions to terminate from the _task_handler thread which has died. Instead, the exception are caught and handled and termination of the pool execution is performed. 2. The exception that was raised is caught and passed to the main thread, and is re-thrown in the context of the main thread - hence the user catch it and handle it, or - at the very least - be aware of the issue. I tested the patch to the best of my abilities, and am almost certain nothing was changed performance wise nor anything broken. Further eyes would, of course, only help for confirming this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23051 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23004] mock_open() should allow reading binary data
Demian Brecht added the comment: Thanks again for the update Aaron, I've left a couple small comments in Rietveld. Other than those, the patch looks good to me. Thanks for the contribution! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23004 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23049] Fix functools.reduce code equivalent.
Raymond Hettinger added the comment: Elsewhere I have used rough equivalent. FWIW, the initializer defaulting to None is also an approximation. It would be more technically correct to have initializer = sentinel where sentinel = object(). But of course this too would obfuscate the documentation which mainly aimed to clarify two sticky points: 1) the order of arguments to the function call (accm, x) vs (x, accm) and 2) that if an initializer isn't specified, the first value from the iterable is used. These are the two issues that Guido found difficult to remember and caused reduce() to be banished from builtins. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23049 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15506] configure should use PKG_PROG_PKG_CONFIG
Roundup Robot added the comment: New changeset 54939f3c1e17 by Benjamin Peterson in branch '2.7': use autoconf macro to check for pkg-config (closes #15506) https://hg.python.org/cpython/rev/54939f3c1e17 New changeset 76df5870757a by Benjamin Peterson in branch '3.4': use autoconf macro to check for pkg-config (closes #15506) https://hg.python.org/cpython/rev/76df5870757a New changeset 5e473a7a01f3 by Benjamin Peterson in branch 'default': merge 3.4 (#15506) https://hg.python.org/cpython/rev/5e473a7a01f3 -- nosy: +python-dev resolution: - fixed stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15506 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14134] xmlrpc.client.ServerProxy needs timeout parameter
Demian Brecht added the comment:
I'm a -1 to adding the timeout parameter to the ServerProxy implementation for
pretty much the same reasons Jeff mentioned, but mainly because of the
ambiguity that is introduced between the timeout and transport parameters (who
should win in the case that they're both used?). I'm also a -1, although a
little less strongly, on adding the timeout parameter to the transport layer.
Instead, what I would /like/ to see is to have a connection_factory parameter
added to Transport.__init__ that takes a host parameter (i.e. what's passed
into HTTPConnection here:
https://hg.python.org/cpython/file/e301ef500178/Lib/xmlrpc/client.py#l1231)
which would default to a local function or lambda that does exactly what it's
doing now. There are a few benefits to doing this:
1. Adding a timeout is just slightly less trivial than the current proposal
2. Encapsulation of the HTTPConnection object isn't broken
3. By exposing the ability to override the lower level HTTPConnection,
connection_factory can result in a client that not only allows for setting
changes such as timeouts, but can also result in any connection object that
adheres to the expected HTTPConnection interface.
For me, the 3rd point is the biggest selling feature. Not only can tweaks such
as the timeout be made, but if other features are required such as customized
logging, exponential back-off and such, they can easily be implemented in a
child class of HTTPConnection. You could even write a (possibly) trivial
adapter layer to interface with a 3rd party HTTP library if you so chose to.
So, instantiating a ServerProxy object with an HTTPConnection with a custom
timeout in its transport layer might look like this:
def updated_timeout(host):
return HTTPConnection(host, timeout=42)
proxy = ServerProxy('http://example.com/gateway/',
transport=Transport(connection_factory=updated_timeout))
While the use cases that you've used as examples can tend to happen, I firmly
believe that those should be solved by enhanced documentation and not by
implementation changes.
--
nosy: +demian.brecht
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14134
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23052] python2.7.9 [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
New submission from binbjz: It will prompt ssl certificate_vefify_failed(_ssl.c:581) when I used pysphere with python 2.7.9 to connect server. But I switched python 2.7.8 it works well. 2014-12-15 13:22:53,187 [DEBUG] Can not connect to xxx.xxx.xxx.108: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) 2014-12-15 13:22:53,187 [DEBUG] Can not connect to 153.65.178.113: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) Process Process-2: Process Process-3: Traceback (most recent call last): Traceback (most recent call last): File 2.7.9/lib/python2.7/multiprocessing/process.py, line 258, in _bootstrap File 2.7.9/lib/python2.7/multiprocessing/process.py, line 258, in _bootstrap 2014-12-15 13:22:53,187 [DEBUG] Can not connect to xxx.xxx.xxx.109: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) Process Process-4: Traceback (most recent call last): File 2.7.9/lib/python2.7/multiprocessing/process.py, line 258, in _bootstrap 2014-12-15 13:22:53,188 [DEBUG] Can not connect to xxx.xxx.xxx.104: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) Process Process-6: Traceback (most recent call last): File 2.7.9/lib/python2.7/multiprocessing/process.py, line 258, in _bootstrap 2014-12-15 13:22:53,188 [DEBUG] Can not connect to 153.65.178.112: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) Process Process-1: Traceback (most recent call last): File 2.7.9/lib/python2.7/multiprocessing/process.py, line 258, in _bootstrap 2014-12-15 13:22:53,189 [DEBUG] Can not connect to xxx.xxx.xxx.105: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) Process Process-7: Traceback (most recent call last): File 2.7.9/lib/python2.7/multiprocessing/process.py, line 258, in _bootstrap 2014-12-15 13:22:53,190 [DEBUG] Can not connect to xxx.xxx.xxx.106: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581) Process Process-8: Traceback (most recent call last): File 2.7.9/lib/python2.7/multiprocessing/process.py, line 258, in _bootstrap self.run() self.run() self.run() self.run() File 2.7.9/lib/python2.7/multiprocessing/process.py, line 114, in run File 2.7.9/lib/python2.7/multiprocessing/process.py, line 114, in run self.run() File 2.7.9/lib/python2.7/multiprocessing/process.py, line 114, in run File 2.7.9/lib/python2.7/multiprocessing/process.py, line 114, in run self._target(*self._args, **self._kwargs) self.run() File 2.7.9/lib/python2.7/multiprocessing/process.py, line 114, in run self._target(*self._args, **self._kwargs) File EsxiControler.py, line 153, in get_all_inUse_vm_statusList File 2.7.9/lib/python2.7/multiprocessing/process.py, line 114, in run self._target(*self._args, **self._kwargs) File EsxiControler.py, line 153, in get_all_inUse_vm_statusList self._target(*self._args, **self._kwargs) File EsxiControler.py, line 153, in get_all_inUse_vm_statusList self._target(*self._args, **self._kwargs) self._target(*self._args, **self._kwargs) File EsxiControler.py, line 153, in get_all_inUse_vm_statusList File EsxiControler.py, line 153, in get_all_inUse_vm_statusList File EsxiControler.py, line 153, in get_all_inUse_vm_statusList meth2='get_inUse_vmstatus', meth3='disconnect', initK='vm_name', initV='vm_status') File EsxiControler.py, line 210, in get_output_formatter meth2='get_inUse_vmstatus', meth3='disconnect', initK='vm_name', initV='vm_status') meth2='get_inUse_vmstatus', meth3='disconnect', initK='vm_name', initV='vm_status') File EsxiControler.py, line 210, in get_output_formatter vm_dict = mtd2() meth2='get_inUse_vmstatus', meth3='disconnect', initK='vm_name', initV='vm_status') File EsxiControler.py, line 210, in get_output_formatter meth2='get_inUse_vmstatus', meth3='disconnect', initK='vm_name', initV='vm_status') File /tmp/EsxiControler.py, line 69, in get_inUse_vmstatus File EsxiControler.py, line 210, in get_output_formatter vm_dict = mtd2() File EsxiControler.py, line 210, in get_output_formatter vm_dict = mtd2() File /tmp/EsxiControler.py, line 69, in get_inUse_vmstatus vm_dict = mtd2() File /tmp/EsxiControler.py, line 69, in get_inUse_vmstatus vm_dict = mtd2() File /tmp/EsxiControler.py, line 69, in get_inUse_vmstatus File /tmp/EsxiControler.py, line 69, in get_inUse_vmstatus meth2='get_inUse_vmstatus', meth3='disconnect', initK='vm_name', initV='vm_status') File EsxiControler.py, line 210, in get_output_formatter vm_dict = mtd2() File /tmp/EsxiControler.py, line 69, in get_inUse_vmstatus for vmPath in self.get_vmlist(): for vmPath in self.get_vmlist(): File /tmp/EsxiControler.py, line 56, in get_vmlist File /tmp/EsxiControler.py, line 56, in get_vmlist for vmPath in self.get_vmlist(): for vmPath in self.get_vmlist(): for vmPath in self.get_vmlist(): self.vmlist =
[issue22928] HTTP header injection in urrlib2/urllib/httplib/http.client
Changes by Demian Brecht demianbre...@gmail.com: -- nosy: +demian.brecht ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22928 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23052] python2.7.9 [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
Alex Gaynor added the comment: Python 2.7.9 enabled certificate validation by default for HTTP connections, see PEP476. The server you're connecting to does not have a certificate that is trusted by your client. pysphere should configure SSL appropriately for this use case. -- nosy: +alex resolution: - not a bug stage: - resolved ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23052 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14134] xmlrpc.client.ServerProxy needs timeout parameter
Andrej A Antonov added the comment: @demian.brecht , your example code-fragment is too big. :-) too many lines -- just only for adding timeout. it is uncomfortably. most people will not using that: most likely they just will forget about timeout (but in *MOST* situations not using timeout -- it is mistake). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14134 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23052] python2.7.9 [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
binbjz added the comment: alex, thank you for quick reponse. I will check http://www.python.org/dev/peps/pep-0476/ -- resolution: not a bug - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23052 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23052] python2.7.9 [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
Changes by Berker Peksag berker.pek...@gmail.com: -- resolution: - not a bug status: open - closed type: crash - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23052 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
