Ned Deily added the comment:
See Issue37990 for a report of a regression introduced by these changes.
--
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/issue37
Ned Deily added the comment:
Thanks for the report. It looks like this regression was introduced by the
changes for Issue37729.
--
assignee: -> inada.naoki
keywords: +3.8regression
nosy: +inada.naoki, ned.deily
priority: normal -> high
stage: -> needs patch
versions: +P
Change by Ned Deily :
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
versions: +Python 3.8
___
Python tracker
<https://bugs.python.or
Change by Ned Deily :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue37996>
___
___
Change by Ned Deily :
--
resolution: -> duplicate
stage: test needed -> resolved
status: open -> closed
superseder: -> Implement PyOS_CheckStack on macOS using pthread_get_stack*_np
___
Python tracker
<https://bugs.python
Ned Deily added the comment:
When building a default 64-bit-only Python on current MacOS systems, don't use
the --enable-universalsdk (and --with-universal-arch) options to ./configure
since system header files are no longer installed in /usr/include.
Be aware that you may have to s
Ned Deily added the comment:
I'm not sure what happened here or why we haven't noticed it before. For
example, it appears that the consolidated blurb file for the earliest example,
3.5.2rc1.rst, has not been modified since its original blurbifi
Ned Deily added the comment:
Ah, some further insight: I realized that the original docset for 3.5.2 is
available in the documentation archive. Comparing the (pre-blurb) changelog
from the original release to its current state:
https://docs.python.org/release/3.5.2/whatsnew/changelog.html
Ned Deily added the comment:
I don't have an opinion about the bulk of the proposed change. But, since
_osx_support was mentioned as a model for an _aix_support, I wanted to comment
on the history of _osx_support. _osx_support was created as a separate module
back when the distutils2
Change by Ned Deily :
--
stage: -> resolved
status: pending -> closed
___
Python tracker
<https://bugs.python.org/issue38027>
___
___
Python-bugs-list
Change by Ned Deily :
--
nosy: +barry, maxking, r.david.murray
___
Python tracker
<https://bugs.python.org/issue36226>
___
___
Python-bugs-list mailing list
Unsub
Change by Ned Deily :
--
nosy: +brett.cannon, eric.snow, ncoghlan
___
Python tracker
<https://bugs.python.org/issue35923>
___
___
Python-bugs-list mailin
Ned Deily added the comment:
NumPy has a very complex build and install process including supplying its own
modified version of Distutils. You should take up any build and install issues
first with the NumPy project and then, if you both agree that there appears to
be a problem in Python
Ned Deily added the comment:
The traceback you provide in the first message:
File
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pip/_internal/wheel.py",
line 324, in move_wheel_files
scheme = distutils_scheme(
File
"/Lib
Ned Deily added the comment:
Yeah, I agree that increasing the timeout shouldn't be the answer here. I still
have never seen failure modes like this when running my own tests. The idea
about CPUs is one worth pursuing although I usually run with -j3. Also I
wonder how much memory t
Change by Ned Deily :
--
versions: -Python 2.7, Python 3.5, Python 3.6
___
Python tracker
<https://bugs.python.org/issue37858>
___
___
Python-bugs-list mailin
Ned Deily added the comment:
Please give an example of how this is a problem in using Python. You don't give
any context here.
--
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/is
Ned Deily added the comment:
"2to3 is a Python program that reads Python 2.x source code and applies a
series of fixers to transform it into valid Python 3.x code."
The example you supply, badvar,py, is not a valid Python 2.x program. Python 2
identifiers cannot contain such
Ned Deily added the comment:
Benjamin, can you answer Justin's question above?
--
nosy: +benjamin.peterson
___
Python tracker
<https://bugs.python.org/is
Ned Deily added the comment:
> 2to3 should be able to parse valid Python 3 code.
OK, then should the original behavior here be treated as a bug and fixed? If
so, this issue should be re-opened.
--
___
Python tracker
<https://bugs.pyth
Change by Ned Deily :
--
nosy: -ned.deily
stage: resolved -> needs patch
versions: +Python 3.9 -Python 3.5, Python 3.6
___
Python tracker
<https://bugs.python.org/issu
Ned Deily added the comment:
New changeset 61f34f9f63aab7503420603627ad5bd8902d904b by Ned Deily (Michael
Felt) in branch '3.7':
bpo-34720: Fix test_importlib.test_bad_traverse for AIX (GH-14238)
https://github.com/python/cpython/commit/61f34f9f63aab7503420603627ad5b
Change by Ned Deily :
--
versions: -Python 3.7
___
Python tracker
<https://bugs.python.org/issue34711>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ned Deily :
--
versions: -Python 3.7
___
Python tracker
<https://bugs.python.org/issue35704>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
The open proposed PR for this issue has been languishing unreviewed for several
months now. Since the proposal is really a request to change our development
process, I'm nosying Brett and Łukasz (3.9 RM). In any case, if we would
decide to add this to our
Ned Deily added the comment:
> If the pubkeys.txt on python.org has no benefit, why does it exist?
That's an excellent question! Based on the points raised here and elsewhere,
we discussed this more off-line and decided that we should remove the
pubkeys.txt file from the website s
Ned Deily added the comment:
(See later discussion and resolution in Issue37967.)
--
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/issue36
Ned Deily added the comment:
This issue does not seem to me to be a security issue so would not meet the
criteria for backporting to 3.6.
--
___
Python tracker
<https://bugs.python.org/issue33
Change by Ned Deily :
--
nosy: -ned.deily
___
Python tracker
<https://bugs.python.org/issue38035>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
The Windows and macOS installers also need to by updated to the new versions.
--
components: +Windows, macOS
nosy: +lukasz.langa, ned.deily, paul.moore, ronaldoussoren, steve.dower,
tim.golden, zach.ware
priority: normal -> release blocker
resolut
Change by Ned Deily :
--
pull_requests: +15780
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16170
___
Python tracker
<https://bugs.python.org/issu
Change by Ned Deily :
--
pull_requests: +15781
pull_request: https://github.com/python/cpython/pull/16171
___
Python tracker
<https://bugs.python.org/issue38
Ned Deily added the comment:
New changeset 24d1597e430498ebe2d3d18fba2cacb3957b494d by Ned Deily in branch
'master':
bpo-38117: Updated OpenSSL to 1.1.1d in macOS installer. (GH-16170)
https://github.com/python/cpython/commit/24d1597e430498ebe2d3d18fba2cac
Ned Deily added the comment:
New changeset 8dd358caf0d3f300ee64799812a020fe0de53637 by Ned Deily in branch
'2.7':
bpo-38117: Updated OpenSSL to 1.0.2t in macOS installer for 2.7.x. (GH-16171)
https://github.com/python/cpython/commit/8dd358caf0d3f300ee64799812a020
Ned Deily added the comment:
macOS 3.9, 3.8, 3.7 installers updated to 1.1.1d, macOS 2.7 installer updated
to 1.0.2t. Leaving open for Windows installers updates.
--
nosy: +benjamin.peterson
versions: +Python 2.7
___
Python tracker
<ht
Ned Deily added the comment:
If I understand Jason's message correctly, the changes for Issue30458
introduced a regression in 3.7.4 and will introduce the same regression in
other branches as they are released, including 3.5.8 whose rc1 is now in
testing. 3.7.5rc1 is scheduled to be t
Ned Deily added the comment:
See msg352596 in Issue30458 for discussion of whether the regression should be
considered a "release blocker" for the imminent 3.7.5 and 3.5.8 releases.
--
keywords: +3.7regression
nosy: +ned.deily
___
Pyth
Ned Deily added the comment:
> I've added 'release blocker' priority to don't miss this bugfix for the next
> release.
Note that 3.7.5rc1 is scheduled to be tagged today so we need to make a
decision on whether to hold the release for a fix. From a quick test, i
Change by Ned Deily :
--
stage: resolved -> needs patch
status: closed -> open
___
Python tracker
<https://bugs.python.org/issue34820>
___
___
Python-bugs-
Ned Deily added the comment:
Thanks for identifying this issue and breaking it out into a separate bpo,
Jason. If I understand correctly, the problematic fix for Issue30458 has
already been released in maintenance release 3.7.4 and security release 3.6.9,
is in the current security release
Ned Deily added the comment:
With the breaking out of the portential and/or actual regression (e.g. invalid
requests can no longer be crafted) into Issue38216, itself a potential release
blocker, we are still left here with the as-yet unresolved issue identified
above in msg34728 (e.g. not
Ned Deily added the comment:
Thanks for your comments, Greg. Here's my take as release manager for 3.7 (and
for 3.6). What bothers me here is that we apparently changed de facto behavior
between maintenance releases, in the middle of 3.7's lifecycle, without
warning, no doubt
Change by Ned Deily :
--
keywords: +security_issue
priority: normal -> high
versions: +Python 2.7, Python 3.5, Python 3.6, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issu
Ned Deily added the comment:
I am certainly not a domain expert but, at a high level, I think the approach
in PR 16321 is a reasonable compromise and I would support merging it to 3.7
and 3.6 (I'll let Larry and Benjamin speak for 3.5 and 2.7) assuming there are
no review objections.
Ned Deily added the comment:
Also, besides the normal news entry (via blurb), there should probably be a
"Notable changes in x.y.z" entry added to the end of each affected release's
Doc/whatsnew/x.y.rst file.
--
___
Python
Ned Deily added the comment:
> Will the latter to accept non-ascii values also be merged to security
> branches too given that it predates the security issue addressed ?
At this point, I'm willing to allow it in 3.6 unless someone identifies a
compelling re
Ned Deily added the comment:
I assume you are using a Python 3.7.x from a python.org macOS installer?
Support for macOS dark mode is almost entirely a Tk issue as Tkinter is
basically a shallow wrapper around Tk-provided APIs. We have been shipping Tk
8.6.8, s stable, slightly out-of-date
Change by Ned Deily :
Removed file: https://bugs.python.org/file48241/name of the past
___
Python tracker
<https://bugs.python.org/issue36210>
___
___
Python-bugs-list m
Ned Deily added the comment:
New changeset e4be8c984d035da30f9ed051aa6f3f762f0e9060 by Ned Deily (Michael
Felt) in branch '3.8':
bpo-36210: correct logic in setup.py for optional extensions for AIX (GH-12202)
(GH-16376)
https://github.com/python/cpyt
Change by Ned Deily :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9 -Python 3.7
___
Python tracker
<https://bugs.python.or
Change by Ned Deily :
--
nosy: +gvanrossum, levkivskyi
___
Python tracker
<https://bugs.python.org/issue38298>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
Perhaps this should be a release blocker for 3.5.8. Larry?
--
nosy: +larry, ned.deily
___
Python tracker
<https://bugs.python.org/issue38
Change by Ned Deily :
--
versions: -Python 3.5, Python 3.6
___
Python tracker
<https://bugs.python.org/issue38301>
___
___
Python-bugs-list mailing list
Unsub
Ned Deily added the comment:
New changeset 1698cacfb924d1df452e78d11a4bf81ae389 by Ned Deily (Victor
Stinner) in branch '3.6':
bpo-38243, xmlrpc.server: Escape the server_title (GH-16373) (GH-16441)
https://github.com/python/cpython/commit/1698cacfb924d1df452e78d11a4bf8
Change by Ned Deily :
--
nosy: +davin, pitrou
___
Python tracker
<https://bugs.python.org/issue38035>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
Thanks for the report but this is not something relevant to this issue tracker.
A quick whois lookup for the domain did not reveal an owner. Suggest you
pursue by asking the PSF infrastructure team via an email to
infrastructure-staff at python.org
Ned Deily added the comment:
New changeset 5b18ce60b432d1dfa6f6988be07dd55646201a9b by Ned Deily (Jason R.
Coombs) in branch '3.6':
[3.6] bpo-38216, bpo-36274: Allow subclasses to separately override validation
and encoding behavior (GH-16448) (GH-16462)
https://github.com/pyth
Ned Deily added the comment:
New changeset 5b18ce60b432d1dfa6f6988be07dd55646201a9b by Ned Deily (Jason R.
Coombs) in branch '3.6':
[3.6] bpo-38216, bpo-36274: Allow subclasses to separately override validation
and encoding behavior (GH-16448) (GH-16462)
https://github.com/pyth
New submission from Ned Deily :
Thanks for the PR! As noted in my review comment of it, I believe a more
robust approach would be needed to ensure that builds still work properly when
building with a local copy of SQLite on macOS (not the system-supplied one), a
common occurrence
Ned Deily added the comment:
Sorry, I should have checked: this issue has come up at least a couple of times
before, for example, Issue30646 and Issue24464 (still open with a slightly more
compex patch). Let's just close this issue as a duplicate of the earlier one
and continue an
Change by Ned Deily :
--
resolution: third party -> duplicate
superseder: -> Got warning when compiling sqlite3 module on Mac OS X
___
Python tracker
<https://bugs.python.org/i
Ned Deily added the comment:
Now that this has come up again, it's worth noting Ronald's comment in
msg295954 from duplicate Issue30646:
"See also <https://sqlite.org/c3ref/enable_shared_cache.html>. Apple basically
disabled this function starting at macOS 10.7, that&#x
Ned Deily added the comment:
Also, I notice that, while there is docstring help for
sqlite3.enable_shared_cache, it does not seem to be mentioned in the sqlite3
module doc page in the Library reference.
--
___
Python tracker
<ht
Ned Deily added the comment:
Nick, do you consider this a 3.8.0 release blocker? If so, you should reopen
it and mark it as such, since the 3.8.0rc1 cutoff is imminent.
--
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/issue38
Change by Ned Deily :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9 -Python 3.4, Python 3.5, Python 3.6
___
Python tracker
<https://bugs.python.or
Ned Deily added the comment:
Thanks for the reminder. Unfortunately, the macOS installer is working as
designed. As discussed at length in Issue18117 (and elsewhere), building using
the -framework Python, either directly in compiler calls or indirectly through
Xcode is problematic because
Ned Deily added the comment:
Since this sounds like a regression being introduced by 3.8.0, should the
reversion be included in 3.8.0 final or can it wait for 3.8.1?
--
keywords: +3.8regression
nosy: +lukasz.langa, ned.deily
___
Python tracker
Change by Ned Deily :
--
versions: -Python 3.7
___
Python tracker
<https://bugs.python.org/issue38350>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ned Deily :
--
keywords: -3.8regression
versions: -Python 3.8
___
Python tracker
<https://bugs.python.org/issue38266>
___
___
Python-bugs-list mailin
Ned Deily added the comment:
Also the similar single test in 2.7.x fails on 10.15 (pre-release):
==
ERROR: test_relative_path (test.test_py_compile.PyCompileTests
Ned Deily added the comment:
I verified it is exploitable via the sqlite3 module by adapting the test case
from the SQLite ticket (https://www.sqlite.org/src/info/e4598ecbdd18bd82). But
since it requires the exploiter to be able to specify raw SQL statements, it
doesn't sound like it
Ned Deily added the comment:
Sorry, you appear to be using a third-party packaging system that provides
Python for Android platforms. It's not something we provide or support. You
should ask your question of that project (python-for-android perhaps?) or on a
forum like StackOve
Ned Deily added the comment:
FWIW, the assertion error on macOS reported above in msg338774 does not seem to
occur anymore with current HEAD of master and with recent system clang (Apple
clang version 11.0.0 (clang-1100.0.33.8)) on macOS 10.14.6
Change by Ned Deily :
--
Removed message: https://bugs.python.org/msg354169
___
Python tracker
<https://bugs.python.org/issue38404>
___
___
Python-bugs-list m
Change by Ned Deily :
Removed file: https://bugs.python.org/file48646/2.jpg
___
Python tracker
<https://bugs.python.org/issue38404>
___
___
Python-bugs-list mailin
Change by Ned Deily :
--
Removed message: https://bugs.python.org/msg354170
___
Python tracker
<https://bugs.python.org/issue38404>
___
___
Python-bugs-list m
Change by Ned Deily :
--
nosy: -larry, pokeronlinejakarta
resolution: -> rejected
stage: -> resolved
status: open -> closed
title: Poker Online -> spam
type: crash ->
___
Python tracker
<https://bugs.pyt
Change by Ned Deily :
--
nosy: +vstinner
___
Python tracker
<https://bugs.python.org/issue38429>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
(Just FYI: the version of Tcl/Tk, 8.6.8, we are shipping with the python.org
installers for macOS is unchanged since 3.7.2 a year ago, 2.7.16 (in March),
and has not changed during the 3.8.0 pre-release cycle. We did try to update
to 8.6.9 for 3.7.2rc1 but
Ned Deily added the comment:
Thanks for the report. That problem was fixed on the master branch by
141da44bb45bc182886303fce92cbbae5631cb4c on 2019-06-03. Suggest you build from
a more recent source release or updated git repo.
--
nosy: +ned.deily
resolution: -> out of date
st
New submission from Ned Deily :
./configure's --with-universal-archs= supports a number of different CPU
architecture combinations. However most of them are no longer supported on
current macOS systems. If you choose an option with archs not available in the
build tool chain in use
Ned Deily added the comment:
Also note that, on current macOS systems, specifying just --enable-universalsdk
to ./configure results in an implicit --with-universal-archs of intel (which
implies both x86_64 and i386).
checking for --enable-universalsdk... /
checking for --with-universal
Ned Deily added the comment:
Going and back and looking closer at the original failure, I see now that the
root cause of the configure failures *is* using --with-universal-archs=64-bit.
As noted in the Mac/README file, "64-bit" means compile for both "ppc64" and
"x
Ned Deily added the comment:
Going back and looking closer at the original failure, I see now that the root
cause of the configure failures *is* using --with-universal-archs=64-bit. As
noted in the Mac/README file, "64-bit" means compile for both "ppc64" and
"x
Change by Ned Deily :
--
Removed message: https://bugs.python.org/msg354431
___
Python tracker
<https://bugs.python.org/issue38014>
___
___
Python-bugs-list m
Ned Deily added the comment:
(“8.7.10” should be “8.6.10”)
--
___
Python tracker
<https://bugs.python.org/issue38440>
___
___
Python-bugs-list mailing list
Unsub
Ned Deily added the comment:
Marking as regression release blocker for 3.7.5 final and 3.8.0 final.
--
keywords: +3.7regression
nosy: +lukasz.langa, martin.panter, ned.deily, vstinner
priority: normal -> release blocker
___
Python tracker
<
Ned Deily added the comment:
This change introduces a potential 3.7 regression; see Issue38449.
--
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/issue22
Ned Deily added the comment:
Thanks for the report! Those whatsnew issues are being addressed in PR 16621.
--
nosy: +ned.deily
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bug
Ned Deily added the comment:
It looks like Christian originally requested autobackports to both 3.8 and 3.7
but both failed due to git checkout errors. He then manually restarted the 3.8
backport but it looks like the 3.7 one did not get restarted. Christian, was
that intentional or just
Ned Deily added the comment:
Thanks for looking into this, @maxking. With both 3.8.0 final and 3.7.5 final
scheduled for just a few days away, I wonder if the best thing to do at this
point is to revert them and work on a more robust fix targeted for the next
maintenance releases since the
Ned Deily added the comment:
Thanks everyone for the quick action on this!
--
priority: release blocker -> normal
___
Python tracker
<https://bugs.python.org/issu
Ned Deily added the comment:
(On second thought, I'll leave this open as a release blocker until we've
cherry-picked the fixes for 3.8.0 final and 3.7.5 final.)
--
priority: normal -> release blocker
___
Python tracker
<https:/
Change by Ned Deily :
--
nosy: +akuchling, rhettinger
___
Python tracker
<https://bugs.python.org/issue38463>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ned Deily :
--
nosy: +akuchling, rhettinger
___
Python tracker
<https://bugs.python.org/issue38461>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ned Deily :
--
nosy: +akuchling, asvetlov, rhettinger, yselivanov
___
Python tracker
<https://bugs.python.org/issue38460>
___
___
Python-bugs-list m
Ned Deily added the comment:
Thanks for the input, @jmr! I realize that what I wrote was ambiguous so to
clarify I *have* tested that example with the final release versions of
Catalina and Xcode 11.1 and could not reproduce. Just for fun, I've also
tested with the latest deve
Change by Ned Deily :
--
nosy: +doko
___
Python tracker
<https://bugs.python.org/issue38472>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Ned Deily added the comment:
Your system appears to be running Cylance, which I gather is some sort of
third-party virus protection system; from the system crash trace, the crash
ssems to have happened in /Library/Application
Support/Cylance/Desktop/CyMemDef.dylib which presumably is part
Ned Deily added the comment:
New changeset ae41f629e187e1f0cf4d62f5a7b181c64da26466 by Ned Deily (Ricardo
Bánffy) in branch '3.7':
[3.7] bpo-38294: Add list of no-longer-escaped chars to re.escape
documentation. (GH-16442) (GH-16647)
https://github.com/python/cpyt
1101 - 1200 of 6927 matches
Mail list logo
