[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Maciej Szulik added the comment: Julian I'm almost done with this issue. I just need to polish that a little bit and I'll provide working patch withing few hours. Sorry for not writing about that later, but I'm just starting with this and I had some time figuring it out. -- __

[issue20012] Re: Allow Path.relative_to() to accept non-ancestor paths

Anurag Kulkarni added the comment: Hey! A few changes are required to accomplish what you seek, but results could be severe. Path.relative_to() should return an exception if relative path is not part of the original path. However, I have got a solution for that. I am not that familiar with py

[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Vajrasky Kok added the comment: Julian, You need to update the patch from Juarez Bochi and Berker Peksag to the tip. -- nosy: +vajrasky ___ Python tracker ___

[issue20012] Allow Path.relative_to() to accept non-ancestor paths

New submission from Alexander Boyd: pathlib.Path.relative_to() blows up when given a path that's not an ancestor of the path on which relative_to is being called: >>> pathlib.Path("/usr/bin").relative_to("/etc") Traceback (most recent call last): File "", line 1, in File "pathlib.py", line

[issue19492] Report skipped distutils tests as skipped

Éric Araujo added the comment: Alright. Patch looks good, thanks. -- assignee: eric.araujo -> serhiy.storchaka ___ Python tracker ___ ___

[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Julian Gindi added the comment: I'm interested in taking over and finishing whatever needs to be completed to move this forward. What else needs to be done? It looks like improved tests are needed, but are there any changes needed to the implementation code? -- nosy: +Julian.Gindi ___

[issue9291] mimetypes initialization fails on Windows because of non-Latin characters in registry

Suzumizaki added the comment: There is possibility that the installation of setuptools fails with any Windows machine because of this bug. I want change the priority of this issue higher... I failed the installation of setuptools with Python 2.7.6 on my machine, Windows 8.1 Pro Japanese Editio

[issue19855] uuid._find_mac fails if an executable not in /sbin or /usr/sbin

R. David Murray added the comment: I'm on gentoo, so this was causing test runs to fail for me, giving me sufficient motivation to review the patches and commit them :) Thanks, Serhiy. -- nosy: +r.david.murray resolution: -> fixed stage: patch review -> committed/rejected status: open

[issue19855] uuid._find_mac fails if an executable not in /sbin or /usr/sbin

Roundup Robot added the comment: New changeset b0fbaed45956 by R David Murray in branch '3.3': #19855: uuid.get_node now looks on the PATH for executables on unix. http://hg.python.org/cpython/rev/b0fbaed45956 New changeset 2e856fcb9084 by R David Murray in branch 'default': Merge: #19855: uuid.

[issue19524] ResourceWarning when urlopen() forgets the HTTPConnection object

Martin Panter added the comment: Thanks for looking at this. Perhaps you weren’t pasting the HTTP response into “socat”. After the six request lines are printed out, I enter the five lines between and ; I didn’t really make this obvious. Otherwise, urlopen() hangs waiting for the response and

[issue20011] Changing the signature for Parameter's constructor

New submission from Antony Lee: As suggested on python-ideas, this small patch changes the constructor of inspect.Parameter so that "kind" defaults to "POSITIONAL_OR_KEYWORD", which should make code that needs to construct Parameter objects slightly less verbose (as I believe POSITIONAL_OR_KEY

[issue20010] time.strftime('%z') didn't make +HHMM return in windows xp

Civa Lin added the comment: Oh! Thanks your info! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue20010] time.strftime('%z') didn't make +HHMM return in windows xp

R. David Murray added the comment: As the documentation of the module says, we pass this call through to the underlying c library. What does the Windows documentation say about %z? A quick google turns up this hit, which seems to indicate it is a platform problem: http://connect.microsoft.co

[issue20006] Sporadic failures of test_weakset

Roundup Robot added the comment: New changeset a3d86f80c899 by Antoine Pitrou in branch '3.3': Issue #20006: Fix sporadic failures in test_weakset. http://hg.python.org/cpython/rev/a3d86f80c899 New changeset 26d92a21f6cf by Antoine Pitrou in branch 'default': Issue #20006: Fix sporadic failures

[issue20006] Sporadic failures of test_weakset

Antoine Pitrou added the comment: This was all my fault :) Thanks for reporting! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue20006] Sporadic failures of test_weakset

Roundup Robot added the comment: New changeset 226c37c209fc by Antoine Pitrou in branch '2.7': Issue #20006: Fix sporadic failures in test_weakset. http://hg.python.org/cpython/rev/226c37c209fc -- nosy: +python-dev ___ Python tracker

[issue20010] time.strftime('%z') didn't make +HHMM return in windows xp

New submission from Civa Lin: On windows xp (Taiwanese) platform... c:\> py -c "import time; print(time.strftime('%z', time.localtime()))" It will raise a UnicodeEncodeError in my system. I think it's not a +HHMM format and has different behavior with document: http://docs.python.org/3

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Serhiy Storchaka added the comment: 2.7 is affected too. Thank you Simon Sapin for your contribution. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: +Python 2.7 ___ Python tracker

[issue20009] Property should expose wrapped function.

New submission from steven Michalske: When using the @property decorator the wrapped functions are not exposed for source introspection. (At least I can't see how they are.) The issue is then that Ipython "%psource" will show the source for the @property as opposed to the function that it wrap

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Roundup Robot added the comment: New changeset ebace0a5a33e by Serhiy Storchaka in branch '2.7': Issue #20007: HTTPResponse.read(0) no more prematurely closes connection. http://hg.python.org/cpython/rev/ebace0a5a33e New changeset 47ae858cd661 by Serhiy Storchaka in branch '3.3': Issue #20007: H

[issue17781] optimize compilation options

Changes by Stefan Krah : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue16748] Make CPython test package discoverable

Changes by Zachary Ware : -- dependencies: +Clean up/refactor/make discoverable test_decimal, Fix test discovery for test_codecmaps*.py, Fix test discovery for test_concurrent_futures.py, Support ./python -m unittest in test_socket ___ Python tracke

[issue20008] Clean up/refactor/make discoverable test_decimal

New submission from Zachary Ware: This patch makes extensive changes to test_decimal, with the ultimate goal of making `python -m unittest discover Lib/test/ "test_*.py"` not choke on test_decimal (see issue16748). Trying to do so uncovered a few other issues, such as some tests not properly

[issue19524] ResourceWarning when urlopen() forgets the HTTPConnection object

Serhiy Storchaka added the comment: I can't reproduce issue. Python just hangs on read() when socat is used as test server. Perhaps I do something wrong. -- nosy: +orsenthil, serhiy.storchaka stage: -> patch review versions: +Python 3.4 -Python 3.2

[issue16404] Uses of PyLong_FromLong that don't check for errors

Changes by Serhiy Storchaka : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue12441] _GLOBAL_DEFAULT_TIMEOUT remains as an object() in HTTPConnection and the connection hangs

