[issue24964] Add tunnel CONNECT response headers to httplib / http.client

Martin Panter added the comment: This is the patch I had in mind. It looks like it only implements the detach() method, so we would still need to add support for passing in the tunnel details to the HTTPSConnection constructor. This patch would allow doing stuff at a lower level than the exist

[issue24964] Add tunnel CONNECT response headers to httplib / http.client

Changes by Martin Panter : -- stage: test needed -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue24984] document AF_BLUETOOTH socket address formats

Martin Panter added the comment: Here is a suggestion of how to add a versionchanged tag. Let me know if it is accurate or not. (I’m not actually familiar with the history.) -- Added file: http://bugs.python.org/file40370/bluetooth_socket_docs_5.patch __

[issue24748] Change of behavior for importlib between 3.4 and 3.5 with DLL loading

Nick Coghlan added the comment: Huh, for some reason the Rietveld diff missed the changes to _testmultiphase.c that are in the patch file. The change looks good to me. The test adds a new "test.imp_dummy" module, imports that, and then ensures it can be replaced by using imp.load_dynamic to i

[issue23406] interning and list comprehension leads to unexpected behavior

Martin Panter added the comment: That works for me. Here is a new patch using David’s new wording. -- Added file: http://bugs.python.org/file40369/issue23406_doc_stdtypes.v3.patch ___ Python tracker ___

[issue2651] Strings passed to KeyError do not round trip

Changes by Raymond Hettinger : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue24912] The type of cached objects is mutable

Nathaniel Smith added the comment: Sorry, you were too quick for me :-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue25005] webbrowser breaks on query strings with multiple fields on Windows

Steve Dower added the comment: It'll have to be backed out. There may be a fix to salvage some of the functionality, but it's certainly too significant at this stage. -- ___ Python tracker

[issue24912] The type of cached objects is mutable

Guido van Rossum added the comment: Oh. I feel dumb now. I guess I'll let Larry choose. If it's just a matter of comment text we can always improve it in 3.5.1. -- ___ Python tracker __

[issue24912] The type of cached objects is mutable

Nathaniel Smith added the comment: There's already a PR on bitbucket that I made, in case that's helpful. The only difference from the v2 patch are that I rephrased some of the comment in a more neutral way (based on feedback from Mark posted on the PR itself), and added a NEWS entry. It does

[issue24912] The type of cached objects is mutable

Guido van Rossum added the comment: PR: https://bitbucket.org/larry/cpython350/pull-requests/15/issue-24912-prevent-__class__-assignment/diff -- assignee: -> larry resolution: -> fixed ___ Python tracker ___

[issue24912] The type of cached objects is mutable

Guido van Rossum added the comment: I'm creating the PR for Larry. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Nick Coghlan added the comment: In tandem with an "asynchronous iterable" glossary entry, that could be a nice improvement. Even without such a change the first hit for "python asynchronous iterable" is PEP 492, so it will get folks pointed in the right direction. --

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Tim Peters added the comment: > Half-up leaves them all 5 microseconds apart, When only looking at the decimal digit in the 6th place after rounding. Which is all I did look at ;-) -- ___ Python tracker __

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Tim Peters added the comment: Bah. It doesn't matter who's consuming the rounding of a binary float to decimal microseconds: there are only 32 possible fractional parts where nearest/even and half-up deliver different results. half-up preserves properties of these specific inputs that neare

[issue24917] time_strftime() Buffer Over-read

John Leitch added the comment: I plucked the error message from the % operator: >>> '%' % 'foo' Traceback (most recent call last): File "", line 1, in ValueError: incomplete format >>> '%z' % 'foo' Traceback (most recent call last): File "", line 1, in ValueError: unsupported format charac

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: Hmm, on Mac OSX "%" and "A%" are valid format strings: >>> time.strftime("%") '%' >>> time.strftime("A%") 'A%' Mark's experiments show that on Windows they are not. What about the other platforms affected by the patch? I am concerned about the bottom pa

[issue25002] Deprecate asyncore/asynchat

