Change by Ronald Oussoren :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Ronald Oussoren added the comment:
The crash is not nice, but
The script contains the following line in the definition of status():
except status() as e:
That will cause unbounded recursion when os.fstat raises an exception, which
likely happens here. You probably want to catch
Change by Ronald Oussoren :
--
title: status() crashes on Python3.9 and 3.10 -> crash with unbounded recursion
in except statement
___
Python tracker
<https://bugs.python.org/issu
Ronald Oussoren added the comment:
The value of the recursion limit is not relevant here, I get the same crash
when I set the recursion limit to 100 (in my reproducer scriptlet).
There might be a missing recursion level check in the exception handling
machinery though, self-recursion in an
Ronald Oussoren added the comment:
As mentioned earlier I can reproduce this without calling os.fstat (python
3.9.1rc, macOS 10.15):
# ---
def status():
try:
1/0
except status():
pass
status()
#
The crash happens both with the default recursion limit as well with a
Ronald Oussoren added the comment:
See also #42500
--
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue42509>
___
___
Python-bugs-list m
Ronald Oussoren added the comment:
See also #42509
--
___
Python tracker
<https://bugs.python.org/issue42500>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ronald Oussoren added the comment:
Good catch.
--
___
Python tracker
<https://bugs.python.org/issue42504>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ronald Oussoren added the comment:
There's also macholib (which is used by py2app for rewriting mach-o headers).
Note that resigning for arm64 is possible using the following command:
$ codesign -s - --preserve-metadata=identifier,entitlements,flags,runtime -f
.
This was mentioned i
Ronald Oussoren added the comment:
I'm -1 on adding this API as it is inherently unsafe and is bound to be used in
locations where its contract is not honoured (especially outside of the core).
Note that the pre-condition on the argument is that you now only own a
reference to the o
Ronald Oussoren added the comment:
A private function is less problematic, but still far from ideal. Any use of
the function is IMHO a code smell that should be refactored.
I'm primarily against this function in the public API because it will be used
where it isn't appropriate
Ronald Oussoren added the comment:
BTW. Have you considered using coccinelle
<https://coccinelle.gitlabpages.inria.fr/website/> instead of a python script?
I have no experience with the tool, but it is meant to be used for code
transformation ("semantic patches"). I only
Ronald Oussoren added the comment:
The work in #441100 is merged into master and 3.9, including an (experimental)
"universal2" build of the latter in 3.9.1rc1 that is build with the latest SDK.
I'm therefore closing this issue.
--
dependencies: -Support macOS 11 an
Ronald Oussoren added the comment:
I totally understand, I would have done the same. Coccinelle looks like an
interesting tool for refactorings like this, but I prefer to write Python
scripts (and often just refactor manually).
--
___
Python
Ronald Oussoren added the comment:
Are you running in dark mode?
--
___
Python tracker
<https://bugs.python.org/issue42541>
___
___
Python-bugs-list mailin
Ronald Oussoren added the comment:
The problem seems to be that the window background doesn't adjust to dark mode,
while the window contents does.
I don't know if we should do something in Tkinter for this.
--
___
Python track
Ronald Oussoren added the comment:
With some luck it might be possible to work around this. If it isn’t we should
at least opt out of dark mode for IDLE by changing its Info.plist.
https://developer.apple.com/documentation/appkit/nsappearancecustomization
Ronald Oussoren added the comment:
FWIW I don't agree with this fix.
sys.get_config_var('MACOSX_DEPLOYMENT_TARGET') has always resulted in a string
value. There's bound to be someone relying on this.
As I wrote in comment on the PR a nicer fix is to
Ronald Oussoren added the comment:
This is a duplicate of #38261. I'm closing that other issue because this issue
has more discussion.
--
___
Python tracker
<https://bugs.python.org/is
Ronald Oussoren added the comment:
This is a duplicate of #42541.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Tkinter colours wrong on MacOS universal2
___
Python tracker
<https://
Ronald Oussoren added the comment:
It is possible to opt out of dark mode using a key in the Info.plist file. This
can also be used in the Python.app hidden in the framework to globally disable
support for dark mode.
I wouldn't switch back to 8.6.9, if only because that doesn
Ronald Oussoren added the comment:
The value *for this key* is a dot separated sequence of integer labels in a
string. The limit of that is a single integer label that could be converted to
a Python int.
With the current patch get_config_var('MACOSX_DEPLOYMENT_TARGET') mostly
Ronald Oussoren added the comment:
I'd prefer to (effectively) revert the PR and treat MACOSX_DEPLOYMENT_TARGET=11
the same as MACOSX_DEPLOYMENT_TARGET=11.0.
The same issue has crept up on the wheel and packaging repos (in the context of
changing the platform tag in wheel names).
Ronald Oussoren added the comment:
I might be able to debug during the weekend, but my main focus will be on back
porting the changes in #41100 to the 3.8 branch (or at least parts of it).
--
___
Python tracker
<https://bugs.python.org/issue42
Ronald Oussoren added the comment:
IMHO sysconfig.get_platform() and distutilis.util.get_platform() should always
return a version with a major and minor number on macOS.
Could you add more information on the system where you get a version number
that includes the micro version?
And to
Ronald Oussoren added the comment:
> Now, the next minor releases will be 11.0.1 (that has shipped already),
> 11.1.0 (will ship soon), then either 11.1.1 or 11.2.0 (we don't know). The
> next major version will of course be 12.0.0.
>
> The question is: for 11.1.x or 11.
New submission from Ronald Oussoren :
Which OS and version are you trying to install on?
--
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue42
Change by Ronald Oussoren :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<https://bugs.python.org/issue42
Ronald Oussoren added the comment:
https://math.stackexchange.com/questions/46975/how-to-prove-two-regular-expressions-are-identical-in-mathematical-way
contains some references to proofs that checking if two regular expressions
are equivalent is PSPACE-complete. Another answer in that
Change by Ronald Oussoren :
--
components: +macOS
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue38309>
___
___
Python-bugs-list mailin
Ronald Oussoren added the comment:
What platform are you using?
--
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue42614>
___
___
Pytho
Ronald Oussoren added the comment:
Does this affect unix-style builds with --enable-shared or framework builds?
For the latter the python executable is linked to the framework, and lib
python.dylib is an alias for the framework.
A related known problem is that linking an extension to a
Ronald Oussoren added the comment:
Currently macOS 11 is needed to build a universal2 framework. That because we
haven't spent time yet on detecting if the current compiler can compile for
arm64.
An easy workaround: Patch _osx_support.py, in particular the function
"_supports_ar
Ronald Oussoren added the comment:
Closing this issue, because this is a platform bug.
The reproducer in msg170147 works reliably for me on macOS 10.15 with Python
3.9, the system bug may have been fixed in the meantime.
--
components: +macOS
resolution: not a bug -> third pa
Ronald Oussoren added the comment:
What filesystem is used on macOS? If it is HFS+ you're likely running into
unicode normalisation in the filesystem.
That is, 'й' can be represented as a single unicode codepoint (and likely is in
your script), but in the NFD normalisation u
Change by Ronald Oussoren :
--
components: +macOS
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/issue42614>
___
___
Python-bugs-list mailin
Change by Ronald Oussoren :
--
Removed message: https://bugs.python.org/msg382880
___
Python tracker
<https://bugs.python.org/issue42616>
___
___
Python-bug
Change by Ronald Oussoren :
--
Removed message: https://bugs.python.org/msg382879
___
Python tracker
<https://bugs.python.org/issue42616>
___
___
Python-bug
Change by Ronald Oussoren :
--
components: +Distutils -2to3 (2.x to 3.x conversion tool), Argument Clinic, C
API, Cross-Build, asyncio, ctypes
nosy: +dstufft, eric.araujo, froody, ned.deily -Alex.Willmer, asvetlov,
yselivanov, zhtw1234
versions: -Python 3.6, Python 3.7
Ronald Oussoren added the comment:
I've removed two spammy comments and adjusted the categories (the latter
explains Larry's annoyance, someone selected all categories which automatically
added him to the nosy list).
--
___
Python track
Ronald Oussoren added the comment:
Linking extensions to libpython with a static build of python will cause
problems (as you described in your initial message).
The not very satisfactory response is "don't do that then". Note that
distutils won't link against libpython
Ronald Oussoren added the comment:
can this issue be closed?
--
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue38137>
___
___
Python-bug
Change by Ronald Oussoren :
--
components: +macOS
nosy: +ned.deily
___
Python tracker
<https://bugs.python.org/issue38137>
___
___
Python-bugs-list mailin
Ronald Oussoren added the comment:
I'm closing this as "not a bug" because this is likely caused by different
unicode normalisations for strings.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
Ronald Oussoren added the comment:
This might be related to #42500
--
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue42651>
___
___
Pytho
Ronald Oussoren added the comment:
This might be related to #42500
--
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue42652>
___
___
Pytho
Change by Ronald Oussoren :
--
components: +macOS
nosy: +ned.deily, ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue42688>
___
___
Python-bug
Ronald Oussoren added the comment:
Could you please sign the CLA? (See the PR for details on that)
The PR looks sane.
Out of interest: why do you use an external version of libffi? AFAIK the system
copy of libffi contains some magic sauce to work nicer with signed binaries
Ronald Oussoren added the comment:
How did you install python3.7?
Platform.machine() will return "x86_64" when running in Rosetta 3. That is,
when python itself is an x86_64 binary.
--
___
Python tracker
<https://bugs.python.o
Ronald Oussoren added the comment:
That installer contains intel (x86_64) binaries. The behaviour of
platform.machine() and platform.processor() is expected, due to Rosetta the
binary runs as if it is running on an Intel Mac.
There is a "universal2" installer for Python 3.9.1 whic
Change by Ronald Oussoren :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
superseder: -> crash with unbounded recursion in except statement
___
Python tracker
<https://bugs.python
Change by Ronald Oussoren :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
superseder: -> crash with unbounded recursion in except statement
___
Python tracker
<https://bugs.python
Change by Ronald Oussoren :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Ronald Oussoren added the comment:
What's the script used, is it the script in the reddit thread?
The reddit thread mentions a change to the script that might help:
return [await r.json() for r in responses]
To:
return await asyncio.gather(*(r.json() for r in responses))
Ronald Oussoren added the comment:
As another datapoint: This works for me on macOS 11.1 with the universal2
installer for Python 3.9.1 (which includes Tk 8.6.10).
--
___
Python tracker
<https://bugs.python.org/issue38
Ronald Oussoren added the comment:
W.r.t. building on 10.9: until very recently (trunk and 3.9.1) Python didn’t
check for symbol availability at runtime. Building on 10.9 is basically a
workaround for that.
The, for now experimental, “universal2” installer for 3.9.1 is build on Big Sur
and
Ronald Oussoren added the comment:
The API documentation already implies that write might not write the entire
buffer because it returns the number of bytes actually written (just like
os.write).
A possible workaround on the SSL layer is hence to clamp the amount of bytes to
write to
Change by Ronald Oussoren :
--
keywords: +patch
pull_requests: +23015
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24187
___
Python tracker
<https://bugs.python.org/issu
Ronald Oussoren added the comment:
I've added a (draft) PR for this. The PR is a this time not tested on a 10.15
system.
Another change that might be needed: ensure that sysconfig.get_platform() does
not return "universal2" as the binary architecture when the compiler do
Ronald Oussoren added the comment:
> Another change that might be needed: ensure that sysconfig.get_platform()
> does not return "universal2" as the binary architecture when the compiler
> does not support arm64.
Hmmm... _osx_support.get_platform_osx() contains th
Ronald Oussoren added the comment:
This is a recursion problem, "mystr" will be equivalent to
'hello123'.__sizeof__.__sizeof__. ...(100K repetition)... .__sizeof__. The
dealloc of "mystr" will cause recursive calls to tp_dealloc along the entire
chain an
Ronald Oussoren added the comment:
AFAIK you should specify the types of the fixed arguments for variadic
functions. The ABI for the M1 has a different calling convention of the
variadic arguments, the ctypes implementation counts how many variadic
arguments there are based on the specified
Ronald Oussoren added the comment:
I agree that this should be mentioned in the documentation for ctypes.
--
___
Python tracker
<https://bugs.python.org/issue42
Change by Ronald Oussoren :
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
___
Python tracker
<https://bugs.python.org/issu
Ronald Oussoren added the comment:
Note that there is a way to avoid this crash using the trashcan API (see the
use of Py_TRASHCAN_BEGIN in various implementation). This API is generally
only used for recursive data structures and because it has a performance cost
(based on what I've
Ronald Oussoren added the comment:
A list of stdlib modules/extensions is IMHO problematic for maintenance, esp.
if you consider that not all modules/extensions are installed on all systems
(both because dependencies aren't present and because packagers have decided to
unbundle parts o
Ronald Oussoren added the comment:
>> Wouldn't it be sufficient to somehow mark the stdlib entries on sys.path?
>> Although that might give misleading answers with tools like
>> pyinstaller/py2exe/py2app that package an application and its dependencies
>> into a
Ronald Oussoren added the comment:
> On 19 Jan 2021, at 12:30, STINNER Victor wrote:
>
> Ronald:
>> You wouldn't necessarily have to import a module to test, this is something
>> that could be added to importlib. One (poorly thought out) option is to add
&g
Ronald Oussoren added the comment:
BTW. A list of stdlib module names is not sufficient to determine if a module
is in the stdlib, thanks to .pth files it is possible to have entries on
sys.path before the stdlib.
--
___
Python tracker
<ht
Ronald Oussoren added the comment:
What kind of error do you get?
--
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue42970>
___
___
Pytho
Ronald Oussoren added the comment:
This might be a security feature in Big Sur, access to some locations is
restricted by default. I'm not sure if that includes ~/Library, it definitely
affects access to ~/Documents. I'd expect to see a security pop-up from the
system though.
Ronald Oussoren added the comment:
I will create a PR later today, I've already committed the work in a branch of
my clone of cpython.
--
___
Python tracker
<https://bugs.python.org/is
Change by Ronald Oussoren :
--
pull_requests: +23160
pull_request: https://github.com/python/cpython/pull/24341
___
Python tracker
<https://bugs.python.org/issue42
Ronald Oussoren added the comment:
see PR 24341.
--
___
Python tracker
<https://bugs.python.org/issue42504>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ronald Oussoren added the comment:
I can reproduce the issue on macOS 11.1.
As you write:
- running /dev/fd/X as a script fails silently if it refers to an smallish file
- reading /dev/fd/X referring to the same smallish files works fine (the
``open('/dev/fd/9').read()`` scenar
Ronald Oussoren added the comment:
I've checked all three and all of them are present in errnomodule.c, and all of
them are defined in the errno module (macOS 11, Python 3.9.1 "universal2"
build).
On first glance all errno values in the macOS 11 SDK are present in
Change by Ronald Oussoren :
--
resolution: -> not a bug
stage: -> resolved
status: open -> pending
___
Python tracker
<https://bugs.python.or
Ronald Oussoren added the comment:
I was too quick, EQFULL appears to be missing:
#define EQFULL 106 /* Interface output queue is full */
If the script I'm using to check for this is correct this is the only missing
errno with the macOS 11 SDK.
--
resol
Change by Ronald Oussoren :
--
keywords: +patch
pull_requests: +23234
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/24419
___
Python tracker
<https://bugs.python.org/issu
New submission from Ronald Oussoren :
The following O_* flags are present in the macOS 11 SDK, but aren't provided by
posixmodule.c:
O_FSYNC (alias for O_SYNC)
O_EVTONLY
O_SYMLINK
O_NOFOLLOW_ANY
--
components: Extension Modules, macOS
keywords: easy (C)
messages: 386159
Ronald Oussoren added the comment:
Likewise for O_POPUP and O_ALERT, although I don't understand what these are
supposed to do.
--
___
Python tracker
<https://bugs.python.org/is
Ronald Oussoren added the comment:
I got feedback on FB889: Apple says they have fixed the issue (they don't
mention in what version, but I expect 11.2). I haven't checked this yet.
--
___
Python tracker
<https://bugs.python.o
New submission from Ronald Oussoren :
The following syslog facility constants on macOS are missing from the syslog
module:
* LOG_FTP
* LOG_NETINFO
* LOG_REMOTEAUTH
* LOG_INSTALL
* LOG_RAS
* LOG_LAUNCHD
I'm working on a PR
--
components: Extension Modules, macOS
messages: 386456
Change by Ronald Oussoren :
--
keywords: +patch
pull_requests: +23242
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/24432
___
Python tracker
<https://bugs.python.org/issu
Ronald Oussoren added the comment:
The same code is present in trunk.
I'm in favour of disabling usage of X11 browsers of macOS, that's almost
certainly not what users want.
I no longer have XQuartz installed on my machine, but when I did I only used it
for running X11 GUIs
Ronald Oussoren added the comment:
As the issue is gone with the 3.10 universal2 installer it should also be gone
with the 3.9.1 universal installer. I'd expect that the difference is in the
use of a newer version of Tcl/Tk.
We haven't used the newer versions of Tcl/Tk with the r
Ronald Oussoren added the comment:
@terrygreeniaus: Are you running macOS 11 on your MacBook Pro?
If so, could you verify the hardware address of the iBridge interface?
I've checked to libc sources on opensource.apple.com and those don't seem to
contain code to treat the iBridge
Change by Ronald Oussoren :
--
keywords: +patch
pull_requests: +23272
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24480
___
Python tracker
<https://bugs.python.org/issu
Ronald Oussoren added the comment:
I've created a PR for this.
Open question: Is this a bug fix (with back ports to 3.9 and 3.8) or a feature
(no back ports)?
--
___
Python tracker
<https://bugs.python.org/is
Change by Ronald Oussoren :
--
components: +macOS
nosy: +ned.deily, ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue43122>
___
___
Python-bug
Change by Ronald Oussoren :
--
components: +macOS
nosy: +ronaldoussoren
___
Python tracker
<https://bugs.python.org/issue32824>
___
___
Python-bugs-list mailin
Ronald Oussoren added the comment:
This is a duplicate of #41754.
--
nosy: +ronaldoussoren
resolution: -> duplicate
stage: patch review -> resolved
superseder: -> Webbrowser Module Cannot Find xdg-settings on OSX
___
Python tracke
Change by Ronald Oussoren :
--
resolution: -> third party
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Ronald Oussoren added the comment:
There is no ETA. I'm spending more time away from the computer and on other
projects when I'm not at work. I also have no personal need for 3.8 support.
If anyone else is up to the job: the back port to 3.9 should be a good starting
point, b
Ronald Oussoren added the comment:
Can this be closed as out of date?
1. universal2 installers are build using Xcode 12
2. the regular installers are build on macOS 10.9 and the system compilers on
that system should support C++ 11 and 14
Ronald Oussoren added the comment:
To channel Victor: Another thing to look into is to introduce accessors for
struct fields in category 1 and 2 so that the struct can be made private in the
future.
The difference between category 1 and 2 is sadly not very clear cut. Anything
defined in
Change by Ronald Oussoren :
--
nosy: +gregorlingl, willingc
___
Python tracker
<https://bugs.python.org/issue43205>
___
___
Python-bugs-list mailing list
Unsub
Change by Ronald Oussoren :
--
components: +macOS
___
Python tracker
<https://bugs.python.org/issue30799>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ronald Oussoren added the comment:
Please add more information about what you're doing. Your report does not
contain enough information to try to reproduce the problem.
This is supposed to work just fine, and does work for me.
--
nosy: +ronaldous
Ronald Oussoren added the comment:
I'm not sure what you are asking here.
Looking at the screenshot I'd say that the zipfile you are trying to extract
contains files with a newline in their name. That's a perfectly valid (although
annoying) name on unix-y platforms.
The
701 - 800 of 2445 matches
Mail list logo