Changes by Serhiy Storchaka : -- stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue19946] Handle a non-importable __main__ in multiprocessing

Richard Oudkerk added the comment: Thanks for your hard work Nick! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue7464] circular reference in HTTPResponse by urllib2

Changes by Serhiy Storchaka : -- stage: needs patch -> test needed versions: -Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python

[issue4492] httplib code thinks it closes connection, but does not

Changes by Serhiy Storchaka : -- stage: needs patch -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue19998] Python 2.7.6 fails to build _ctypes on GCC 2.x toolchain

Jim Carroll added the comment: As requested, I've opened the issue with the libffi project: https://github.com/atgreen/libffi/issues/63 -- ___ Python tracker ___ ___

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Changes by Serhiy Storchaka : -- versions: -Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue17636] Modify IMPORT_FROM to fallback on sys.modules

PJ Eby added the comment: Unfortunately, this is not quite true: the weird edge cases for that approach are simply *different*, and harder to diagnose. ;-) The approach here can only affect execution paths that would currently raise ImportError; that one can break execution paths that are *cu

[issue992389] attribute error due to circular import

PJ Eby added the comment: The new patch will have weird results in the case of a parent module that defines an attribute that's later replaced by an import, e.g. if foo/__init__.py defines a variable 'bar' that's a proxy for the foo.bar module. This is especially problematic if this proxy is