R. David Murray added the comment: smtpd is used for testing smtplib. It is also used in test_logging. I would object to having it removed, but I suspect we can manage to rewrite it by 3.8. Maybe Eric and I can collaborate on it. -- nosy: +r.david.murray ___

[issue24917] time_strftime() Buffer Over-read

John Leitch added the comment: Attached is a revised patch. -- Added file: http://bugs.python.org/file40367/time_strftime_Buffer_Over-read_v2.patch ___ Python tracker ___ __

[issue25005] webbrowser breaks on query strings with multiple fields on Windows

R. David Murray added the comment: Thank you for reporting this. I see that the Windows browser class uses shell=True, and that is wrong from a security standpoint. This appears to be a regression from 3.4, introduced by issue 8232. Since this is a security regression there either needs to b

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Alexander Belopolsky added the comment: > timestamps aren't random, so "statistical bias" is roughly meaningless in > this context. I agree. I don't think I made any arguments about timestamps specifically other than a consistency with timedeltas. In the later case, I think all the usual ar

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: > if there's a risk I'm overlooking I'd like to better understand it, > and the relevant Python documentation should be updated. I don't think there is any special risk that you are overlooking other than a documented fact that Python's strftime is a thin

[issue24917] time_strftime() Buffer Over-read

Larry Hastings added the comment: Yes, I'd like this fix in 3.5.0. One bit of feedback on the patch: outbuf is a char * (or wchar_t *), therefore outbuf[1] is a char (or wchar_t). You shouldn't compare it to NULL. I'm not sure we still support any compilers that define NULL as (void *)0, but

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: As far as I know, the practical consequence of "security" classification for the issue is how many affected older versions will be patched. I am keeping that and the 3.2 - 3.5 versions range. The priority may affect whether this will make it into 3.5.0.

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Tim Peters added the comment: Goodness. It's the properties of "randomly chosen decimals" that have nothing to do with timestamps ;-) timestamps aren't random, so "statistical bias" is roughly meaningless in this context. I gave a specific example before of how nearest/even destroys obvious

[issue24917] time_strftime() Buffer Over-read

John Leitch added the comment: When I get a bit of slackspace (probably tomorrow afternoon/evening) I can test on the spectrum of versions to confirm the issue is in >= 3.2. I'll also look into improving our automation so all future reports can have the appropriate versions flagged. Regarding

[issue25002] Deprecate asyncore/asynchat

Eric V. Smith added the comment: I use smtpd.py for testing my code. But it's not such a big deal that I couldn't live without it. If I have some time to burn, I might convert it to asyncio so I can continue to use it. -- nosy: +eric.smith ___ Pytho

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: FWIW, the patch looks good to me, but it needs to be reviewed by a Windows developer. -- components: +Extension Modules ___ Python tracker __

[issue24912] The type of cached objects is mutable

Guido van Rossum added the comment: Serhiy, can you commit it and prepare a PR for Larry? -- ___ Python tracker ___ ___ Python-bugs-li

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: I will keep the "security" classification, but will not increase the priority. Accepting format strings from untrusted sources is a vulnerability in and by itself and in most cases those strings are literals. --

[issue24912] The type of cached objects is mutable

Serhiy Storchaka added the comment: issue24912-v2.patch LGTM. -- stage: -> commit review ___ Python tracker ___ ___ Python-bugs-list

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: John, There is no doubt that this is a bona fide bug. I was just hoping that someone with a Windows development machine would help figuring out the affected versions. >From the hg history, it looks like the faulty code is present in all versions >star

[issue24917] time_strftime() Buffer Over-read

John Leitch added the comment: It very well may apply to versions apart from 3.5. Our test environment is quite complex and unfriendly to working with multiple versions of Python. Plus, we're strapped for time, so we tend to file under the version we're currently targeting and defer to those b

[issue24875] pyvenv doesn´t install PIP inside a new venv with --system-site-package

Mathieu Pasquet added the comment: This bug actually makes the --system-site-packages option useless, because it prevents installation of any package inside the virtualenv unless one tries the workaround given by gracinet. -- nosy: +mathieui ___ Pyt

