[issue32210] Add the versions of the Android SDK and NDK to test.pythoninfo

New submission from Xavier de Gaye : * The NDK version can be obtained by parsing the file $ANDROID_NDK_ROOT/source.properties. * The versions of the SDK build-tools, emulator and platform-tools packages as well as those of the system images can be obtained by parsing the output of "$ANDROID_S

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Change by STINNER Victor : -- pull_requests: +4606 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue32030] PEP 432: Rewrite Py_Main()

Change by STINNER Victor : -- pull_requests: +4607 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue32107] Improve MAC address calculation and fix test_uuid.py

Serhiy Storchaka added the comment: New changeset e69fbb6a560a02d0587b9075afd338a1e9073af0 by Serhiy Storchaka in branch 'master': Fix a regression in uuid added in bpo-32107. (#4677) https://github.com/python/cpython/commit/e69fbb6a560a02d0587b9075afd338a1e9073af0 -- __

[issue32211] Document the bug in re.findall() and re.finditer() in 2.7 and 3.6

New submission from Serhiy Storchaka : >>> re.findall(r'^|\w+', 'two words') ['', 'wo', 'words'] Seems the current behavior was documented incorrectly in issue732120. It will be fixed in 3.7 (see issue1647489, issue25054), but I hesitate to backport the fix to 3.6 and 2.7 because this can brea

[issue32212] few discrepancy between source and docs in logging

New submission from Michal Plichta : my code: logger = logging.getLogger(name) logger.setLevel(level=logging.DEBUG) ... stream_handler = logging.StreamHandler(stream=stdout) stream_handler.setLevel(logging_level) stream_handler.setFormatter(fmt=formatter) and mypy-0.550 complains about fmt vs.

[issue32211] Document the bug in re.findall() and re.finditer() in 2.7 and 3.6

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +4608 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-

[issue32199] uuid.getnode() should return the MAC address on Android

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +4609 stage: needs patch -> patch review ___ Python tracker ___ ___ Pyt

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Mark Shannon added the comment: I plan to resurrect my original design over the Christmas break. The reason that I want to get back to the original design is its consistency and relative simplicity. Duplicating the finally block for every exit from the try body might sound expensive, but it o

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Antoine Pitrou added the comment: Le 04/12/2017 à 12:46, Mark Shannon a écrit : > > I plan to start from > https://github.com/python/cpython/pull/2827/commits/693b9398b5fd202fa5864f9cc76fa1bc7f84f62e > as that adheres to the original design, but cleans up the code. > Antoine that is on your br

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

STINNER Victor added the comment: "./Program/_testembed.exe bpo20891" fails randomly on macOS: --- macbook:master haypo$ while true; do ./Programs/_testembed bpo20891 ||break; date; done Lun 4 déc 2017 12:46:34 CET Lun 4 déc 2017 12:46:34 CET Lun 4 déc 2017 12:46:34 CET Fatal Python error: P

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

Antoine Pitrou added the comment: Why not *always* call PyEval_InitThreads() at interpreter initialization? Are there any downsides? -- ___ Python tracker ___ ___

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

STINNER Victor added the comment: > Why not *always* call PyEval_InitThreads() at interpreter initialization? > Are there any downsides? The code is quite old: commit 1984f1e1c6306d4e8073c28d2395638f80ea509b Author: Guido van Rossum Date: Tue Aug 4 12:41:02 1992 + * Makefile adap

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

STINNER Victor added the comment: The "if (gil_created())" check can be found in the Py_BEGIN_ALLOW_THREADS / Py_END_ALLOW_THREADS macros which call PyEval_SaveThread() / PyEval_RestoreThread(): PyThreadState * PyEval_SaveThread(void) { PyThreadState *tstate = PyThreadState_Swap(NULL);

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

Antoine Pitrou added the comment: > I guess that the intent of dynamically created GIL is to reduce the > "overhead" of the GIL when 100% of the code is run in single thread. I'm not sure it is ok to guess here. The original code was written in 1992, when system threading APIs were buggy and

[issue1647489] zero-length match confuses re.finditer()

Serhiy Storchaka added the comment: New changeset 70d56fb52582d9d3f7c00860d6e90570c6259371 by Serhiy Storchaka in branch 'master': bpo-25054, bpo-1647489: Added support of splitting on zerowidth patterns. (#4471) https://github.com/python/cpython/commit/70d56fb52582d9d3f7c00860d6e90570c625937

[issue25054] Capturing start of line '^'

Serhiy Storchaka added the comment: New changeset 70d56fb52582d9d3f7c00860d6e90570c6259371 by Serhiy Storchaka in branch 'master': bpo-25054, bpo-1647489: Added support of splitting on zerowidth patterns. (#4471) https://github.com/python/cpython/commit/70d56fb52582d9d3f7c00860d6e90570c625937

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Serhiy Storchaka added the comment: I started on Antoine's PR and work on different approach (https://github.com/serhiy-storchaka/cpython/pull/1) which don't duplicate the code for continue/break/return. Instead it uses some kind of subroutines. END_FINALLY expects the one of three cases: 1.

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Antoine Pitrou added the comment: Le 04/12/2017 à 13:25, Serhiy Storchaka a écrit : > > I started on Antoine's PR and work on different approach > (https://github.com/serhiy-storchaka/cpython/pull/1) which don't duplicate > the code for continue/break/return. Instead it uses some kind of subr

[issue32030] PEP 432: Rewrite Py_Main()

STINNER Victor added the comment: New changeset 31a8393cf6a74c870c3484dd68500619f6232c6d by Victor Stinner in branch 'master': Revert "bpo-32197: Try to fix a compiler error on OS X introduced in bpo-32030. (#4681)" (#4694) https://github.com/python/cpython/commit/31a8393cf6a74c870c3484dd6850

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

STINNER Victor added the comment: New changeset 31a8393cf6a74c870c3484dd68500619f6232c6d by Victor Stinner in branch 'master': Revert "bpo-32197: Try to fix a compiler error on OS X introduced in bpo-32030. (#4681)" (#4694) https://github.com/python/cpython/commit/31a8393cf6a74c870c3484dd6850

[issue32212] few discrepancy between source and docs in logging

R. David Murray added the comment: I don't understand what the bug is that you are reporting here. Can you clarify? mypy isn't part of the stdlib, so an explanation in terms of what's in the stdlib would be helpful. -- nosy: +r.david.murray ___ P

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

STINNER Victor added the comment: Oh sorry, I missed the macOS failure and I wasn't available last week-end for quickly fix it. So thanks Serhiy for the revert ;-) I reapplied my changes with the following fix. test_embed randomly failed, but it's unrelated (I was able to reproduce the bug on

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

STINNER Victor added the comment: I tested manually that compilation and tests succeed on macOS. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Serhiy Storchaka added the comment: > The problem is that makes the stack consumption of END_FINALLY variable. > How about always consuming 6 items, even when most of them are unused > padding? Right. Though the value of the stack increment makes sense only for the case 1, because in other cas

[issue32212] few discrepancy between source and docs in logging

Michal Plichta added the comment: see at typeshed: https://github.com/python/typeshed/blob/master/stdlib/2and3/logging/__init__.pyi#L147 def setLevel(self, lvl: Union[int, str]) -> None: ... def setFormatter(self, form: 'Formatter') -> None: ... this match python documentation: Handler

[issue32197] Compiling against master branch fails; error: expected expression SET_DECODE_ERROR

Sanyam Khurana added the comment: Hey Victor, thanks for the update. I was confused about how the macro was replaced in the previous version. -- ___ Python tracker ___ ___

[issue32212] few discrepancy between source and docs in logging

R. David Murray added the comment: Ah. I'm guessing Vinay will probably want to fix the docs, then, since that's less disruptive backward compatibility wise. -- nosy: +vinay.sajip ___ Python tracker ___

[issue32212] few discrepancy between source and docs in logging

Change by R. David Murray : -- stage: -> needs patch versions: +Python 3.7 -Python 3.4, Python 3.5 ___ Python tracker ___ ___ Python

[issue32035] Documentation of zipfile.ZipFile().writestr() fails to mention that 'data' may also be bytes

Change by Chirag Rathod : -- keywords: +patch pull_requests: +4610 stage: needs patch -> patch review ___ Python tracker ___ ___ Pyth

[issue32212] few discrepancy between source and docs in logging

Michal Plichta added the comment: Nice, btw maybe other parameters in logging's docs needs to be corrected. -- ___ Python tracker ___ __

[issue32213] assertRaises and subTest context managers cannot be nested

New submission from Paul Ganssle : The TestCase.assertRaises and TestCase.subTest macros apparently don't interact with each other well. To demonstrate, consider the following code: from unittest import TestCase class SubTestRaisesTest(TestCase): def test_assert_outer(self):

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Mark Shannon added the comment: Serhiy, I assume that you plan to use something like the JVM's JSR/RET instruction pair. https://docs.oracle.com/javase/specs/jvms/se9/html/jvms-6.html Is that right? My reasons for preferring the finally-block duplication approach is that it keeps the interpr

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

Guido van Rossum added the comment: Yeah, the original reasoning was that threads were something esoteric and not used by most code, and at the time we definitely felt that always using the GIL would cause a (tiny) slowdown and increase the risk of crashes due to bugs in the GIL code. I'd be hap

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Antoine Pitrou added the comment: Le 04/12/2017 à 16:21, Mark Shannon a écrit : > > My reasons for preferring the finally-block duplication approach is that it > keeps the interpreter simpler and minimises the amount work done when no > exception is raised. As demonstrated, the increase in th

[issue32205] test.pythoninfo does not print the cross-built sysconfig data

STINNER Victor added the comment: I'm not sure of the purpose of this change. You can please elaborate on you use case? You use cross-compilation, ok. But why do you want to run test.pythoninfo on the computer building Python, rather than the computer running tests? The purpose of test.pytho

[issue31901] atexit callbacks should be run at subinterpreter shutdown

Marcel Plch added the comment: I created a PR with fix on this issue - https://github.com/python/cpython/pull/4611 This makes Py_EndInterpreter() call atexit callbacks for the subinterpreter it is destroying. It doesn't make Py_Finalize() end all subinterpreters, as the current implementati

[issue32213] assertRaises and subTest context managers cannot be nested

R. David Murray added the comment: To be pedantic, are not macros, they are context managers :) Your first case is not something I would have thought of coding. In the to_raise=True case, the subTest is failing because an exception is raised inside its scope. In the to_raise=False case, the

[issue32213] assertRaises and subTest context managers cannot be nested

Paul Ganssle added the comment: @r.david.murray So it is, my mistake. I think I was conflating issues when this first came up, and then I didn't notice that the order the test cases printed in was different than I expected. -- stage: -> resolved status: open -> closed __

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Serhiy Storchaka added the comment: Right, this is similar to how the JSR/RET pair was used in for calling the finally block. It seems the main drawback of duplicating of the finally code is not increasing the code size (which can be exponential in degenerate cases), but the problem with det

[issue32213] assertRaises and subTest context managers cannot be nested

R. David Murray added the comment: Yes, that's an easy mistake to make. I avoided it by only running one of the tests cases at a time, and I'll admit I had to think about it for a while to understand what was going on in your first case. -- ___ Py

[issue32205] test.pythoninfo does not print the cross-built sysconfig data

STINNER Victor added the comment: "make pythoninfo" is an alias for ./python -m test.pythoninfo. I added to support Python compiled in shared mode (./configure --enable-shared) and macOS which requires ./python.exe. Obviously, for a specific buildbot or specific script, you are free to run d

[issue32205] test.pythoninfo does not print the cross-built sysconfig data

STINNER Victor added the comment: See also bpo-32210: Add the versions of the Android SDK and NDK to test.pythoninfo. -- ___ Python tracker ___ ___

[issue32213] assertRaises and subTest context managers cannot be nested

Change by R. David Murray : -- resolution: -> not a bug ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue32210] Add the versions of the Android SDK and NDK to test.pythoninfo

STINNER Victor added the comment: Maybe add a collect_android() function which would exit early if sys.getandroidapilevel() doesn't exist? > * The NDK version can be obtained by parsing the file > $ANDROID_NDK_ROOT/source.properties. > * The versions of the SDK build-tools, emulator and platf

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Mark Shannon added the comment: On 04/12/17 16:56, Serhiy Storchaka wrote: > > Serhiy Storchaka added the comment: > > Right, this is similar to how the JSR/RET pair was used in for calling the > finally block. > > It seems the main drawback of duplicating of the finally code is not > incre

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

Change by STINNER Victor : -- pull_requests: +4612 stage: resolved -> patch review ___ Python tracker ___ ___ Python-bugs-list mailin

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

STINNER Victor added the comment: I wrote the PR 4700 to create the GIL in Py_Initialize(). Would you be ok to backport this fix to Python 2.7 and 3.6 as well? -- ___ Python tracker _

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Change by Paul Ganssle : -- pull_requests: +4611 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Mark Shannon added the comment: Actually looking back at the original patch, the gap between __enter__ and SETUP_FINALLY *was* in the original patch. My mistake. The fix would to be restore SETUP_WITH. The complexity we really want to get rid of is at the end of the with statement not the st

[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

Neil Schemenauer added the comment: After studying the patch and doing some reading, I prefer the finally-block duplication approach as well. Java does it that way as well and it works for them. It would be be interesting to compile a large body of packages and see what the increase in byte

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

Guido van Rossum added the comment: For 2.7 I hesitate to OK this, who knows what skeletons are still in that closet. It doesn't sound like a security fix to me. For 3.6 I'm fine with it as a bugfix. -- ___ Python tracker

[issue32205] test.pythoninfo does not print the cross-built sysconfig data

Xavier de Gaye added the comment: I may have misunderstood the scope of pythoninfo. On Android the readline or sqlite versions are known at build time since they have to be built at that time, but much more useful information can be obtained (or will be obtained) from python running on the de

[issue19610] Give clear error messages for invalid types used for setup.py params (e.g. tuple for classifiers)

Neil Schemenauer added the comment: Don't be sorry. We are all passionate about making Python better. distutils will be better once we gets this sorted out. Berker deserves credit for seeing an issue and developing on a fix for it. The collaboration between all the core developers is maki

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Change by Terry J. Reedy : -- pull_requests: +4613 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue32208] Improve semaphore documentation

Antoine Pitrou added the comment: The changes you are proposing sound reasonable to me. Would you like to submit a pull request for them? -- assignee: -> docs@python components: +Documentation nosy: +docs@python, pitrou stage: -> needs patch versions: -Python 3.4, Python 3.5, Pytho

[issue32175] Add hash auto-randomization

Antoine Pitrou added the comment: Agreed this is not desirable at this point. Let's leave 2.7 like it is. -- nosy: +pitrou ___ Python tracker ___ _

[issue21621] Add note to 3.x What's New re Idle changes in bugfix releases

Terry J. Reedy added the comment: #21961 ends with the entry I added for 3.4 and 3.5. 3.7 (and checking 3.6) will be a new issue. -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> Add What's New for Idle. __

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Terry J. Reedy added the comment: New changeset 21255fc3932a60c064f85c0fe68f2840f390ebe4 by Terry Jan Reedy in branch 'master': bpo-30928: Update idlelib/NEWS.txt to 2017 Dec 3. (#4701) https://github.com/python/cpython/commit/21255fc3932a60c064f85c0fe68f2840f390ebe4 --

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Change by Roundup Robot : -- pull_requests: +4614 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue32175] Add hash auto-randomization

Raymond Hettinger added the comment: Marking as closed for the reasons listed by the other respondents. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker __

[issue32207] IDLE: run's tk update adds context traceback on callback error

Change by Terry J. Reedy : -- keywords: +patch pull_requests: +4615 stage: needs patch -> patch review ___ Python tracker ___ ___ Pyt

[issue32207] IDLE: run's tk update adds context traceback on callback error

Terry J. Reedy added the comment: Thanks. I am still puzzled why the nested within nested try-except did not work as I expected, but I care more about fixing this. The result based on your suggestion is better (to read, I think) than extra nesting that did work. -- stage: patch revie

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Terry J. Reedy added the comment: New changeset 6e687948b0025a1ab0d0773efe62ce64f0c745fc by Terry Jan Reedy (Miss Islington (bot)) in branch '3.6': bpo-30928: Update idlelib/NEWS.txt to 2017 Dec 3. (GH-4701) (#4702) https://github.com/python/cpython/commit/6e687948b0025a1ab0d0773efe62ce64f0c74

[issue32214] Implement PEP 557: Data Classes

New submission from Eric V. Smith : PR to follow. Development was at https://github.com/ericvsmith/dataclasses -- assignee: eric.smith components: Library (Lib) messages: 307596 nosy: eric.smith, ned.deily priority: normal severity: normal status: open title: Implement PEP 557: Data Clas

[issue32207] IDLE: run's tk update adds context traceback on callback error

Change by Terry J. Reedy : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue32214] Implement PEP 557: Data Classes

Change by Eric V. Smith : -- keywords: +patch pull_requests: +4616 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue32207] IDLE: run's tk update adds context traceback on callback error

Terry J. Reedy added the comment: New changeset 1e2fcac4972530aa2c963d7e4011021df5ba866e by Terry Jan Reedy in branch 'master': bpo-32207: Improve tk event exception tracebacks in IDLE. (#4703) https://github.com/python/cpython/commit/1e2fcac4972530aa2c963d7e4011021df5ba866e --

[issue32207] IDLE: run's tk update adds context traceback on callback error

Change by Roundup Robot : -- pull_requests: +4617 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Change by Terry J. Reedy : -- pull_requests: +4618 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue32214] Implement PEP 557: Data Classes

Eric V. Smith added the comment: New changeset f0db54a0a1823534606ed5ce5a772365ba694c41 by Eric V. Smith in branch 'master': bpo-32214: Implement PEP 557: Data Classes (#4704) https://github.com/python/cpython/commit/f0db54a0a1823534606ed5ce5a772365ba694c41 -- __

[issue32207] IDLE: run's tk update adds context traceback on callback error

Terry J. Reedy added the comment: New changeset 9da33c82124f27eb58ba4cf145675fe7a1035744 by Terry Jan Reedy (Miss Islington (bot)) in branch '3.6': bpo-32207: Improve tk event exception tracebacks in IDLE. (GH-4703) (#4705) https://github.com/python/cpython/commit/9da33c82124f27eb58ba4cf145675

[issue32207] IDLE: run's tk update adds context traceback on callback error

Change by Terry J. Reedy : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue32214] Implement PEP 557: Data Classes

Change by Eric V. Smith : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Terry J. Reedy added the comment: New changeset 2c0c68d927bfa557f98bac26644f5b64c4b135a7 by Terry Jan Reedy in branch 'master': bpo-30928: update idlelib/NEWS.txt. (#4706) https://github.com/python/cpython/commit/2c0c68d927bfa557f98bac26644f5b64c4b135a7 -- __

[issue30928] Copy modified blurbs to idlelib/NEWS.txt

Change by Roundup Robot : -- pull_requests: +4619 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue32175] Add hash auto-randomization

STINNER Victor added the comment: By the way, for a few other reasons, Python 3 is more secure than Python 2.7. If you care of security, please upgrade! -- ___ Python tracker

[issue32210] Add the versions of the Android SDK and NDK to test.pythoninfo

STINNER Victor added the comment: Oh, I forgot that pythoninfo already has: call_func(info_add, 'sys.androidapilevel', sys, 'getandroidapilevel') Well, that's the *build time* API level, not the most useful one, but still useful. -- ___ Python tra

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: P-ganssle seems to be proposing to limit parsing to exactly what “datetime.isoformat” produces; i.e. whole number of seconds, milliseconds or microseconds. Personally I would prefer it without this limitation, like in Mathieu’s patches. But P-ganssle has done

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Martin Panter added the comment: The other difference is Mattieu guarantees ValueError for invalid input strings, which I think is good. -- ___ Python tracker ___

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: The better is the enemy of the good here. Given the history of this issue, I would rather accept a well documented restrictive parser than wait for a more general code to be written. Note that we can always relax the parsing rules in the future.

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Mathieu Dupuy added the comment: I'm right now available again to work on this issue. I'll submit a pull request within a week with all issues addressed Le 4 déc. 2017 11:45 PM, "Alexander Belopolsky" a écrit : > > Alexander Belopolsky added the comment: > > The better is the enemy of the go

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Paul Ganssle added the comment: > The better is the enemy of the good here. Given the history of this issue, I > would rather accept a well documented restrictive parser than wait for a more > general code to be written. Note that we can always relax the parsing rules > in the future. This

[issue32208] Improve semaphore documentation

Garrett Berg added the comment: Gave it a shot! -- keywords: +patch pull_requests: +4620 stage: needs patch -> patch review ___ Python tracker ___ _

[issue32215] sqlite3 400x-600x slower depending on formatting of an UPDATE statement in a string

New submission from Brian Forst : We're moving some code from Python 2.7 to 3.6 and found a weird performance issue using SQLite in-memory and on-disk DBs with the built-in sqlite3 library. In Python 2.7, the two update statements below (excerpted from the attached file) run in the same amount

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Alexander Belopolsky added the comment: +1 on what Paul said. Mathieu, the goal for 3.7 will be to get Paul's PR merged. It will be great if you could help in reviewing it. We can return to the features in your PR during the 3.8 development cycle. -- __

[issue28556] typing.py upgrades

Change by Ivan Levkivskyi : -- pull_requests: +4621 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue32215] sqlite3 400x-600x slower depending on formatting of an UPDATE statement in a string

R. David Murray added the comment: I can confirm that there is a difference on linux as well, using the sqlite version for both 2.7 and 3.7: rdmurray@pydev:~/python/p27[2.7]>./python sqlite3_27_36_performance_bug.py First step: 3.22849011421 Second step: 3.2167429924 rdmurray@pydev:~/python/p

[issue32215] sqlite3 400x-600x slower depending on formatting of an UPDATE statement in a string

R. David Murray added the comment: ...using the *same* sqlite version... -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue32215] sqlite3 400x-600x slower depending on formatting of an UPDATE statement in a string

Change by R. David Murray : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue32216] Document PEP 557 Data Classes

New submission from Eric V. Smith : The documentation needs to be added. -- assignee: docs@python components: Documentation messages: 307614 nosy: docs@python, eric.smith priority: high severity: normal status: open title: Document PEP 557 Data Classes versions: Python 3.7 _

[issue28791] update sqlite to latest version before beta 1

Ned Deily added the comment: New changeset ca7562a7fea61646c1b40ace04deecf9903d34a1 by Ned Deily (Mariatta) in branch 'master': bpo-28791: Update macOS installer to use SQLite 3.21.0. (#4245) https://github.com/python/cpython/commit/ca7562a7fea61646c1b40ace04deecf9903d34a1 -- __

[issue28791] update sqlite to latest version before beta 1

Change by Ned Deily : -- pull_requests: +4622 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue32217] freeze.py fails to work.

New submission from Decorater : It seems on my system installed python 3.6.0 when invoking python 3.6.3's freeze.py it seems to fail with this traceback: python ..\externals\cpython\Tools\freeze\freeze.py pyeimport.py Traceback (most recent call last): File "..\externals\cpython\Tools\freeze\

[issue15873] datetime: add ability to parse RFC 3339 dates and times

Paul Ganssle added the comment: > The other difference is Mattieu guarantees ValueError for invalid input > strings, which I think is good. I forgot to address this - but I don't think this is a difference in approaches. If you pass `None` or an int or something, the problem is with the type

[issue28791] update sqlite to latest version before beta 1

Ned Deily added the comment: New changeset a72e7bf563d5a9fb706a1775f5ae883a91b8a99f by Ned Deily in branch '3.6': [3.6] bpo-28791: Update macOS installer to use SQLite 3.21.0. (#4245) (#4711) https://github.com/python/cpython/commit/a72e7bf563d5a9fb706a1775f5ae883a91b8a99f -- __

[issue28791] update SQLite libraries for Windows and macOS installers

Ned Deily added the comment: > Should we mark issue 30952 'deferred blocker' too? No, that's a different matter. AFAICT, there is no standard option for that. -- ___ Python tracker _

[issue32217] freeze.py fails to work.

R. David Murray added the comment: Does the 3.6.0 freeze fail under 3.6.0, or the 3.6.3 freeze fail under 3.6.3? If not, there's no bug to report. -- nosy: +r.david.murray ___ Python tracker ___

[issue28791] update SQLite libraries for Windows and macOS installers

Ned Deily added the comment: I've updated the macOS installer for 3.7.0 and for 3.6.4. I'll leave this open for possible updating the Windows installer for 3.6.x (OK by me) and for possible updates for 2.7.x. -- stage: patch review -> needs patch title: update sqlite to latest versio

  1   2   >