[issue20004] csv.DictReader classic class has a property with setter

R. David Murray added the comment: Committed. Thanks, Peter. -- resolution: -> wont fix stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue20004] csv.DictReader classic class has a property with setter

Peter Otten added the comment: The proposed patch looks fine to me. And for the record, I don't think setting fieldnames should be promoted in the 3.x documentation. Along the lines of Eric's suggestion I should have written something like >>> import csv >>> with open("tmp.csv") as f: ...

[issue18283] shutil.which() should support bytes

Changes by Arfrever Frehtes Taifersar Arahesis : -- stage: committed/rejected -> ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20004] csv.DictReader classic class has a property with setter

R. David Murray added the comment: Since it isn't easy to figure out that setting fieldnames to None would do anything useful without looking at the code, I'd say a code comment would be appropriate. The exception would be someone backporting code from python3, but I think we'll just quietly

[issue20004] csv.DictReader classic class has a property with setter

R. David Murray added the comment: Here is a proposed comment wording. -- keywords: +patch Added file: http://bugs.python.org/file33181/csv_dictread_setter_comment.patch ___ Python tracker _

[issue19994] re.match does not return or takes long time

Tim Peters added the comment: Closing this. Since nobody else "wants have a go" over two decades so far, no point waiting for that ;-) -- resolution: invalid -> wont fix stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue4130] Intel icc 9.1 does not support __int128_t used by ctypes

Jens Timmerman added the comment: sorry for my confusion, libffi's website stated libffi-3.0.14 was released on TBD. I must have missed the TBD part. -- ___ Python tracker __

[issue19994] re.match does not return or takes long time

Matthew Barnett added the comment: It takes a long time due to excessive backtracking. The regex implementation on PyPI finishes quickly because it contains some extra logic to reduce the chances of that happening, but it could be tricky trying to incorporate that into the existing re module.

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Serhiy Storchaka added the comment: > Are those five functions new in 3.4 and undocumented? PyErr_SetFromErrnoWithFilenameObject exists even in 2.7. Other 4 PyImport_*Object functions all added in 3.3 (see issue3080). All 5 functions are documented. 14 new functions were added in 3.4. --

[issue19995] hex() and %x, oct() and %o do not behave the same

Eric V. Smith added the comment: Yes, looking through Objects/unicodeobject.c, 'u', 'i', and 'd' are treated the same everywhere. -- ___ Python tracker ___ _

[issue19995] hex() and %x, oct() and %o do not behave the same

Guido van Rossum added the comment: AFAIK %i and %d are the same. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Larry Hastings added the comment: Are those five functions new in 3.4 and undocumented? -- ___ Python tracker ___ ___ Python-bugs-list

[issue17976] file.write doesn't raise IOError when it should

Serhiy Storchaka added the comment: Agree. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Larry Hastings added the comment: Are we proposing renaming any functions that are either a) not new in 3.4, or b) were documented as of 3.4 beta 1? -- ___ Python tracker ___ ___

[issue17976] file.write doesn't raise IOError when it should