[issue25006] List pybind11 binding generator

New submission from Wenzel Jakob: Hi, over the last few months, I've been developing a library ("pybind11") for creating Python bindings of C++ code. It is similar in spirit to Boost.Python but uses a very different minimalist approach. It would be fantastic to get this library listed here:

[issue24917] time_strftime() Buffer Over-read

Mark Lawrence added the comment: Okay, so presumably this applies to all supported versions and not just 3.5? Can you also remove the reproducer and supply specific instructions on how to build the code so that the problem can be reproduced. -- components: +Windows nosy: +paul.moore,

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: Sorry for a bad guess. John's advise makes much more sense than mine. -- ___ Python tracker ___ _

[issue24917] time_strftime() Buffer Over-read

Mark Lawrence added the comment: Python prompt or script makes no difference. C:\Users\Mark\Desktop>py -2.6 time_strftime_Buffer_Over-read.py Traceback (most recent call last): File "time_strftime_Buffer_Over-read.py", line 2, in strftime("AA%"*0x1) ValueError: Invalid format string

[issue24917] time_strftime() Buffer Over-read

John Leitch added the comment: > I have tried the reproducer on Windows 10 with 2.6, 2.7, 3.3, 3.4, 3.5 and > 3.6. In every case I got this. What you are observing is due to the arrangement and contents of process memory. With a simple repro (such as the one provided), there's a good chance

[issue24917] time_strftime() Buffer Over-read

Alexander Belopolsky added the comment: > In every case I got [ValueError] You shouldn't have. I am no Windows expert, but I suspect something is wrong with your use of the command line. Please try it at the Python prompt or put the code in a script. --

[issue25001] Make --nowindows argument to regrtest propagate when running with -j

Brett Cannon added the comment: Steve's idea SGTM. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue25005] webbrowser breaks on query strings with multiple fields on Windows

New submission from Brian Hou: With Python 3.5.0rc2 (tested with both Git BASH and Cmder on Windows 8): $ python3 >>> import webbrowser >>> webbrowser.open_new('http://example.com/?a=1&b=2') 'b' is not recognized as an internal or external command, operable program or batch file. True The opene

[issue25002] Deprecate asyncore/asynchat

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue24917] time_strftime() Buffer Over-read

Mark Lawrence added the comment: I have tried the reproducer on Windows 10 with 2.6, 2.7, 3.3, 3.4, 3.5 and 3.6. In every case I got this. C:\py -3.4 -c"from time import *;strftime('AA%'*0x1)" Traceback (most recent call last): File "", line 1, in ValueError: Invalid format string

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

STINNER Victor added the comment: Ok, thanks for the explanation :-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue25002] Deprecate asyncore/asynchat

Guido van Rossum added the comment: Ideally these modules should emit a deprecation warning starting in 3.6 (when asyncio is no longer provisional) and we should strive to delete them per 3.8. If nobody rewrites smptd.py using asyncio it should be deleted at the same time. --

[issue24912] The type of cached objects is mutable

Guido van Rossum added the comment: We should have something for rc3, which is imminent. I vote for (1) and (2) if Serhiy thinks the patch is ready. -- ___ Python tracker ___ __

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Alexander Belopolsky added the comment: .. and "[Round half to even] is the default rounding mode used in IEEE 754 computing functions and operators." -- ___ Python tracker ___

[issue23630] support multiple hosts in create_server/start_server

