Change by Ned Deily :
--
pull_requests: -29746
___
Python tracker
<https://bugs.python.org/issue38576>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
As Ronald notes, the issue isn't in venv, it's that the value of
sys._base_executable has changed between 3.10 and 3.11 for macOS builds.
$ /usr/local/bin/python3.10
Python 3.10.2 (v3.10.2:a58ebcc701, Jan 13 2022, 14:50:16) [Clang 13.0.0
(clang-1300.0.
Ned Deily added the comment:
New changeset 7dbb2f8eaf07c105f4d2bb0fe61763463e68372d by Miss Islington (bot)
in branch '3.10':
bpo-42982: update pbkdf2 example & add another link (GH-30966) (#30968)
https://github.com/python/cpython/commit/7dbb2f8eaf07c105f4d2bb0fe6
Change by Ned Deily :
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
stage: -> needs patch
versions: +Python 3.11
___
Python tracker
<https://bugs.python.org/i
Change by Ned Deily :
--
nosy: +orsenthil
___
Python tracker
<https://bugs.python.org/issue46870>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
Sorry, this slipped off my radar and I haven't gone back and checked older
versions of macOS. But it certainly is true that at least with the current
versions of the Apple Developer Tools (either the Command Line Tools or Xcode)
for macOS 11 (Big Sur) and
Ned Deily added the comment:
To reiterate, the example I gave had nothing to do with using a venv. The value
of sys._base_executable is now always wrong whether or not using a venv. The
consequences are more obvious when using a venv
Ned Deily added the comment:
Thanks for the suggested PR. And thanks for noticing, Erlend! I should have
checked with you first!
To reiterate what I noted on the PR, this (reduntant) change would only have
affected the Pythons provided by the python.org macOS installers; this behavior
New submission from Ned Deily :
The PYTHONEXECUTABLE is a holdover from old Python 2 days; AFAIK, it was
specifically to support the Build Applet tool which could be used to build
macOS app bundles in Python 2. The only place in current Py3 releases where it
is used is in the standard
Ned Deily added the comment:
Why are you using --prefix=/ ? Or better yet, please explain you are trying to
accomplish. A normal case would be --prefix=/some/path other than / and not use
DESTDIR. You won't be able to install into / on a current macOS system anyway.
--
Change by Ned Deily :
--
nosy: +vinay.sajip
___
Python tracker
<https://bugs.python.org/issue46914>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
My apologies: I'm not sure where I got the idea you were building on macOS!
In any case, this problem has come up a few times in the past, no doubt for a
similar reason, most recently in open issue Issue31114. I'm closing this issue
as a duplicate of
Ned Deily added the comment:
To emphasize, Python 3.9.2 is obsolete and no longer supported; at the moment,
the current release of Python 3.9 is 3.9.10. The most current bugfix release
(3.9.x) obsoletes all previous releases of that Python version (3.9); during a
version's support life
Change by Ned Deily :
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> BZip 1.0.6 Critical Vulnerability
___
Python tracker
<https://bugs.python
Change by Ned Deily :
--
assignee: -> steve.dower
priority: normal -> critical
title: BZip 1.0.6 Critical Vulnerability -> Update Windows installer to use
BZip 1.0.8
versions: +Python 3.10, Python 3.11
___
Python tracker
<https://bug
Change by Ned Deily :
--
title: Update Windows installer to use BZip 1.0.8 -> Update Windows installer
to use bzip2 1.0.8
___
Python tracker
<https://bugs.python.org/issu
Ned Deily added the comment:
New changeset 97476271275a4bd1340230677b7301d7b78b3317 by Steve Dower in branch
'3.7':
bpo-46948: Fix CVE-2022-26488 by ensuring the Windows Installer correctly uses
the install path during repair (GH-31730)
https://github.com/python/cpyt
Change by Ned Deily :
--
priority: critical -> release blocker
___
Python tracker
<https://bugs.python.org/issue44549>
___
___
Python-bugs-list mailing list
Un
Ned Deily added the comment:
We haven't released 2.4.6 yet for maintenance/security branches so we probably
should update to 2.4.7 first.
--
nosy: +corona10, lukasz.langa, ned.deily, pablogsal
priority: normal -> release blocker
___
Python
Ned Deily added the comment:
New changeset 4a3c610cd635f14747cf02c77908e80620aae6ea by Steve Dower in branch
'3.7':
bpo-44549: Update bzip2 to 1.0.8 in Windows builds to mitigate CVE-2016-3189
and CVE-2019-12900 (GH-31732) (GH-31735)
https://github.com/python/cpyt
New submission from Ned Deily :
gcc -o Python.framework/Versions/2.7/Python -dynamiclib \
-all_load libpython2.7.a -Wl,-single_module \
-install_name /tmp/a/empty
space/Python.framework/Versions/2.7/Python \
-compatibility_version 2.7
Ned Deily added the comment:
It turns out that supporting a framework path name that contains spaces (or
other special characters) is a much more pervasive change that I had originally
expected. That's because the path specified by ./configure --enable-framework=
also becomes the de
Ned Deily added the comment:
Have you looked at Bob Ippolito's xattr module which has been out for some time
and wraps Linux, OS X, BSD, and Solaris extended attributes?
http://pypi.python.org/pypi/xattr
--
nosy: +ned.deily
___
Python tr
Ned Deily added the comment:
Thanks for your suggested patch! A similar change was needed in idle
lib/ScriptBinding.py to handle the same case for script files in edit windows.
Applied in 3.2 (for 3.2.3) and default (for 3.3).
--
assignee: -> ned.deily
nosy: +ned.deily
resolut
New submission from Ned Deily :
In behavior carried over from Python 2 string literals, Python 3 byte string
literals raise a less helpful ValueError exception when an invalid hex escape
code is given:
>>> x = b'\x0'
ValueError: invalid \x escape
A string literal r
Ned Deily added the comment:
Thanks for the report. Fixed, although findertools is woefully obsolete and no
longer exists in Python 3. For working with the Finder in current OS X
releases, use appscript instead (http://pypi.python.org/pypi/appscript/).
--
assignee: ronaldoussoren
Ned Deily added the comment:
The database test failures were due to the fact that, on OS X, the tempdir was
created in /var which on OS X is actually a symlink to /private/var so the
tests for path inclusion which used startswith were failing. I added a call to
os.path.realpath to normalize
Ned Deily added the comment:
That won't work in IDLE because IDLE replaces the standard sys.stdout file
object with a special proxy object to capture stdout across its processes and
the proxy object does not currently support all of the attributes of a
io.TextTIOWrapper object, like e
Changes by Ned Deily :
--
nosy: +ghaering
___
Python tracker
<http://bugs.python.org/issue12993>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ned Deily :
--
nosy: +ghaering
___
Python tracker
<http://bugs.python.org/issue12997>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ned Deily :
--
nosy: +ned.deily
___
Python tracker
<http://bugs.python.org/issue13061>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
There is some confusion here, I think. As best as I can tell, the original
problem reported in the Stackoverflow question and to MacPorts involved using
the clang compiler, not llvm-gcc and the Decimal problem reported here was only
ever a problem when using
Ned Deily added the comment:
The problem can be reproduced on some other platforms depending on the version
of Tcl/Tk in use. But the supplied program violates the well-known if not
particularly well-documented restriction of tkinter programming that all Tk UI
operations must be on the main
Ned Deily added the comment:
>From the symptoms you describe, you are almost certainly trying to use a
>version of IDLE with the Cocoa Tcl/Tk 8.5 supplied by Apple in Mac OS X 10.6.
>That version of Tcl/Tk is known to be buggy. If you installed a 64-bit/32-bin
>version of Pyth
Ned Deily added the comment:
It turns out that the proposed fix here for pydoc was independently added in
the early days of Python 3 but was not backported. That fix for 2.7 plus a
fix-in-progress for Issue7367 (for both 2.7 and 3.x) and additional test cases
(also in progress) should
Changes by Ned Deily :
--
assignee: ronaldoussoren -> ned.deily
stage: -> committed/rejected
status: pending -> closed
title: Decimal module yields incorrect results when Python compiled with llvm
-> Decimal module yields incorrect results when Python compile
Changes by Ned Deily :
--
nosy: +orsenthil
stage: -> patch review
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue13104>
___
___
Python-
Ned Deily added the comment:
Thanks for the patch!
--
nosy: +ned.deily
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Ned Deily added the comment:
The applied changesets correct pkgutil's walk_packages for "classic" imports to
ignore unreadable directories the same way that the interpreter's import does.
With this fix to pkgutil, pydoc -k also no longer fails in this case. Applied
in
Ned Deily added the comment:
The applied changesets backport the "ignore exceptions" fix for pydoc -k from
3.x to 2.7 and also refactor test_pydoc to remove unneeded complexity and add
test cases for importing bad packages and unreadable package directories (a
problem addressed in
Changes by Ned Deily :
--
stage: patch review -> committed/rejected
___
Python tracker
<http://bugs.python.org/issue7425>
___
___
Python-bugs-list mai
Ned Deily added the comment:
Thanks for your suggested code and test. Somewhat different fixes to pkgutil
have been added by the changes for Issue7367 and a necessary backport of a fix
for pydoc from 3.x to 2.7 was made for Issue7425. With these fixes in place,
pydoc for 3.3.0, 3.2.3, and
Ned Deily added the comment:
This problem has been fixed with the changes for Issue7367 and, for 2.7,
Issue7425. They should appear in 3.3.0, 3.2.3, and 2.7.3.
--
resolution: -> duplicate
stage: test needed -> committed/rejected
status: open -> closed
s
Changes by Ned Deily :
--
nosy: +brian.curtin, tim.golden
___
Python tracker
<http://bugs.python.org/issue13078>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
The problem of pydoc apropos failing due to exceptions raised by pkgutil
walk_packages is fixed in 2.7.3 by the changes for Issue7425; they were already
fixed in 3.x.
--
nosy: +ned.deily
resolution: invalid -> duplicate
superseder: -> Impro
Changes by Ned Deily :
--
nosy: +georg.brandl
___
Python tracker
<http://bugs.python.org/issue13122>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
I don't have a strong opinion about whether running setup.py in IDLE is
supported. But that's not the real issue here. The problem is that the IDLE
RPC proxy of the standard IO streams is incomplete, in particular, the 'errors'
attribute
Ned Deily added the comment:
> sudo make frameworkinstall
While that shouldn't affect the Apple-supplied system Pythons, be aware that
with default ./configure settings this will overwrite any third-party Python
installs (like from the python.org installers) of the version in que
Ned Deily added the comment:
I forgot to mention that one advantage of using another framework and root
location, say, under your home directory somewhere, is that it is unnecessary
to use sudo. And you don't need to use the special target in any case, simply
"ma
Ned Deily added the comment:
This is related to Issue12342. The problem is that Tcl/Tk 8.5 (and earlier) do
not support Unicode code points outside the BMP range as in this example. So
IDLE will be unable to display such characters but it should not crash either.
--
assignee
Ned Deily added the comment:
The recent fixes do not address cases like here where importing a module causes
a crash in the interpreter process, usually due to some faulty third-party
extension module. One way to handle it more gracefully might be to move the
import scan to a separate
Ned Deily added the comment:
Thanks for the additional investigation. You don't see more in the traceback
because the exception is occurring in the _tkinter C glue layer. I am able to
reproduce the problem on some other platforms as well (e.g. Python 3.x on OS X
with Carbon Tk 8.4).
Ned Deily added the comment:
Just to be sure we're talking about the same thing here, my understanding is
that the "missing traceback" issues referred to here are only an issue when
IDLE is run as a stand-alone GUI program, such as can be done on Windows and
with the OS X IDL
Ned Deily added the comment:
Mark, you don't say what version of OS X or which Python you are using but, if
you are using an Apple-supplied Python on 10.6 or 10.7 or if you are using
python.org 64-bit/32-bit installers for 2.7 or 3.2, the Python standard library
sqlite3 modules dynami
Ned Deily added the comment:
What do you do for platforms like OS X where we support one set of binary files
that contain multi-architecture C-files that can run as Intel-64, Intel-32 or
PPC-32 on the same machine at user option at run time? For example, the
Apple-suppled system Python on
Changes by Ned Deily :
--
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue12997>
___
___
Python-bugs-
Ned Deily added the comment:
This sounds like an issue with Windows installation rather than an IDLE issue.
--
components: +Installation, Windows -IDLE
nosy: +brian.curtin, loewis, ned.deily, tim.golden
___
Python tracker
<http://bugs.python.
Ned Deily added the comment:
"./python.exe" is not a given on Mac OS X; that's only true if the file system
you are building in is case-insensitive, otherwise it is "./python". Suggest
rewording to:
"(you may need to use :file:`./python.exe` on Mac OS X&quo
Ned Deily added the comment:
I believe this was a bug specific to the llvm-gcc compiler shipped with Xcode
4.1 and possibly Xcode 4.0. I do not have Xcode 4 on OS X 10.6 but haypo's
test does fail with the llvm-gcc 4.2.1 that comes with Xcode 4.1 on 10.7. Can
you confirm exactly
Ned Deily added the comment:
In general, I would not recommend using anything other than an Apple-supplied
tool chain for building anything on Mac OS X. To help us better understand the
issues, can you say exactly which compilers you tried originally, i.e. the
complete --version output from
Ned Deily added the comment:
Oleg, thanks. That is consistent with previous reports; so far, this issue has
only been reported with llvm-gcc, not the plain gcc-4.2's shipped in Xcode
prior to 4.2.
--
___
Python tracker
<http://bugs.py
Ned Deily added the comment:
Haypo, the OP has a workaround. IMO, we should not be making any
recommendations about which Apple compiler to use on OS X 10.7 until we have
completed test cycles of each. There are too many variables at the moment. I
am doing that and should have results in a
Ned Deily added the comment:
With a current 3.3 build (i.e. "wide" build) on OS X, I can reproduce this. It
causes an exception on the execution of that command in the IDLE shell but it
doesn't crash IDLE. Not surprisingly, it doesn't seem to be reproducible with
Ned Deily added the comment:
Julian, I am able to build and run the current default (3.3) tip (52b35dae22d1)
on 10.7.2 with the gcc-4.2 from Xcode 4.1, with or without debug enabled. Are
you sure you have pulled all the latest updates and are using a clean build
directory? If so, please
Changes by Ned Deily :
--
resolution: accepted -> fixed
___
Python tracker
<http://bugs.python.org/issue6877>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Ned Deily :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue1681674>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
Sorry, I should have noticed earlier that this is a duplicate of Issue12342.
The problem is simply that Tcl/Tk does not currently support the display of
Unicode code points outside of the BMP. The question then is what IDLE to do
when asked to display such
Ned Deily added the comment:
(Merging CC list from duplicate Issue13265.
--
nosy: +ezio.melotti, kbk, maniram.maniram, serwy
___
Python tracker
<http://bugs.python.org/issue12
New submission from Ned Deily :
Currently in the default (pre-3.3) branch, IDLE fails if its Restart Shell
command is attempted:
Exception in Tkinter callback
Traceback (most recent call last):
File "Lib/tkinter/__init__.py", line 1397, in __call__
return self.func(*args)
Changes by Ned Deily :
--
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file23565/issue13300-3x.patch
___
Python tracker
<http://bugs.python.org/issu
Ned Deily added the comment:
Thanks for the patch! Committed to 27 (for release in 2.7.3), 32 (for 3.2.3),
and default (for 3.3).
--
assignee: -> ned.deily
nosy: +ned.deily
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
versions: +Python 3.3
Changes by Ned Deily :
--
nosy: +ghaering
___
Python tracker
<http://bugs.python.org/issue13299>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
I can fairly easily reproduce the hang on a current OS X system and the latest
patch appears to solve the problem. Looks good to me.
--
nosy: +ned.deily
stage: needs patch -> patch review
___
Python tracker
&l
Ned Deily added the comment:
LGTM. Thanks for the patch! Committed to 27 (for release in 2.7.3), 32
(3.2.3), and default (3.3).
--
assignee: -> ned.deily
nosy: +ned.deily
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
versions: +Python 2.7
Ned Deily added the comment:
The issue is indeed with chown call. The call that fails has a gid of -1,
truncated to 4294967295, which is a valid gid on OS X ('nogroup'). The
Apple-supplied Python 2.7.1 in OS X 10.7 fails running under sudo as root:
Python 2.7.1 (r271:86832, Jun 1
Ned Deily added the comment:
For some reason, Apple is patching Modules/posixmodule.c in a way that reverts
the fixes to chown in Issue1747858. You can see the patches for their 10.7.2
python 2.7 here:
http://opensource.apple.com/source/python/python-57/2.7/fix/posixmodule.c.ed
It probably
Changes by Ned Deily :
--
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue13315>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Ned Deily :
--
status: pending -> open
title: Unable to deal with large tarfile -> tarfile extract fails on OS X
system python due to chown of gid=-1
___
Python tracker
<http://bugs.python.org/i
Ned Deily added the comment:
shelve is behaving as documented. Because the shelve dictionary entry is
mutable (a dictionary), you need to set writeback=True to get the behavior you
expect. http://docs.python.org/library/shelve.html
--
nosy: +ned.deily
resolution: -> invalid
st
Ned Deily added the comment:
Lucas, exactly what source version of Python are you trying to build (i.e what
does "hg summary" say)?
--
___
Python tracker
<http://bugs.python.o
Ned Deily added the comment:
A request for this change in behavior is already being tracked by Issue10364.
--
nosy: +ned.deily
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> IDLE: make .py default added exten
Changes by Ned Deily :
--
nosy: +Kaleb702
___
Python tracker
<http://bugs.python.org/issue10364>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ned Deily :
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Ned Deily added the comment:
Thanks for you interest in improving Python. As noted in the response to one of
your other issues, we generally do not do style cleanups just for the sake of
style cleanups. In addition, our policy for current maintenance branches, like
Python 2.7, is to apply
Ned Deily added the comment:
Lucas, there is nothing particularly special about the configuration parameters
that Michael used other than enabling debug. Prior to Xcode 4, Xcode supplied
a "standard" (non-LLVM) gcc as the default compiler, 4.2 for 10.6 and 4.0 for
10.5 and 10.4.
Ned Deily added the comment:
Since you mention 2.7.1, presumably you are using the Apple-suppled Python
2.7.1 in OS X. That Python is not linked with GNU readline, rather the BSD
libedit library. As a workaround you could try installing the third-party
readline package from PyPI which
Ned Deily added the comment:
I can reproduce that using a Python that uses the Apple-suppled Tcl 8.4
framework in OS X 10.4.11. That version of Tcl 8.4 is quite old. If you are
using a Python 2.7.x from a python.org installer, you may be able to use a
newer version of Tcl by installing a
Changes by Ned Deily :
--
nosy: +amaury.forgeotdarc
___
Python tracker
<http://bugs.python.org/issue12988>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
Thank for the suggestion! BTW, a similar change had been recently made to
Python 3 for Issue9871 for invalid byte strings.
--
assignee: -> ned.deily
nosy: +ned.deily
resolution: -> fixed
stage: -> committed/rejected
status: open -> clo
Ned Deily added the comment:
Support for Berkeley DB (the bsddb) was removed from the standard library in
Python 3 and replaced by a third-party module (bsddb3) listed in PyPI which is
better able to keep up with changes in the various BDB releases.
http://docs.python.org/py3k/whatsnew/3.0
Ned Deily added the comment:
LGTM
--
___
Python tracker
<http://bugs.python.org/issue13371>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Ned Deily added the comment:
I am able to reproduce the problem on 2.7 OS X 10.7 64-bit.
unicode._encodedecimal is gobbling up memory. Looks like length is incorrect.
Breakpoint 1, unicode_encodedecimal (self=0x0, args=0x1007ce0d0) at
/Users/nad/Projects/PyDev/active/temp/u27-clang/Modules
Ned Deily added the comment:
That fixes it.
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Ned Deily :
--
assignee: -> ned.deily
___
Python tracker
<http://bugs.python.org/issue13501>
___
___
Python-bugs-list mailing list
Unsubscri
Ned Deily added the comment:
#10364 covers point 7 (make .py default added extension on save)
--
dependencies: +IDLE: make .py default added extension on save
nosy: +ned.deily
___
Python tracker
<http://bugs.python.org/issue13
New submission from Ned Deily :
Since AFAIK Apple does not currently ship a version of liblzma with Mac OS X,
the OS X installer build script should be modified to build and link a version
in support of the new lzma module (Issue6715).
Mac/BuildScript/build-installer.py
http://tukaani.org/xz
Ned Deily added the comment:
I've opened Issue13507 to track adding liblzma to the OS X installer builds.
--
nosy: +ned.deily
___
Python tracker
<http://bugs.python.org/i
Ned Deily added the comment:
Is there any reason to believe that the problem is confined to OS X?
--
nosy: +ned.deily, neologix
___
Python tracker
<http://bugs.python.org/issue13
Ned Deily added the comment:
Without having yet done a detailed review of the patch and the configure
options, I don't see a need to open a second issue. The scope of this one is
fine: generalizing the support of libedit to other plat
Ned Deily added the comment:
Thanks for the patch, Tal, and thanks for testing it, Roger. Applied to 3.2
for release in 3.2.3 and to default for 3.3.0.
--
assignee: -> ned.deily
nosy: +ned.deily
resolution: works for me -> fixed
stage: -> committed/rejected
status: open
101 - 200 of 6927 matches
Mail list logo