Roundup Robot added the comment: New changeset 24a043355050 by Serhiy Storchaka in branch '2.7': Circumventing a bug in glibc (issue #17976). http://hg.python.org/cpython/rev/24a043355050 -- ___ Python tracker

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Serhiy Storchaka added the comment: > Are all the functions that use "Object" to indicate "Unicode object instead > of string" new in 3.4? Of those, how many are undocumented? Following 5 functions work with PyObject* filenames and have Object-less variants which works with char * filenames:

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Simon Sapin added the comment: I could reproduce on 3.3.3 and tip, but not 3.2.3 or 2.7.6. -- versions: +Python 3.5 -Python 2.7 ___ Python tracker ___ ___

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Simon Sapin added the comment: html5lib issue: https://github.com/html5lib/html5lib-python/issues/127 -- ___ Python tracker ___ ___ Py

[issue20004] csv.DictReader classic class has a property with setter

Peter Otten added the comment: Setting the fieldnames attribute of an existing DictReader is not documented. Eric, there is no need for an enhancement (other than for the documentation) as this already works in Python 3 where newstyle classes are the default. The heart of the bug is really the

[issue20004] csv.DictReader classic class has a property with setter

Eric V. Smith added the comment: My (poorly phrased) question really was: is resetting fieldnames documented to force a re-read of the column headers? I don't see that it is, so I'm going to call this a 3.5 enhancement request. I agree with David that we can't change DictReader to inherit from

[issue20006] Sporadic failures of test_weakset

Serhiy Storchaka added the comment: > Ah, it seems the failure can happen because of hash randomization. Indeed. With -R switch 1/8 of tests are failed. -- ___ Python tracker __

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Changes by Serhiy Storchaka : -- nosy: +orsenthil, serhiy.storchaka stage: -> patch review versions: +Python 2.7, Python 3.3, Python 3.4 ___ Python tracker ___ _

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Larry Hastings added the comment: Are all the functions that use "Object" to indicate "Unicode object instead of string" new in 3.4? Of those, how many are undocumented? -- ___ Python tracker

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Serhiy Storchaka added the comment: > So all the PyRun_*Object functions are new in 3.4, and none of them are > documented yet? Not all. Only following functions are new in 3.4: Parser/parsetok.c:PyParser_ParseStringObject Parser/parsetok.c:PyParser_ParseFileObject Python/future.c:PyFuture_Fro

[issue17976] file.write doesn't raise IOError when it should

Jaakko Moisio added the comment: The new patch is fine as it is, but my logic behind using err_flag was the following: err_flag was set solely based on the inspection of return value of fwrite and ferror, without referencing to errno. It is of course true that at the same time errno is set to

[issue20006] Sporadic failures of test_weakset

Antoine Pitrou added the comment: Here is a patch. The failure doesn't occur on 3.x because of f189da5bda26, which clearly looks misled now. -- assignee: -> pitrou keywords: +patch Added file: http://bugs.python.org/file33180/issue20006.patch ___ Py

[issue20006] Sporadic failures of test_weakset

Changes by Antoine Pitrou : -- components: +Tests stage: -> patch review versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___

[issue19702] Update pickle to take advantage of PEP 451

Larry Hastings added the comment: So far I agree that this should be postponed to 3.5. -- ___ Python tracker ___ ___ Python-bugs-list

[issue19518] Add new PyRun_xxx() functions to not encode the filename

Larry Hastings added the comment: So all the PyRun_*Object functions are new in 3.4, and none of them are documented yet? Option 4 is silly--I don't think we should ship them as public APIs in 3.4 if we're planning to rename them. I prefer the previous options. p.s. fwiw I hate "ExName". --

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

Simon Sapin added the comment: Adding a proposed patch. -- keywords: +patch Added file: http://bugs.python.org/file33179/python-issue20007.diff ___ Python tracker ___ ___

[issue20007] .read(0) on http.client.HTTPResponse drops the rest of the content

New submission from Simon Sapin: When given a file-like object, html5lib calls .read(0) in order to check if the result is bytes or Unicode: https://github.com/html5lib/html5lib-python/blob/e269a2fd0aafcd83af7cf1e65bba65c0e5a2c18b/html5lib/inputstream.py#L434 When given the result of urllib.cl

[issue17976] file.write doesn't raise IOError when it should

STINNER Victor added the comment: > The complete fix is maybe to write fflush() before fclose(), or at least > raise an exception if fclose() returns a non-zero result. Correctly, > file.close() returns a number in case of an error... Oh sorry, I missed the line "if (sts == -1) ..." which rais

[issue20004] csv.DictReader classic class has a property with setter

R. David Murray added the comment: Although this is clearly a bug, we've run into backward compatibility issues in the past with promoting stdlib classic classes to new style, so I'm not sure if the risk of fixing it is worth the benefit. It is obviously not a problem in Python3. Eric: I had

[issue20006] Sporadic failures of test_weakset

Antoine Pitrou added the comment: Ah, it seems the failure can happen because of hash randomization. -- ___ Python tracker ___ ___ Pyt

[issue17976] file.write doesn't raise IOError when it should

Serhiy Storchaka added the comment: Are you have Python code which exposes a bug? -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue20006] Sporadic failures of test_weakset

