[issue22906] PEP 479: Change StopIteration handling inside generators
Stefan Behnel added the comment:
Regarding the patch below, isn't most of this redundant? ISTM that simply
calling PyErr_SetString(...) should do all of this, including the exception
chaining.
diff -r 23ab1197df0b Objects/genobject.c
--- a/Objects/genobject.c Wed Nov 19 13:21:40 2014 +0200
+++ b/Objects/genobject.c Thu Nov 20 16:47:59 2014 +1100
@@ -130,6 +130,23 @@
}
Py_CLEAR(result);
}
+else if (!result)
+{
+if (PyErr_ExceptionMatches(PyExc_StopIteration))
+{
+PyObject *exc, *val, *val2, *tb;
+PyErr_Fetch(exc, val, tb);
+PyErr_NormalizeException(exc, val, tb);
+Py_DECREF(exc);
+Py_XDECREF(tb);
+PyErr_SetString(PyExc_RuntimeError,
+generator raised StopIteration);
+PyErr_Fetch(exc, val2, tb);
+PyErr_NormalizeException(exc, val2, tb);
+PyException_SetContext(val2, val);
+PyErr_Restore(exc, val2, tb);
+}
+}
if (!result || f-f_stacktop == NULL) {
/* generator can't be rerun, so release the frame */
--
nosy: +scoder
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22906
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22906] PEP 479: Change StopIteration handling inside generators
Chris Angelico added the comment: Stefan, I'm not sure - I don't know the details of the C API here. But I tried commenting out everything but that one line, and while it does result in RuntimeError, it doesn't do the exception chaining. Currently, I believe the exception isn't being caught at all; but I don't know what it would take to do the full catching properly. The current patch doesn't always have a traceback on the original StopIteration, either, so it's definitely not quite right yet. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22906 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22965] smtplib.py: senderrs[each] - TypeError: unhashable instance
New submission from mattes: I get the following error: File /usr/local/Cellar/python/2.7.8_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/smtplib.py, line 731, in sendmail senderrs[each] = (code, resp) TypeError: unhashable instance senderrs[str(each)] = (code, resp) fixes it. Not sure if that is the best fix though. See also http://stackoverflow.com/questions/27195432/google-app-engine-mail-send-returns-typeerror-unhashable-instance-in-python2 -- components: Library (Lib), email messages: 231854 nosy: barry, mattes, r.david.murray priority: normal severity: normal status: open title: smtplib.py: senderrs[each] - TypeError: unhashable instance type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22965 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22906] PEP 479: Change StopIteration handling inside generators
Stefan Behnel added the comment: Ah, right - chaining only happens automatically when the exception has already been caught and moved to sys.exc_info. There's a _PyErr_ChainExceptions(), though, which does it for you. You should be able to say PyErr_Fetch(x,y,z) PyErr_SetString() _PyErr_ChainExceptions(x,y,z) (does pretty much what your code does as well) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22906 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22906] PEP 479: Change StopIteration handling inside generators
Chris Angelico added the comment: Yeah, I saw that. Since that function begins with an underscore, I thought it best to replicate its behaviour rather than to call it. Either way ought to work though. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22906 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22906] PEP 479: Change StopIteration handling inside generators
Stefan Behnel added the comment: Public underscore C functions are there for exactly the purpose of not duplicating functionality across *internal* core runtime code, without making them an official part of the C-API for *external* code. (I understand that it's a POC patch, though, so whoever applies that change eventually will rework it anyway.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22906 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22906] PEP 479: Change StopIteration handling inside generators
Stefan Behnel added the comment: FYI, here's the set of tests that I've written for my implementation in Cython: https://github.com/cython/cython/blob/b4383a540a790a5553f19438b3fc22b11858d665/tests/run/generators_pep479.pyx -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22906 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22966] py_compile: foo.bar.py → __pycache__/foo.cpython-34.pyc
New submission from Piotr Ożarowski: when py_compile module is asked to create .pyc file for file with invalid name, it doesn't fail or ignore such request - it creates/overwrites .pyc file for sane file name (i.e. ignores everything after dot) $ touch foo.bar.py $ python3.4 -m py_compile foo.bar.py $ ls __pycache__ foo.cpython-34.pyc Even though foo.bar.py is not a valid file name, some programmers are using such names for plugins which leads to bugs similar to https://lists.debian.org/debian-python/2014/11/msg00061.html. I will update my scripts to not feed py_compile module with file names containing dot (and remove already generated .pyc files if such files are detected), but please do not generate them or generate .pyc files with invalid file names as well. -- messages: 231859 nosy: piotr priority: normal severity: normal status: open title: py_compile: foo.bar.py → __pycache__/foo.cpython-34.pyc versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22966 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22898] segfault during shutdown attempting to log ResourceWarning
Xavier de Gaye added the comment: Out of curiosity I have tried to figure out how to build another test case using the model provided by runtimerror_singleton.py. This cannot be done, and for the following reasons: The infinite recursion of PyErr_NormalizeException() is supposed to occur as follows: when a RuntimeError caused by recursion is normalized, PyErr_NormalizeException() calls the RuntimeError class to instantiate the exception, the recursion limit is reached again, triggering a new RuntimeError that needs also to be normalized causing PyErr_NormalizeException() to recurse infinitely. But the low/high water mark level heuristic of the anti-recursion protection mechanism described in a comment of ceval.h prevents this. Let's assume the infinite recursion is possible: * At iteration 'n' of the infinite recursion, the instantiation of the RuntimeError exception fails because of recursion with a new RuntimeError and tstate-overflowed is true: PyErr_NormalizeException() recurses. * At iteration 'n + 1', the instantiation of this new RuntimeError is successfull because the recursion level is not checked when tstate-overflowed is true: the recursion of PyErr_NormalizeException() terminates and infinite recursion is not possible. This explains the paradox that, if you remove entirely the check against infinite recursion in PyErr_NormalizeException(), then the runtimerror_singleton_2.py reproducer does not crash and the ResourceWarning is printed even though the recursion limit has been reached. The attached patch implements this fix, includes the previous changes in _warning.c, and moves the test case to test_exceptions. History (for reference): The PyExc_RecursionErrorInst singleton was added by svn revision 58032 [1] to fix the issue titled a bunch of infinite C recursions [2]. In parallel, changeset cd125fe83051 [3] added the 'overflowed' member to the thread state. Interestingly changeset cd125fe83051 was committed before revision 58032, but the whole discussion on issue [2] took place well before this commit was done, and so the fact that the infinite recursion problem of PyErr_NormalizeException() was being fixed by changeset cd125fe83051 as a side effect, went unnoticed. [1] http://svn.python.org/view?view=revisionrevision=58032 [2] http://bugs.python.org/issue1202533 [3] https://hg.python.org/cpython/rev/cd125fe83051 -- Added file: http://bugs.python.org/file37316/remove_singleton.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22898 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19858] Make pickletools.optimize aware of the MEMOIZE opcode.
Serhiy Storchaka added the comment: Here is a patch which makes pickletools.optimize() to work with the MEMOIZE opcode. As side effect it also renumbers memoized values, this allows to use short BINPUT and BINGET instead of LONG_BINPUT and LONG_BINGET. -- keywords: +patch stage: needs patch - patch review versions: +Python 3.4 Added file: http://bugs.python.org/file37317/pickle_optimize_memoize.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19858 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22966] py_compile: foo.bar.py → __pycache__/foo.cpython-34.pyc
Changes by Brett Cannon br...@python.org: -- components: +Library (Lib) stage: - test needed type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22966 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22966] py_compile: foo.bar.py → __pycache__/foo.cpython-34.pyc
Changes by Brett Cannon br...@python.org: -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22966 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22462] Modules/pyexpat.c violates PEP 384
Roundup Robot added the comment: New changeset e4b986350feb by Antoine Pitrou in branch '3.4': Close issue #22895: fix test failure introduced by the fix for issue #22462. https://hg.python.org/cpython/rev/e4b986350feb New changeset 4990157343c6 by Antoine Pitrou in branch 'default': Close issue #22895: fix test failure introduced by the fix for issue #22462. https://hg.python.org/cpython/rev/4990157343c6 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22462 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22895] test failure introduced by the fix for issue #22462
Antoine Pitrou added the comment: This should be fixed now. -- resolution: - fixed stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22895 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22895] test failure introduced by the fix for issue #22462
Roundup Robot added the comment: New changeset e4b986350feb by Antoine Pitrou in branch '3.4': Close issue #22895: fix test failure introduced by the fix for issue #22462. https://hg.python.org/cpython/rev/e4b986350feb New changeset 4990157343c6 by Antoine Pitrou in branch 'default': Close issue #22895: fix test failure introduced by the fix for issue #22462. https://hg.python.org/cpython/rev/4990157343c6 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22895 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22542] Use arc4random under OpenBSD for os.urandom() if /dev/urandom is not present
700eb415 added the comment: From the OpenBSD random(4) man page: The arc4random(3) function in userland libraries should be used instead, as it works without the need to access these devices every time. Theo just had a good talk on this issue here about why /dev/random needs replacing here: http://www.openbsd.org/papers/hackfest2014-arc4random/index.html . There's also a videon on YouTube. At this point, I should probably have a patch ready sometime towards the middle of the week. I had a conversation with Ted Unangst off list, and think the best place for me to push it would first be a patch to the OpenBSD ports. After the OpenBSD guys review it, I'll then push it here. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22542 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22966] py_compile: foo.bar.py → __pycache__/foo.cpython-34.pyc
Changes by Barry A. Warsaw ba...@python.org: -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22966 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22966] py_compile: foo.bar.py → __pycache__/foo.cpython-34.pyc
Piotr Ożarowski added the comment: Python 3.2 generates foo.bar.cpython-32.pyc so it's a regression -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22966 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22967] tempfile.py does not work in windows8
New submission from Kyle Lahnakoski: I installed python 2.7.8 on Windows version 6.2 (build 9200) and get-pip.py does not run. I traced the problem to c:\python27\lib\tempfile.py Here is my session: c:\Users\kyle\Downloadspython Python 2.7.8 (default, Jun 30 2014, 16:03:49) [MSC v.1500 32 bit Intel)] on win32 Type help, copyright, credits or license for more information. import tempfile Traceback (most recent call last): File stdin, line 1, in module File c:\Python27\lib\tempfile.py, line 32, in module import io as _io File io.py, line 72, in module import numpy as N ImportError: No module named numpy Ok, seems odd that numpy is required. I installed numpy, and tried again: import tempfile tmpdir = tempfile.mkdtemp() Traceback (most recent call last): File stdin, line 1, in module File c:\Python27\lib\tempfile.py, line 325, in mkdtemp dir = gettempdir() File c:\Python27\lib\tempfile.py, line 269, in gettempdir tempdir = _get_default_tempdir() File c:\Python27\lib\tempfile.py, line 200, in _get_default_tempdir with _io.open(fd, 'wb', closefd=False) as fp: AttributeError: 'module' object has no attribute 'open' I expected that tempfile would import without issue. -- components: IO messages: 231867 nosy: klahnako...@mozilla.com priority: normal severity: normal status: open title: tempfile.py does not work in windows8 type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22967 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22967] tempfile.py does not work in windows8
Zachary Ware added the comment: Try the following in Command Prompt: cd /D C:\Users\kyle\Downloads python -c import io;print io.__file__ The result should be C:\Python27\lib\io.pyc. If it's not, rename the file that you do get back. -- nosy: +zach.ware resolution: - not a bug status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22967 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22967] tempfile.py does not work in windows8
Kyle Lahnakoski added the comment: Doh! Dirty directory! Thank you for your time! My apologies. -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22967 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22967] tempfile.py does not work in windows8
Zachary Ware added the comment: No problem, glad it was an easy one :) -- stage: - resolved ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22967 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22968] types._calculate_meta nit: isinstance != PyType_IsSubtype
New submission from Greg Turner: Kinda trivial but... Something like the enclosed, untested patch would seem to make new_class work a bit more like type_new. To be explicit, the difference is whether or not to respect virtual subclasses. So, for example, as implemented, we can implement __subclasscheck__ on a 'AtypicalMeta' metaclass to create an 'Atypical' class whose __mro__ is (ATypical, object) -- note, no 'type' -- but for which issubclass(type, ATypical) is true. If I'm not mistaken, this disguise will suffice sneak our psuedo-metatype past new_class (but not type.__new__, so we still get the same error message, and the universe does not implode on itself as planned...) In my case,the only sequela was that the fantasy of my very own type-orthogonal graph of foo-style classes in 3.x was first subtly encouraged and then dashed against the Cpython rocks... (just kidding, sort-of). -- components: Library (Lib) files: fix_types_calculate_meta.patch keywords: patch messages: 231871 nosy: gmt priority: normal severity: normal status: open title: types._calculate_meta nit: isinstance != PyType_IsSubtype type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file37318/fix_types_calculate_meta.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22968 ___ ___ 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
Zachary Ware added the comment: I'd prefer to just reimplement itemgetter and attrgetter to make them picklable rather than adding pickling methods to them; see attached patch. I also posted a few comments, but I just went ahead and addressed them myself in this patch. I'm not qualified to give the _operator.c changes a proper review, but they look good enough to me if others agree that __reduce__ is the best approach in C. -- Added file: http://bugs.python.org/file37319/issue22955.diff ___ 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
[issue22955] Pickling of methodcaller, attrgetter, and itemgetter
Changes by Zachary Ware zachary.w...@gmail.com: Removed file: http://bugs.python.org/file37319/issue22955.diff ___ 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
[issue22955] Pickling of methodcaller, attrgetter, and itemgetter
Changes by Zachary Ware zachary.w...@gmail.com: Added file: http://bugs.python.org/file37320/issue22955.diff ___ 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
[issue22955] Pickling of methodcaller, attrgetter, and itemgetter
Serhiy Storchaka added the comment: operator.methodcaller is similar to functools.partial which is pickleable and can be used as a sample. In C implementation some code can be shared between __repr__ and __reduce__ methods. As for tests, different protocols should be tested. Also should be tested compatibility between C and Python implementations, instances pickled with one implementation should be unpickleable with other implementation. Move pickle tests into new test class. If add __repr__ methods, they need tests. The restriction of method name type should be tested too. -- ___ 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
[issue22884] argparse.FileType.__call__ returns unwrapped sys.stdin and stdout
paul j3 added the comment: Related issues are: http://bugs.python.org/issue13824 - argparse.FileType opens a file and never closes it http://bugs.python.org/issue14156 - argparse.FileType for '-' doesn't work for a mode of 'rb' As discussed earlier FileType was meant as a convenience for small scripting applications, ones that don't try to close the file before exiting. But now we are encouraged to open files in a context that guarantees closure. In 13824 I proposed a 'FileContext', and included a dummy context like this handle stdin/out. But I think the closefd=False approach raised in 14156 and David is probably the better way to go. I think the main thing that is lacking is a testing mechanism. -- nosy: +paul.j3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22884 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)
Steve Dower added the comment: AFAICT, cabinet.lib has been around since at least VS 2008, so 3.4 will be fine. But since it builds currently there's no point changing it. I'll just let my changes handle it for 3.5 and leave the older versions alone. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21236 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22676] _pickle's whichmodule() is slow
Steve Dower added the comment: That patch looks good to me (better than my fix would have been :) ) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22676 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22909] [argparse] Using parse_known_args, unknown arg with space in value is interpreted as first positional arg
paul j3 added the comment: This an issue for parse_args as well. parse_args just calls parse_known_args, and raises an error if extras is not empty. Early on in parsing, it tries to classify argument strings as either optionals (--flags) or positionals (arguments). And there's an explicit test for spaces: def _parse_optional(self, arg_string): ... # if it contains a space, it was meant to be a positional if ' ' in arg_string: return None Basically, if it can't match the string with a define optional, and it contains a space (anywhere) it is classed as positional. That's what your example shows. It sounds familiar, so I suspect it was raised in an earlier issue. I'll have to look it up. -- nosy: +paul.j3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22909 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22919] Update PCBuild for VS 2015
Steve Dower added the comment: After a debug build with VS2015, my biggest concern is this: ..\PC\bdist_wininst\install.rc(19): fatal error RC1015: cannot open include file 'afxres.h'. [P:\ath\to\cpython\PCbuild\bdist_wininst.vcxproj] I thought I had a workaround for this, but I'll have to check it out. Oddly enough, all of my builds have been fine (I think I'm mostly doing release builds - does that make a difference?) I haven't been able to reproduce this. bdist_wininst isn't selected to build for debug in VS, but it builds fine for me anyway. Was your repo dirty? (It didn't make a difference for me, but I have had files occasionally not update properly when switching branches.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22919 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22909] [argparse] Using parse_known_args, unknown arg with space in value is interpreted as first positional arg
paul j3 added the comment: Duplicate of http://bugs.python.org/issue22433 -- resolution: - duplicate ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22909 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22960] xmlrpc.client.ServerProxy() should accept a custom SSL context parameter
Alex Gaynor added the comment: Attached is a patch for 2.7 -- keywords: +patch Added file: http://bugs.python.org/file37321/issue22960.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22960 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22909] [argparse] Using parse_known_args, unknown arg with space in value is interpreted as first positional arg
Changes by Berker Peksag berker.pek...@gmail.com: -- stage: - resolved status: open - closed superseder: - Argparse considers unknown optional arguments with spaces as a known positional argument ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22909 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22536] subprocess should include filename in FileNotFoundError exception
Travis Thieman added the comment: Thank you all for the helpful comments. A revised attempt is attached as -2.patch, with improved behavior around using cwd if the child is never called and orig_executable if it is. I opted not to fix the issue with the redundancy in the error message as I agree that should be handled as a separate issue. -- Added file: http://bugs.python.org/file37322/22536-subprocess-exception-filename-2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22536 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22960] xmlrpc.client.ServerProxy() should accept a custom SSL context parameter
Benjamin Peterson added the comment: I suppose I should ask you to write a test. Of course, HTTPS doesn't seem to be tested at all right now (see the attractive FIXME: mostly untested comment in SafeTransport.) Maybe, it's easier now, though, using the code in Lib/test/ssl_servers.py? -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22960 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22960] xmlrpc.client.ServerProxy() should accept a custom SSL context parameter
Roundup Robot added the comment: New changeset 62bd574e95d5 by Benjamin Peterson in branch '2.7': add context parameter to xmlrpclib.ServerProxy (#22960) https://hg.python.org/cpython/rev/62bd574e95d5 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22960 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22960] xmlrpc.client.ServerProxy() should accept a custom SSL context parameter
Alex Gaynor added the comment: Attached patch fixes it for Python3. -- Added file: http://bugs.python.org/file37323/issue22960-3.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22960 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22960] xmlrpc.client.ServerProxy() should accept a custom SSL context parameter
Roundup Robot added the comment: New changeset 4b00430388ad by Benjamin Peterson in branch '3.4': add context parameter to xmlrpclib.ServerProxy (#22960) https://hg.python.org/cpython/rev/4b00430388ad New changeset 2a126ce6f83e by Benjamin Peterson in branch 'default': merge 3.4 (#22960) https://hg.python.org/cpython/rev/2a126ce6f83e -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22960 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22959] http.client.HTTPSConnection checks hostname when SSL context has check_hostname==False
Benjamin Peterson added the comment: Why do you think it still verifies the hostname? It will certainly check if the certificate has a valid trust chain, but it won't do matching on the hostname. -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22959 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22960] xmlrpc.client.ServerProxy() should accept a custom SSL context parameter
Changes by Benjamin Peterson benja...@python.org: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22960 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