Yann Sionneau added the comment: Yet another version of the patch according to the last review. -- Added file: http://bugs.python.org/file40366/multibind8.patch ___ Python tracker __

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Alexander Belopolsky added the comment: .. and here is an unbeatable argument: "this variant of the round-to-nearest method is also called unbiased rounding, convergent rounding, statistician's rounding, **Dutch rounding**, Gaussian rounding, odd–even rounding, or bankers' rounding."

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Alexander Belopolsky added the comment: Here is what Wikipedia has to say on the subject: """ Round half to even .. This method treats positive and negative values symmetrically, and is therefore free of sign bias. More importantly, for reasonable distributions of y values, the expected (avera

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Alexander Belopolsky added the comment: > By the way, why does Python use ROUND_HALF_EVEN for round()? ROUND_HALF_EVEN does not introduce statistical bias in your floating point data. With this choice a randomly chosen decimal has an equal chance of being rounded up or down. I think one can

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Tim Peters added the comment: Victor, there are good "theoretical" reasons for using half/even rounding in _general_ use. But this bug report isn't the place to get into them. Here it just should be enough to note that the IEEE 754 floating point standard _requires_ half/even to be the defau

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

STINNER Victor added the comment: > My opinions haven't changed: nearest/even is unnatural for rounding times > ("sometimes up, sometimes down" grates against the nature of monotonically > non-decreasing timestamps), By the way, why does Python use ROUND_HALF_EVEN for round()? It also feels

[issue25001] Make --nowindows argument to regrtest propagate when running with -j

Steve Dower added the comment: I'd be happy to always disable assert dialogs/output in regrtest, and then use "-n" to enable stderr output. That way people simply testing their own debug builds don't think it's failed, and the buildbots keep all the output they currently have. -- vers

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Tim Peters added the comment: Yes, it would be good to hear from Mark. When I first saw this report, I checked to see whether he was on the nosy list. He is, but is apparently busy elsewhere. My opinions haven't changed: nearest/even is unnatural for rounding times ("sometimes up, sometime

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

STINNER Victor added the comment: > Is the "review" link up-to date? Oh, I wrote a patch serie, but Rietveld doesn't know the dependencies between my patches... So I attached combined_py34.patch which combines the 3 patches into a single one, hard to reviewer, but it should work with Rietveld

[issue25003] os.urandom() should call getrandom(2) not getentropy(2)

Changes by R. David Murray : -- nosy: +haypo stage: -> needs patch type: -> security ___ Python tracker ___ ___ Python-bugs-list mai

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Changes by STINNER Victor : Removed file: http://bugs.python.org/file40363/fromtimestamp_round_half_up_py34-2.patch ___ Python tracker ___ __

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Changes by STINNER Victor : Added file: http://bugs.python.org/file40364/fromtimestamp_round_half_up_py34-2.patch ___ Python tracker ___ ___

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Changes by STINNER Victor : Removed file: http://bugs.python.org/file40350/round_half_up_py34.patch ___ Python tracker ___ ___ Python-bugs-lis

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Changes by STINNER Victor : Removed file: http://bugs.python.org/file40351/fromtimestamp_round_half_up_py34.patch ___ Python tracker ___ ___

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Changes by STINNER Victor : Added file: http://bugs.python.org/file40363/fromtimestamp_round_half_up_py34-2.patch ___ Python tracker ___ ___

[issue24956] Default value for an argument that is not in the choices list gets accepted

R. David Murray added the comment: OK, I'm going to close this as "not a bug" then, as it seems to be an intentional design decision. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Changes by STINNER Victor : Added file: http://bugs.python.org/file40362/round_half_up_py34-2.patch ___ Python tracker ___ ___ Python-bugs-lis

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Alexander Belopolsky added the comment: It would be nice to hear from Mark Dickinson on this. In Python 3, we took a much more systematic approach to rounding than a rather haphazard Python 2. For example, the rounding mode for timedelta(0, float_seconds) is not specified in Python 2, but it

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Roundup Robot added the comment: New changeset 3c29d05c0710 by Victor Stinner in branch 'default': Issue #23517: Fix implementation of the ROUND_HALF_UP rounding mode in https://hg.python.org/cpython/rev/3c29d05c0710 -- ___ Python tracker

[issue25004] test_mmap should catch f.close() failure in LargeMmapTests._make_test_file()

New submission from John Beck: When running test_mmap on a partition with < 4GB free, it back-traced: Traceback (most recent call last): File "/usr/lib/python3.4/test/test_mmap.py", line 728, in _make_test_file f.flush() OSError: [Errno 28] No space left on device During handling of the a

[issue24956] Default value for an argument that is not in the choices list gets accepted

Changes by Terry J. Reedy : -- nosy: +bethard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue24981] Add a test which uses the ast module to compile the stdlib

Terry J. Reedy added the comment: The distutils error is a ValueError, which was printed as such before I added 'Exception' to the except statement. I did not initially catch SyntaxError separately because some are caught during the compile phase. Revised file corrects 'pass' to 'continue' and

[issue24975] Python 3.5 can't compile AST involving PEP 448 unpacking

Terry J. Reedy added the comment: Upon writing a proof-of-concept file for #24981, I discovered an stdlib file that gave the same error. C:/programs/Python35/Lib\distutils/_msvccompiler.py ValueError: None disallowed in expression list I presume the applied fix will apply to this also. --

[issue25003] os.urandom() should call getrandom(2) not getentropy(2)

New submission from John Beck: A recent Solaris build upgrade resulted in a massive slowdown of a package operation (our package client is written in Python). Some DTrace revealed this was because os.urandom() calls had slowed down by a factor of over 300. This turned out to be caused by an

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

STINNER Victor added the comment: > I did not quite understand why you've chosen ROUND_HALF_UP over > ROUND_HALF_EVEN, but as long as fromtimestamp() uses the same rounding as > timedelta() - I am happy. Not only Tim prefers this rounding mode, Python 2.7 also uses the same mode, and the orig

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Tim Peters added the comment: Alex, if you like, I'll take the blame for the rounding method - I did express a preference for it here: http://bugs.python.org/issue23517#msg249309 When I looked at the code earlier, the round-half-up implementation looked good to me (floor(x+0.5) if x >= 0 else

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Alexander Belopolsky added the comment: Victor, I did not quite understand why you've chosen ROUND_HALF_UP over ROUND_HALF_EVEN, but as long as fromtimestamp() uses the same rounding as timedelta() - I am happy. -- ___ Python tracker

[issue25002] Deprecate asyncore/asynchat

STINNER Victor added the comment: The documentation of both modules begin with the following note: "This module exists for backwards compatibility only. For new code we recommend using asyncio." What do you mean by deprecating the module? Emit a PendingDeprecationWarning in Python 3.6 and emi

[issue25002] Deprecate asyncore/asynchat

Guido van Rossum added the comment: Yes, in 3.6 asyncio will no longer be provisional and we can start deprecating async{ore,hat}. Which is why I marked this bug with 3.6. -- ___ Python tracker ___

[issue24956] Default value for an argument that is not in the choices list gets accepted

paul j3 added the comment: A related issue which Sworddragon found just before starting this issue is http://bugs.python.org/issue9625 The handling of defaults in argparse is a bit complicated. In general it errs on the side of giving the user/developer freedom to set them how ever they

[issue25002] Deprecate asyncore/asynchat

Changes by Guido van Rossum : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue25002] Deprecate asyncore/asynchat

Donald Stufft added the comment: I'm all for deprecating asyncore/asynchat but should deprecating them wait until asyncio is no longer provisional? -- nosy: +dstufft ___ Python tracker

[issue25002] Deprecate asyncore/asynchat

New submission from Guido van Rossum: Now that we've got asyncio in two releases (3.4 and 3.5) we should start deprecating asyncore and asynchat. There isn't much use of these in the stdlib (smtpd.py uses them, and a bunch of tests) and we should probably rewrite those to use asyncio. Maybe sm

[issue25001] Make --nowindows argument to regrtest propagate when running with -j

New submission from Brett Cannon: Not sure how feasible this is, but when running tests under Windows it's very nice to run with --nowindows on, else you get barraged with a ton of debugging warnings. The problem is that if you use -j the use of --nowindows gets turned off. It would be nice if

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

STINNER Victor added the comment: Oh, it looks like my implementation of ROUND_HALF_UP is wrong. Negative numbers are not correctly rounded :-/ I'm working on a fix. -- ___ Python tracker __

[issue24981] Add a test which uses the ast module to compile the stdlib

Brett Cannon added the comment: Two things about the UTF-8 decode issue. One is you don't need to decode the source for it to be compiled; ast.parse()/compile() will work from bytes objects and thus handle the decoded for you. Two, if you want to decode source files into text, use importlib.ut

[issue23517] datetime.utcfromtimestamp rounds results incorrectly

Mark Lawrence added the comment: Python 3.3.5 (v3.3.5:62cf4e77f785, Mar 9 2014, 10:35:05) [MSC v.1600 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> from datetime import * >>> E = datetime(1970,1,1,tzinfo=timezone.utc) >>> s = -1/2**7 >>> dat

[issue24891] race condition in initstdio() (python aborts running under nohup)

STINNER Victor added the comment: I don't plan to send a pull request to the Python 3.5 release manager. This bug existed since Python 3.0, the fix can wait for Python 3.5.1. -- ___ Python tracker _

[issue24891] race condition in initstdio() (python aborts running under nohup)

Yi Ding added the comment: Thank you everyone! I will test the next rc of 3.5. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue24997] mock.call_args compares as equal and not equal

Changes by Terry J. Reedy : -- nosy: +michael.foord, rbcollins ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24990] Foreign language support in turtle module

Terry J. Reedy added the comment: > discussion elsewhere #24978, translate docs to Russian -- nosy: +terry.reedy ___ Python tracker ___ __

[issue24635] test_typing is flaky

Guido van Rossum added the comment: OK, done. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue24635] test_typing is flaky

Roundup Robot added the comment: New changeset 0f37918440c9 by Guido van Rossum in branch 'default': Issue #24635: Fixed flakiness in test_typing.py. (Merge from 3.5.) https://hg.python.org/cpython/rev/0f37918440c9 New changeset 438dde69871d by Guido van Rossum in branch '3.5': Fix issue #24635.

[issue24981] Add a test which uses the ast module to compile the stdlib

Terry J. Reedy added the comment: Ran with installed 3.5.0rc1. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue24981] Add a test which uses the ast module to compile the stdlib

Terry J. Reedy added the comment: Forgot to mention: runtime 4 seconds. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue24981] Add a test which uses the ast module to compile the stdlib

Terry J. Reedy added the comment: The attached recurses one level deep in Lib. Catching UnicodeDecodeError on file read is needed at least for "test/test_source_encoding.py 'utf-8' codec can't decode byte 0xf0 in position 267: invalid continuation byte". Catching "badxxx.py" is needed for sev

[issue24635] test_typing is flaky

Larry Hastings added the comment: Pull request accepted. Please forward merge, thanks! And, yes, this will be a null merge because you already separately committed it to 3.5. -- assignee: larry -> gvanrossum stage: needs patch -> resolved status: open -> closed __

[issue24954] No way to generate or parse timezone as produced by datetime.isoformat()

Changes by Alexander Belopolsky : -- stage: -> needs patch type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing

[issue24954] No way to generate or parse timezone as produced by datetime.isoformat()

Alexander Belopolsky added the comment: This request is similar to (if not a duplicate of) issue 15873. Gnu date uses the following extensions to %z instruction of strftime/strptime: %z +hhmm numeric timezone (e.g., -0400) %:z+hh:mm numeric timezone (e.g., -04:00)

[issue24635] test_typing is flaky

Guido van Rossum added the comment: Assigning to Larry since the next step is his. -- assignee: gvanrossum -> larry priority: high -> release blocker ___ Python tracker ___ _

[issue24635] test_typing is flaky

Guido van Rossum added the comment: BTW, I screwed up and committed this into the public 3.5 repo first (and merged from there into default). I guess once Larry has merged the fix into his special closed 3.5 bitbucket repo I should do a null merge from there back to public 3.5 and forward the

[issue24635] test_typing is flaky

Guido van Rossum added the comment: Pull request for Larry: https://bitbucket.org/larry/cpython350/pull-requests/14/fix-issue-24635/diff -- ___ Python tracker ___ __

  1   2   3   >