Serhiy Storchaka added the comment: > Does it occur only on 2.7? Don't know. -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue20006] Sporadic failures of test_weakset

Antoine Pitrou added the comment: I can't reproduce the failure after more than 2000 test runs. Also, this failure is weird: the test is supposed to be deterministic. -- nosy: +koobs ___ Python tracker

[issue19713] Deprecate various things in importlib thanks to PEP 451

Brett Cannon added the comment: * Yes, you can commit with the warnings being triggered to get help with resolving them, just expect to potentially do a lot of work to make sure they don't leak out into 3.4 final. * Just don't deprecate load_module() yet in code. If we can't even get rid of a

[issue20006] Sporadic failures of test_weakset

Antoine Pitrou added the comment: Does it occur only on 2.7? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17976] file.write doesn't raise IOError when it should

STINNER Victor added the comment: I played with fullwrite.c and now think that the fix is incomplete. fwrite() may succeed to write data into the buffer, but you may get the error on fflush() or fclose(). Try attached fullwrite2.c: fwrite() succeed (written=len, errno=result=0), whereas fclos

[issue17976] file.write doesn't raise IOError when it should

STINNER Victor added the comment: (I was trying to report the issue upstream.) -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20004] csv.DictReader classic class has a property with setter

Eric V. Smith added the comment: I'm not clear on this: is this a new feature you'd like to see, or is this documented behavior of a DictReader that's not working? If it's a new feature, the earliest it can be implemented is in 3.5. -- nosy: +eric.smith ___

[issue20006] Sporadic failures of test_weakset

New submission from Serhiy Storchaka: test_weakset often fails on FreeBSD. Fo example see http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.0%202.7/builds/285/steps/test/logs/stdio. test test_weakset failed -- Traceback (most recent call last): File "/usr/home/buildbot/koobs-freeb

[issue17636] Modify IMPORT_FROM to fallback on sys.modules

Nick Coghlan added the comment: With PEP 451 implemented, note that I have reopened issue 992389 - the patch to set the parent module attribute at the same time as setting the sys.module attribute is actually pretty trivial for the PEP 451 loader case, and that now includes all the standard lo

[issue992389] attribute error due to circular import

Nick Coghlan added the comment: I'm reopening this, since PEP 451 opens up new options for dealing with it (at least for loaders that export the PEP 451 APIs rather than only the legacy loader API, which now includes all the standard loaders other than the ones for builtins and extension modul

[issue16404] Uses of PyLong_FromLong that don't check for errors

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> committed/rejected ___ Python tracker ___ ___ Python-bug

[issue16404] Uses of PyLong_FromLong that don't check for errors

Roundup Robot added the comment: New changeset debdfa44f020 by Serhiy Storchaka in branch '2.7': Issue #16404: Add checks for return value of PyInt_FromLong() in http://hg.python.org/cpython/rev/debdfa44f020 New changeset 928c0acf7c09 by Serhiy Storchaka in branch '3.3': Issue #16404: Add checks

[issue14228] It is impossible to catch sigint on startup in python code

Changes by Yongzhi Pan : -- nosy: +fossilet ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue17976] file.write doesn't raise IOError when it should

Roundup Robot added the comment: New changeset 237deaf9ba64 by Serhiy Storchaka in branch '2.7': Skip test for issue #17976 if /dev/null is not available. http://hg.python.org/cpython/rev/237deaf9ba64 -- ___ Python tracker

[issue19982] Add a "target" parameter to runpy.run_path and runpy.run_module

Nick Coghlan added the comment: Implementing this is actually likely to require non-trivial restructuring of the runpy internals. contextlib.ExitStack may prove useful in making it easier to programmatically select amongst different context managers. The __mp_main__ helpers in multiprocessing

[issue9325] Add an option to pdb/trace/profile to run library module as a script

Nick Coghlan added the comment: Issue 19982 suggests a different way of refactoring the runpy APIs inspired by PEP 451: passing in a "target" module to be used, rather than creating a temporary one from scratch. -- ___ Python tracker

[issue17976] file.write doesn't raise IOError when it should

Serhiy Storchaka added the comment: Thank you Jaakko Moisio for your report and patch. -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker _

[issue19702] Update pickle to take advantage of PEP 451

Changes by Nick Coghlan : -- title: Update pickle to PEP 451 -> Update pickle to take advantage of PEP 451 ___ Python tracker ___ ___

[issue17976] file.write doesn't raise IOError when it should

Roundup Robot added the comment: New changeset 33c27b76a4d0 by Serhiy Storchaka in branch '2.7': Issue #17976: Fixed potential problem with file.write() not detecting IO error http://hg.python.org/cpython/rev/33c27b76a4d0 -- nosy: +python-dev ___ Pyth

[issue19702] Update pickle to PEP 451

Nick Coghlan added the comment: Issue 19700 means that runpy now ensures that __main__.__spec__ is set appropriately when __main__ is executed via the import system. Issue 19946 means that multiprocessing now ensures that __main__ is configured correctly in child processes to reference a prope

[issue19700] Update runpy for PEP 451

Nick Coghlan added the comment: On second thoughts, I'm going to close this one - if further runpy changes are needed to resolve issue 19702 (using __spec__.name for pickle when appropriate), let's deal with them there. -- resolution: -> fixed stage: test needed -> committed/rejected

[issue20005] Minor typo in operator documentation

Changes by Claudiu.Popa : -- assignee: docs@python components: Documentation files: typo_operator.patch keywords: patch nosy: Claudiu.Popa, docs@python priority: normal severity: normal status: open title: Minor typo in operator documentation versions: Python 3.4 Added file: http://bugs.

[issue19946] Handle a non-importable __main__ in multiprocessing

Changes by Nick Coghlan : Removed file: http://bugs.python.org/file33163/test_multiprocessing_main_handling.py ___ Python tracker ___ ___ Pyt

[issue19946] Handle a non-importable __main__ in multiprocessing

Roundup Robot added the comment: New changeset b6d6f3b4b100 by Nick Coghlan in branch 'default': Close #19946: use runpy as needed in multiprocessing http://hg.python.org/cpython/rev/b6d6f3b4b100 -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed _

[issue20000] SSLContext.get_ca_certs() and self-signed certs

Changes by Antoine Pitrou : -- versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20000] SSLContext.get_ca_certs() and self-signed certs

Christian Heimes added the comment: > Interesting. Is it because of the way you implemented get_ca_certs()? Yes, it's the line http://hg.python.org/cpython/file/b78de8029606/Modules/_ssl.c#l3103 that skips all certs that are not recognized as CA certs. I wasn't aware that OpenSSL supports se

[issue17976] file.write doesn't raise IOError when it should

Serhiy Storchaka added the comment: LGTM. But err_flag is not needed, valid error numbers are all nonzero. -- assignee: -> serhiy.storchaka stage: needs patch -> commit review ___ Python tracker __

[issue19946] Handle a non-importable __main__ in multiprocessing

Changes by Nick Coghlan : Removed file: http://bugs.python.org/file33146/issue19946_pep_451_multiprocessing.diff ___ Python tracker ___ ___ P

[issue19946] Handle a non-importable __main__ in multiprocessing

Changes by Nick Coghlan : Removed file: http://bugs.python.org/file33161/test_multiprocessing_main_handling.py ___ Python tracker ___ ___ Pyt

[issue17825] Indentation.offset and SyntaxError.offset mismatch

Serhiy Storchaka added the comment: patch_indenterror_offset_v2.diff LGTM. -- stage: -> commit review versions: +Python 2.7, Python 3.3 ___ Python tracker ___ __

[issue19946] Handle a non-importable __main__ in multiprocessing

Nick Coghlan added the comment: OK, fixed test case attached. Turns out the ipython workaround test was completely wrong and never even loaded multiprocessing, and hence always passed, even with the workaround disabled. So I fixed that test case, and used the same approach for the zipfile, dir

  1   2   >