[issue45582] Rewrite getpath.c in Python
Steve Dower added the comment: New changeset 3f398a77d37b5dfd51dabbc362d482a482fa885a by neonene in branch 'main': bpo-45582: Fix test_embed failure during a PGO build on Windows (GH-30014) https://github.com/python/cpython/commit/3f398a77d37b5dfd51dabbc362d482a482fa885a -- ___ Python tracker <https://bugs.python.org/issue45582> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: I'm going to need a decent amount of time to learn all of these components, because I never use this OS, Tox, nor virtualenv :) I'll try and get to it, but don't hold your breath. Luckily, Modules/getpath.py is much easier to follow and modify than the old systems. If there's a pyvenv.cfg involved, base_executable should be calculated based on the "home" key in it. Previously, I don't think we calculated it at all on Linux - it was just sys.executable before site.py changes anything. On Windows, it was always intended to be "the executable that new venvs should be created with" so that venvs created from venvs would be based off the same install, rather than trying to chain. I have no idea what the correct path for that is in this context, so could do with some help. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43749] venv module does not copy the correct python exe
Steve Dower added the comment: We'd also need to update the launcher to launch the executable with its name, which it currently doesn't do. I was looking at this recently for some other reason. -- ___ Python tracker <https://bugs.python.org/issue43749> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46048] embeddable distro cannot import modules
New submission from Steve Dower : The embeddable distro cannot import native modules. This is because the '.' entry in the ._pth file is incorrect parsed by the new getpath module (issue45582). -- assignee: steve.dower components: Interpreter Core messages: 408300 nosy: lukasz.langa, steve.dower priority: normal severity: normal stage: needs patch status: open title: embeddable distro cannot import modules type: behavior versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46048> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46048] embeddable distro cannot import modules
Change by Steve Dower : -- keywords: +patch pull_requests: +28273 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30048 ___ Python tracker <https://bugs.python.org/issue46048> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46048] embeddable distro cannot import modules
Steve Dower added the comment: New changeset 971ece8e1738b1107dda692cc44c6d8ddce384cd by Steve Dower in branch 'main': bpo-46048: Fix parsing of single character lines in getpath readlines() (GH-30048) https://github.com/python/cpython/commit/971ece8e1738b1107dda692cc44c6d8ddce384cd -- ___ Python tracker <https://bugs.python.org/issue46048> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46048] embeddable distro cannot import modules
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46048> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46049] ._pth files untested on Linux
New submission from Steve Dower : Currently ._pth files are "enabled" for all platforms, but are only tested on Windows. Extend the tests in test_site to work on all platforms. -- assignee: steve.dower components: Interpreter Core messages: 408304 nosy: steve.dower priority: normal severity: normal stage: patch review status: open title: ._pth files untested on Linux type: enhancement versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46049> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46049] ._pth files untested on Linux
Change by Steve Dower : -- keywords: +patch pull_requests: +28276 pull_request: https://github.com/python/cpython/pull/30051 ___ Python tracker <https://bugs.python.org/issue46049> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46049] ._pth files untested on Linux
Steve Dower added the comment: New changeset bfc59ed0a00106f5ba4a32a0c5b3dbe71d12665d by Steve Dower in branch 'main': bpo-46049: Fixes ._pth support on non-Windows (GH-30051) https://github.com/python/cpython/commit/bfc59ed0a00106f5ba4a32a0c5b3dbe71d12665d -- ___ Python tracker <https://bugs.python.org/issue46049> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46049] ._pth files untested on Linux
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46049> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: What's the contents of the pyvenv.cfg in these cases? It looks like the first case is definitely wrong, because the base executable should not be in "venv_a2" (that's sys.executable), but I don't know where it should be on your system. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: > $ cat venv_a3/pyvenv.cfg > home = /home/ss/.pyenv/versions/3.11.0a3/bin > $ venv_a3/bin/python -c "import sys,os.path; print(e := > sys._base_executable); print(os.path.exists(e))" > /home/ss/.pyenv/versions/3.11.0a3/bin/python > True This is the intended behaviour, and yes it's changed from previous versions (but not on Windows, where it was always correct). The previous value was incorrect, hence it was marked as an internal field. If your venv doesn't have a "python" binary in the directory set as "home" in pyvenv.cfg (which by definition, according to Lib/venv/__init__.py, is dirname(sys.executable) ), then there's some other issue with venv on your platform. -- nosy: +vinay.sajip ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: I'm downgrading this from release blocker. If Vinay thinks there's a venv-related release blocker here he's welcome to raise the priority again, but I only see an intentional change to an internal value. Tools relying on internal fields will have to adapt for 3.11. -- priority: release blocker -> normal ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46056] Cannot use virtual environment on Windows 10 in corporate security settings
Steve Dower added the comment: If you execute "python -m venv --without-pip ..." to create, then as a workaround you can set the __PYVENV_LAUNCHER__ environment variable to the full path to the venv's python.exe and run the normal python3.10.exe. As Eryk mentioned, you'll need to run everything through "-m" instead of the script wrappers that pip would install. This includes "-m ensurepip", which should be able to install pip into the venv normally. Note that this is an undocumented/unsupported environment variable, and so it may change in later releases. But it should work fine throughout 3.10's lifetime (and it hasn't changed _yet_ in 3.11). -- ___ Python tracker <https://bugs.python.org/issue46056> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46056] Cannot use virtual environment on Windows 10 in corporate security settings
Steve Dower added the comment: Also, if you see people discussing PEP 582, you might want to throw in a vote of support. It is intended to provide the benefits of a venv without needing to do tricks like we do for the current design, but it keeps being rejected for "not being sufficiently useful". Seems like in your case it would be very useful. That might help sway some of the opponents. -- ___ Python tracker <https://bugs.python.org/issue46056> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14484] missing return in win32_kill?
Steve Dower added the comment: > Windows should have its own specific function. Either that or mimic it properly. Having a single function that requires different parameters based on OS is a very user-hostile design. If someone wants to shepherd it through the process, I'd support either making the typical POSIX values do sensible equivalents on Windows (as best possible), or adding a new function entirely and deprecating all use of the current one on Windows. Those are the only ways to lead people into writing code that works well on all platforms. (My *real* preference is that people stop trying to kill applications ;) and try to set up a safe communication channel instead, but I know it's often unavoidable. Having common parameters that do the Right Things on all platforms is next best.) -- ___ Python tracker <https://bugs.python.org/issue14484> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: Is sys._base_executable correct without a venv? It should be the same as sys.executable in that case. venv calculates 'home' here: Lib/venv/__init__.py#L117 executable = sys._base_executable dirname, exename = os.path.split(os.path.abspath(executable)) context.executable = executable # not relevant to this bug context.python_dir = dirname# written as "home = ..." If the path doesn't exist later on, it's because it didn't exist in the first place. *That* could be the real bug. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: > But the value as it's calculated now seems to give a file that doesn't exist > - how can that be correct? Because we never actually use the executable referenced by the 'home' path in a pyvenv.cfg. It's only used as a starting point to locate a couple of entries in sys.path. So if the executable isn't there, it's no big deal. It shouldn't even matter in the nested-creation case, because we still don't execute it then. It's just how we end up with the same value for 'home' in any venvs created within a venv. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: > Because we never actually use the executable referenced by the 'home' path in > a pyvenv.cfg. This is actually not true on Windows or (I believe) some situations on macOS, where we need to use a redirecting launcher to actually launch the binary specified in this value. But on POSIX, because all the references are hardcoded in the binary, we can just copy the original around and it never loses track of its real home and never has to launch its original copy. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: > $ v311/bin/python -m venv 311-nested > Error: [Errno 2] No such file or directory: > '/private/tmp/bpo-46028/311-nested/bin/python' I assume /private/tmp/bpo-46028/311-nested/bin/python3.11 exists though? Probably that's the issue here - I don't know how else to get the real executable *name* other than copying from argv[0], and it isn't supposed to be necessary. You also have v311/bin/python3.11, right? If you use that one, does it work? I'm trying to narrow down where the base executable is actually being launched and why. -- title: 3.11.0a3: sys._base_executable is wrong, breaks venv - it wasn't under 3.11.0a2 -> 3.11.0a3: under tox, sys._base_executable is wrong ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: Or possibly that error is coming from the attempt to copy it? And since both executable and base_executable don't have the 3/3.x suffix, the copy is failing because the "real" binary does have the suffix. This could be corrected in getpath.py with a platform-specific quirk that searches for suffixed binaries for base_executable, but for performance reasons I think we'd prefer to have that check in venv so that it doesn't impact every single launch of CPython. The actual binary could also be added to pyvenv.cfg as another value - parsing that out in getpath.py is now considerably easier for someone to add than it used to be. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: Does the first venv's 'python' link to python3[.11]? If so, maybe _base_executable should be based on real_executable's filename rather than executable (that is, *after* resolving symlinks rather than before). I don't *think* that will cause any issues, and it shouldn't be any more expensive to compute. Only has to change for when a pyvenv.cfg is detected I think. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46088] Build hangs under Visual Studio in deepfreeze stage
Change by Steve Dower : -- pull_requests: +28361 pull_request: https://github.com/python/cpython/pull/30143 ___ Python tracker <https://bugs.python.org/issue46088> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46088] Build hangs under Visual Studio in deepfreeze stage
Steve Dower added the comment: I posted a PR that shells out to the find_python script and captures its output to use during VS builds. Theoretically, this could save us from running it in build.bat, but I like having the detection and messages up front rather than buried deep in the build logs. -- ___ Python tracker <https://bugs.python.org/issue46088> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46088] Build hangs under Visual Studio in deepfreeze stage
Steve Dower added the comment: On Windows we automatically download a runtime if you don't have one, so this isn't such a big deal. You *do* need an internet connection to do this, of course, but that's the case for most of our external dependencies already. Plus I don't think we're even building the bootstrap interpreter on Windows yet? -- ___ Python tracker <https://bugs.python.org/issue46088> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Change by Steve Dower : -- keywords: +patch pull_requests: +28362 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30144 ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: This PR *might* be a fix, but I think it's only partial. It isn't going to work if you've made a venv and copied "python3"->"python", for example. It still might be best solved by writing base_executable into pyvenv.cfg, and then simply reading it out. -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40915] multiple problems with mmap.resize() in Windows
Steve Dower added the comment: New changeset 6214caafbe66e34e84c1809abf0b7aab6791956b by neonene in branch 'main': bpo-40915: Avoid compiler warnings by fixing mmapmodule conversion from LARGE_INTEGER to Py_ssize_t (GH-30175) https://github.com/python/cpython/commit/6214caafbe66e34e84c1809abf0b7aab6791956b -- ___ Python tracker <https://bugs.python.org/issue40915> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46088] Build hangs under Visual Studio in deepfreeze stage
Steve Dower added the comment: New changeset 6fc91daf730c60b08b4b32cdce28ff26505a0622 by Steve Dower in branch 'main': bpo-46088: Automatically detect or install bootstrap Python runtime when building from Visual Studio (GH-30143) https://github.com/python/cpython/commit/6fc91daf730c60b08b4b32cdce28ff26505a0622 -- ___ Python tracker <https://bugs.python.org/issue46088> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46088] Build hangs under Visual Studio in deepfreeze stage
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46088> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46106] OpenSSL 1.1.1m is now available
Steve Dower added the comment: Are we going to have to rush security releases for this one? Or can it wait (for me) until Monday? -- ___ Python tracker <https://bugs.python.org/issue46106> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46123] _freeze_module on Windows can be built faster with no optimization
Steve Dower added the comment: New changeset 0b582a4a1b24472a35ed7fc973728ac9d595f123 by neonene in branch 'main': bpo-46123: Disable optimizations for _freeze_module.exe on MSVC for faster building (GH-30181) https://github.com/python/cpython/commit/0b582a4a1b24472a35ed7fc973728ac9d595f123 -- ___ Python tracker <https://bugs.python.org/issue46123> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46123] _freeze_module on Windows can be built faster with no optimization
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46123> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46106] OpenSSL 1.1.1m is now available
Steve Dower added the comment: I've put up the builds for 1.1.1m (and double checked everything after last time - it's definitely "m" :) ), so anyone can do the PR to change Python itself. Otherwise I'll probably get time this week. -- ___ Python tracker <https://bugs.python.org/issue46106> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46171] venv module produces spurious warning that location has moved
Steve Dower added the comment: There are plenty of other ways to get a venv through a potentially unexpected path (turns out I've been doing one for years), which is why I went with the general warning rather than limiting it to specific behaviours that are subject to change outside of our control. I'm not opposed to strengthening this check to ignore DOS encoded names, but I think it should remain for anything where the realised executable path isn't the same as what you'd assume from the requested path. Without being very aware of how your directories are all configured, it could be near impossible to diagnose, so the warning in the command-line tool is appropriate. -- nosy: +vinay.sajip ___ Python tracker <https://bugs.python.org/issue46171> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46177] can't install launcher for all users
Steve Dower added the comment: This normally happens because you've already installed the launcher "just for me". You can't change that setting later. Open Add/Remove Programs and uninstall the Python Launcher first. Then you should be able to reinstall it for all users. -- ___ Python tracker <https://bugs.python.org/issue46177> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+
Steve Dower added the comment: Yep, it's a bug and should be fixed. I'm still not back coding yet, but I'll get to it once I am if nobody else gets there first. This is going to affect getpath.py in the native implementation, so it ought to be fixed there (and we need tests for this case, since it's apparently a gap). -- priority: normal -> release blocker ___ Python tracker <https://bugs.python.org/issue46208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46171] venv module produces spurious warning that location has moved
Steve Dower added the comment: My VHDX mounted in a directory is affected by this, and actually broke a couple of tools until I also mounted it as a drive. (Using a VHDX helps bypass a lot of filesystem related perf impacts on Windows, so it's worth the occasional broken tool.) I suspect (but haven't tested) that some file sharing handlers or attached devices could also hit it - thinking here of IoT devices that provide a filesystem-like interface. Either way, I don't think the warning is spurious, and while it's not particularly helpful for people who pass in 8.3 names that are then expanded (it shouldn't ever happen the other way), that's easily fixed on the user's side. (And tempfile, which clearly needs fixing.) I'm also *strongly against* warnings/errors that only occur based on a decision you made ages ago (or that someone else made for you), such as how you installed Python. Right now we have a warning that can be explained in exactly the same way on every platform and every circumstance, but Eryk's proposal/preference would suddenly make the case for the warning way too complex. Tutorials and teachers don't get to ignore it just because it only happens to some of their readers/students, and so we only make things worse for them by making it harder to understand. Better to have a simple, consistent message in this case. -- ___ Python tracker <https://bugs.python.org/issue46171> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46226] User specific paths added to System PATH environment variable
Steve Dower added the comment: If you have them, can you share your install logs (look in %TEMP% for files starting with "Python"). If not, please share your install options. By default, this works fine. You have to make some specific modifications to the install options to do what you've done, such as choosing to install for all users and then overriding the install path to a per-user location. If you're installing just for yourself, the installer shouldn't even have the permissions required to modify system-wide environment variables. It's also possible that your machine has a special configuration to do this, in which case you'll need to speak with your administrator to find out why. We can't help with that - we just use standard MSIs and let the OS choose where things go. -- ___ Python tracker <https://bugs.python.org/issue46226> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46217] 3.11 build failure on Win10: new _freeze_module changes?
Steve Dower added the comment: Good catch. We still support 8.1 for this release, so that flag will have to be taken out (and hopefully people won't be impacted by long path names here). -- ___ Python tracker <https://bugs.python.org/issue46217> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+
Steve Dower added the comment: I'm happy with PR 30362 now - any other comments before we merge? -- ___ Python tracker <https://bugs.python.org/issue46208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+
Steve Dower added the comment: New changeset 9c5fa9c97c5c5336e60e4ae7a2e6e3f67acedfc7 by neonene in branch 'main': bpo-46208: Fix normalization of relative paths in _Py_normpath()/os.path.normpath (GH-30362) https://github.com/python/cpython/commit/9c5fa9c97c5c5336e60e4ae7a2e6e3f67acedfc7 -- ___ Python tracker <https://bugs.python.org/issue46208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46208] os.path.normpath change between 3.11.0a2 and 3.11.0a3+
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46287] UNC path normalisation issues on Windows
New submission from Steve Dower :
Taken from https://github.com/python/cpython/pull/30362#issuecomment-1006840632
For Windows, should there be tests for invalid UNC paths such as "//", "//..",
"//../..", "//../../..", "//server", "//server/..", and "//server/../.."? This
will help to ensure that future changes never allow an invalid path to be
normalized as a valid path.
Also, it's not a major problem that should prevent merging, but the way
repeated slashes are handled prior to the second component of a UNC path is
less than ideal:
>>> os.path.normpath('//spam///eggs')
'spameggs'
>>> os.path.normpath('//spam///eggs/..')
'spam'
This case isn't a valid UNC share, since it's just "//spam", without a share
component. However, the repeated slashes start the filepath part and should be
reduced to a single backslash. That's what the GetFullPathNameW() call does in
abspath():
>>> os.path.abspath('//spam///eggs')
'spam\\eggs'
>>> os.path.abspath('//spam///eggs/..')
'spam\\'
--
components: Windows
messages: 409903
nosy: eryksun, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: test needed
status: open
title: UNC path normalisation issues on Windows
type: behavior
versions: Python 3.11
___
Python tracker
<https://bugs.python.org/issue46287>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46287] UNC path normalisation issues on Windows
Steve Dower added the comment:
My replies to Eryk's comment copied above:
Yes, always more tests :)
The behaviour of normpath has always been weird and/or incorrect around invalid
UNC paths.
For example, on 3.10, normpath("//spam///eggs/..") --> "spam". Originally,
the path was a file path (albeit with an invalid empty share name), and the
final path is just a machine name.
Currently on 3.11, normpath("//spam///eggs/..") --> "spam". This
doesn't match GetFullPathNameW, but at least it leaves the end of the path as a
file (with an empty share name).
I don't think it's necessarily obvious which is correct, though matching
GetFullPathNameW is certainly the easiest rule for us to use. Matching previous
Python versions is also reasonable, though given the input is invalid for its
domain we don't really have any obligation to preserve the result.
--
___
Python tracker
<https://bugs.python.org/issue46287>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45925] Upgrade macOS and Windows installers to use SQLite 3.37.2
Steve Dower added the comment: Are we enabling the build option they mention on the release page? Or is this only going to affect users who use the pragma? We should obviously do the upgrade, but that will determine how aggressively we ought to be messaging the issue. -- ___ Python tracker <https://bugs.python.org/issue45925> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45925] Upgrade macOS and Windows installers to use SQLite 3.37.2
Steve Dower added the comment: We should definitely upgrade, but we probably don't have to trigger a fresh release of all branches for it, or make a big fuss about it being a special fix. That's all I was trying to establish. -- ___ Python tracker <https://bugs.python.org/issue45925> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46217] 3.11 build failure on Win10: new _freeze_module changes?
Steve Dower added the comment: Only a newer WinSDK, which is not in any way a significant change to the resulting build and so isn't part of the "spec" as it were. But we'll remove the use of this flag once someone has the time to make a PR. (Remember to add the RM when you declare something a release blocker or the release may not be blocked.) -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue46217> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45925] Upgrade macOS and Windows installers to use SQLite 3.37.2
Steve Dower added the comment: > Can you update the sources repo in the mean time? Done -- ___ Python tracker <https://bugs.python.org/issue45925> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46297] Python interpreter crashes on bootup with multiple PythonPaths set in registry
Steve Dower added the comment: New changeset c9dc1f491e8edb0bc433cde73190a3015d226891 by Daniel in branch 'main': bpo-46297: Fix interpreter crash on startup with multiple PythonPaths set in registry (GH-30466) https://github.com/python/cpython/commit/c9dc1f491e8edb0bc433cde73190a3015d226891 -- ___ Python tracker <https://bugs.python.org/issue46297> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46297] Python interpreter crashes on bootup with multiple PythonPaths set in registry
Steve Dower added the comment: Thanks for the report and the PR! -- assignee: -> steve.dower ___ Python tracker <https://bugs.python.org/issue46297> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46297] Python interpreter crashes on bootup with multiple PythonPaths set in registry
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46297> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46217] 3.11 build failure on Win10: new _freeze_module changes?
Change by Steve Dower : -- keywords: +patch pull_requests: +28676 stage: backport needed -> patch review pull_request: https://github.com/python/cpython/pull/30473 ___ Python tracker <https://bugs.python.org/issue46217> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46217] 3.11 build failure on Win10: new _freeze_module changes?
Steve Dower added the comment: New changeset d81182b8ec3b1593daf241d44757a9fa68fd14cc by Steve Dower in branch 'main': bpo-46217: Revert use of Windows constant that is newer than what we support (GH-30473) https://github.com/python/cpython/commit/d81182b8ec3b1593daf241d44757a9fa68fd14cc -- ___ Python tracker <https://bugs.python.org/issue46217> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46217] 3.11 build failure on Win10: new _freeze_module changes?
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46217> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46226] User specific paths added to System PATH environment variable
Steve Dower added the comment: Without logs or the ability to reproduce it, there's not much we can do. I ran the install and it put the variables in the right place, so it's not happening all the time. The install logs are usually detailed enough to see why decisions like this are made, but it'll almost certainly be because of something specific to your machine. If running the install again produces the same result, those logs will be helpful as well. I don't see us being able to make any product changes for this though. -- ___ Python tracker <https://bugs.python.org/issue46226> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Steve Dower added the comment: Hi Tommy! Glad to have you join the discussion (I'm a huge fan of OBS Studio, and if the license wasn't incompatible with my employer, I'd be actively contributing :) ) Our challenge with the installer is the portability of Wix Toolset. I'm pretty sure our current version doesn't support ARM64, and they haven't released a newer version that does yet. It's possible that emulation will handle the main part of our installer, but AFAIK nobody has tested it to see whether it confuses the underlying installer service. (I can probably do that at some point, as I have access to some test machines now.) At the same time, any reason why OBS doesn't just include a copy of Python with it? It should be quite easy to include the embeddable runtime on Windows, which would then mean that you're able to ship the exact version necessary and have the paths preconfigured. (It *might* complicate installing 3rd party packages a bit, but you can always allow search paths to be set/PYTHONPATH to be respected, or the executable path overridden.) Possibly this is something you guys have already looked into, so if you know there's an issue I'd love to hear about it. Making it easy/easier to bundle Python with apps like OBS is one of my major focuses. -- ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46346] New compilation warnings on Windows
Steve Dower added the comment: Possibly related to Victor's change in issue46303? -- nosy: +vstinner ___ Python tracker <https://bugs.python.org/issue46346> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Steve Dower added the comment: PEP 514 is the way to find it on Windows (you should be able to look directly for your supported version, rather than enumerating to search). As far as I know, the best way to find it on macOS and Linux is to search PATH for "python3.X". Appreciate the size concerns. The Python runtime comes down to about 10MB with some basic tricks (already done on Windows in the embeddable distro), such as excluding the docs, test suite and zipping the standard library. It's possible with different tricks to do the same on other platforms, so you may even find the best balance for yourselves and your users is to repackage those and do a download-on-demand, rather than looking for a system installed Python. > as an installer, it should be the most forgotten part of python that usually > runs for once or twice. Oh I wish this were the case! Installers should be forgotten, but they need to be 100% reliable or people *really* notice :) But updating the installer build to target ARM64 while generating an x86 executable should be possible, it just hasn't been done yet. -- ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46303] _Py_stat and _Py_wstat using incorrect type for status argument
Steve Dower added the comment: > Microsoft provides stat and struct stat, but they prepend the names with an > underscore. They are also influenced by various compiler options to choose between 32-bit and 64-bit fields. This makes it impossible to use the standard names as part of an ABI, because we can't/don't enforce that the preprocessor definitions match. We should isolate all structures from libc/equivalent in our public API so that we can ensure compatibility. (FILE* was historically also an issue, but that was bad enough that Windows fixed it on their side. The rest of the C runtime library still bleeds everywhere, so we definitely don't want it or its semantics in our public API if avoidable.) -- title: Building Python with clang on Windows fails on _Py_stat(): struct stat is not defined -> _Py_stat and _Py_wstat using incorrect type for status argument ___ Python tracker <https://bugs.python.org/issue46303> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46362] os.path.abspath() needs more normalization on Windows
Steve Dower added the comment: One thing to be aware of is that Windows 11 has changed the rules around these files, so here's my results with 3.10: >>> for path in paths: ... print(os.path.abspath(path)) ... C:\CON C:\PRN C:\AUX \\.\NUL C:\COM1 C:\COM2 C:\COM3 C:\COM9 C:\LPT1 C:\LPT2 C:\LPT3 C:\LPT9 C:\foo But this shouldn't be an issue with the proposed (about to be merged) change. -- ___ Python tracker <https://bugs.python.org/issue46362> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46362] os.path.abspath() needs more normalization on Windows
Steve Dower added the comment: New changeset d4e64cd4b0ea431d4e371f9b0a25f6b75a069dc1 by neonene in branch 'main': bpo-46362: Ensure ntpath.abspath() uses the Windows API correctly (GH-30571) https://github.com/python/cpython/commit/d4e64cd4b0ea431d4e371f9b0a25f6b75a069dc1 -- ___ Python tracker <https://bugs.python.org/issue46362> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46362] os.path.abspath() needs more normalization on Windows
Steve Dower added the comment: Thanks for the patch! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46362> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46362] os.path.abspath() needs more normalization on Windows
Steve Dower added the comment: New changeset 71c0b859ae16ee748cbb050a1f4de93c04e04f83 by neonene in branch 'main': bpo-46362: Ensure abspath() tests pass through environment variables to subprocess (GH-30595) https://github.com/python/cpython/commit/71c0b859ae16ee748cbb050a1f4de93c04e04f83 -- ___ Python tracker <https://bugs.python.org/issue46362> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44934] Windows installer: Append Python to PATH instead of prepending it
Steve Dower added the comment: New changeset c47c9e6589eb7a272cfe4d352eb87389eb20ec2f by bneuburg in branch 'main': bpo-44934: Add optional feature AppendPath to Windows MSI installer (GH-27889) https://github.com/python/cpython/commit/c47c9e6589eb7a272cfe4d352eb87389eb20ec2f -- ___ Python tracker <https://bugs.python.org/issue44934> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44934] Windows installer: Append Python to PATH instead of prepending it
Steve Dower added the comment: Thanks for the PR! This is a good contribution, that wasn't trivial to do. It should be in Python 3.11 alpha 5, so please test it out and make sure it's behaving as you expect. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue44934> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: New changeset 7407fe4c25ba0308d49e3e88e4a107ef32251cdc by Steve Dower in branch 'main': bpo-46028: Calculate base_executable by resolving symlinks in a venv (GH-30144) https://github.com/python/cpython/commit/7407fe4c25ba0308d49e3e88e4a107ef32251cdc -- ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46028] 3.11.0a3: under tox, sys._base_executable is wrong
Steve Dower added the comment: Merged my PR, but I want to leave this open in commit review for now - I'm not sure it deals with all the issues here, and probably not everything from the Discourse thread linked by Victor (though it might come close). -- stage: patch review -> commit review ___ Python tracker <https://bugs.python.org/issue46028> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46434] pdb help fails with AttributeError when using Windows embeddable package
Steve Dower added the comment: The PR looks good. I assume you've started the CLA process, so once that clears we'll be fine to merge. -- versions: -Python 3.7, Python 3.8 ___ Python tracker <https://bugs.python.org/issue46434> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46438] Static linking _decimal module breaks test_freeze
New submission from Steve Dower : After applying this patch on Linux, test_freeze_simple_script (test.test_tools.test_freeze.TestFreeze) fails. diff --git a/Modules/Setup b/Modules/Setup index d3647ecb99..c41bcac453 100644 --- a/Modules/Setup +++ b/Modules/Setup @@ -135,7 +135,7 @@ PYTHONPATH=$(COREPYTHONPATH) #_contextvars _contextvarsmodule.c #_csv _csv.c #_datetime _datetimemodule.c -#_decimal _decimal/_decimal.c +_decimal _decimal/_decimal.c #_heapq _heapqmodule.c #_json _json.c #_lsprof _lsprof.c rotatingtree.c The stderr from the test is below. The rest of the output looks normal to me, but most of the build output is missing. --- STDERR --- gcc: error: Modules/_decimal/libmpdec/libmpdec.a: No such file or directory make: *** [Makefile:976: app] Error 1 -- components: Build messages: 410978 nosy: steve.dower priority: normal severity: normal status: open title: Static linking _decimal module breaks test_freeze versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46438> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44673] Embedded Python - local directories in pythonXX._pth
Steve Dower added the comment: I'm afraid not. The ._pth file is intended for embedding applications that have a static set of search paths. You may want to try adding a startup file (search for PYTHONSTARTUP) that modifies sys.path directly. Or alternatively if you rename the ._pth file to a regular .pth file, it should disable the isolation protection and use the more flexible algorithm, which *I believe* will resolve relative paths against the current directory rather than where the file lives. -- nosy: +steve.dower ___ Python tracker <https://bugs.python.org/issue44673> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31582] Add _pth breadcrumb to sys.path documentation
Steve Dower added the comment: Need to make this happen, and it probably needs to be me (though I'm happy to review a contribution). We now handle ._pth files on all platforms as part of the Modules/getpath.py changes (which I hinted to in my previous comment from 5 years ago ;) ). -- versions: +Python 3.11 -Python 3.6, Python 3.7 ___ Python tracker <https://bugs.python.org/issue31582> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46434] pdb help fails with AttributeError when using Windows embeddable package
Steve Dower added the comment: See https://github.com/python/cpython/blob/b04dfbbe4bd7071d46c8688c2263726ea31d33cd/PC/layout/main.py#L256-L289 Basically, the .pyc files in the embeddable distro have been compiled with optimize=2, which is the equivalent of -OO. So yes, docstrings (and asserts) are expected to have been removed. It shouldn't be removing docstrings from other modules that you provide yourself. -- ___ Python tracker <https://bugs.python.org/issue46434> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46434] pdb help fails with AttributeError when using Windows embeddable package
Steve Dower added the comment: > the existing check in `do_help` didn't catch this case because > https://docs.python.org/3/library/sys.html#sys.flags only reflects command > line flags, rather than whether or not it was actually optimised. Precisely. Your check is much more appropriate for what the actual issue is going to be, though keeping the existing check there means we can provide a more specific error message when we *know* that the user deliberately chose that behaviour. -- ___ Python tracker <https://bugs.python.org/issue46434> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46427] Correct MSBuild's configuration for _freeze_module.exe
Steve Dower added the comment: This configuration is intentional. When cross-compiling, tools that are executed as part of the build need to be built for the tool platform, not the target platform. -- nosy: +steve.dower resolution: -> not a bug stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46427> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46427] Correct MSBuild's configuration for _freeze_module.exe
Steve Dower added the comment: Windows ARM64 devices all support x86 and x64 emulation, so while it's less than ideal performance-wise to use a non-native build for this step, it's hardly fatal. That step doesn't rely on the underlying architecture, just the current Python bytecode format (which is platform independent). Leaving the Platform blank is not acceptable. It needs to be set to the preferred tool architecture, which as it happens, is $(PreferredToolArchitecture). As I said, if you've hit a *real* issue around this, please describe it. There is no theoretical issue here, and as far as I'm aware, no practical issues either. -- ___ Python tracker <https://bugs.python.org/issue46427> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46452] Possible false detection of Windows LZMA library as a malware by Avast
Steve Dower added the comment: I don't think we've changed anything here in years, so I'd be very surprised if something new was in there. More likely somebody PyInstaller'd some malware and the scanners picked up a generic part of it as the signature. Reporting it as a false positive should let them compare against the original sample and correct it. -- ___ Python tracker <https://bugs.python.org/issue46452> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46459] Installing python to external drive (USB) using python installer failure
Steve Dower added the comment: The installer doesn't support installing twice on the same machine, even to different locations. What you probably want to do is to install it normally, then copy all the files onto the USB. You will need to "python -m pip install --force pip" in the new copy to fix up its scripts, and it may interfere with a system install if you use it on a machine that also has its own installation (though that's mostly been cleaned up since ~3.5), but should otherwise be fine. -- ___ Python tracker <https://bugs.python.org/issue46459> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46434] pdb help fails with AttributeError when using Windows embeddable package
Steve Dower added the comment: New changeset 60705cff70576482fea31dcafbf8a37cbb751ea5 by Tom Sparrow in branch 'main': bpo-46434: Handle missing docstrings in pdb help (GH-30705) https://github.com/python/cpython/commit/60705cff70576482fea31dcafbf8a37cbb751ea5 -- ___ Python tracker <https://bugs.python.org/issue46434> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39952] Using VS2019 to automatically build Python3 and it failed to build
Steve Dower added the comment: I think we can close it. -- stage: -> resolved status: pending -> closed ___ Python tracker <https://bugs.python.org/issue39952> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46434] pdb help fails with AttributeError when using Windows embeddable package
Steve Dower added the comment: Thanks for the contribution! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46434> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46463] escape4chm.py script causing AttributeError in docs build
New submission from Steve Dower : Exception occurred: File "D:\a\1\s\Doc\tools\extensions\escape4chm.py", line 44, in fixup_keywords with app.builder.open_file(outdir, outname + '.hhk', 'r') as f: AttributeError: 'HTMLHelpBuilder' object has no attribute 'open_file' The full traceback has been saved in C:\Users\VSSADM~1\AppData\Local\Temp\sphinx-err-9ikx8s0b.log, if you want to report the issue to the developers. Please also report this if it was a user error, so that a better error message can be provided next time. A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks! -- assignee: steve.dower components: Build, Documentation messages: 411180 nosy: steve.dower priority: normal severity: normal status: open title: escape4chm.py script causing AttributeError in docs build versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46463> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46463] escape4chm.py script causing AttributeError in docs build
Change by Steve Dower : -- keywords: +patch pull_requests: +28953 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30768 ___ Python tracker <https://bugs.python.org/issue46463> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46463] escape4chm.py script causing AttributeError in docs build
Steve Dower added the comment: New changeset 57d1855682dbeb9233ef3a531f9535c6442e9992 by Steve Dower in branch 'main': bpo-46463: Fixes escape4chm.py script used when building the CHM documentation file (GH-30768) https://github.com/python/cpython/commit/57d1855682dbeb9233ef3a531f9535c6442e9992 -- ___ Python tracker <https://bugs.python.org/issue46463> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46463] escape4chm.py script causing AttributeError in docs build
Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue46463> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45382] platform() is not able to detect windows 11
Steve Dower added the comment: Yeah, I pushed the machines up to 2022 the other day while tidying the configs. Wouldn't have expected it to impact that issue though, it's fully within OpenSSL, isn't it? (We also updated that recently...) Also, as an FYI, if you use "wmic /output:" then it always writes in utf-16-le with a BOM. It's *very* unlikely you'll ever get output that doesn't fit into MBCS, but if that does ever occur, we can use a temporary file instead of stdout. -- ___ Python tracker <https://bugs.python.org/issue45382> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Steve Dower added the comment: > Our challenge with the installer is the portability of Wix Toolset. I'm > pretty sure our current version doesn't support ARM64, and they haven't > released a newer version that does yet. Turns out they've released some test versions that support it (partially, but enough), just nothing that they've declared stable. I'll push updated tools for 3.11 so we have a chance to discover any breakage in earlier versions, but should be able to do ARM64 regular installer next alpha (Pablo, FYI - this will require updates to your side of things). -- nosy: +pablogsal ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Steve Dower added the comment: Yeah, will just be the same files again but with "arm64" in place of "win32"/"amd64". I'm also going to stop uploading the old webinstall files with my change here, though that shouldn't matter. The code we added to filter them out should handle them being completely absent, IIRC. -- ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Change by Steve Dower : -- pull_requests: +29066 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/30885 ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45382] platform() is not able to detect windows 11
Steve Dower added the comment: sys.getwindowsversion() is affected to Microsoft's minimal rebuilds of OS components causing core DLLs to have older versions than the release, and also to compatibility modes that may report earlier versions if API behaviour is being emulated. The best way for us to use WMI is to call it directly. There are native APIs to access it and retrieve the data directly. It's just nobody has written it yet. Calling out to Powershell needs to account for cases where Powershell is not present, is disabled/blocked/limited, or is a different version. We can rely on the native APIs (at least, if they fail, there's nothing better we could possibly have done). WMI is essentially the Windows equivalent of the platform module, so there's no reason all the APIs in platform.py shouldn't use it, and every reason that sys/os *shouldn't* use it. -- ___ Python tracker <https://bugs.python.org/issue45382> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45382] platform() is not able to detect windows 11
Steve Dower added the comment: >> AFAIK, the Win32_OperatingSystem caption is always ASCII. > > I think I was wrong here. The "Caption" field is localized, so the wmic.exe > OEM encoded output to a pipe isn't reliable. Correct. And while "Windows" itself is never translated, the caption may include terms that are translated (e.g., IIRC, the extra names for point-of-sales versions). -- ___ Python tracker <https://bugs.python.org/issue45382> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31582] Add _pth breadcrumb to sys.path documentation
Steve Dower added the comment: I think we need somewhere in the documentation to explain how the initial import path is calculated, in terms useful for an end user (rather than what's in getpath.py, which is for developers). Right now, I'm not sure there's a good place for it. There's a Windows-specific page with some detail, but we probably need something more generic. Probably it belongs under Doc/using/cmdline.rst (the environment variables section there is tempting, but I expect those would be updated to point to an easier to follow explanation. We'd also point to it from sys.path. Without adding the new section, there isn't really anywhere sensible to mention it. -- ___ Python tracker <https://bugs.python.org/issue31582> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45925] Upgrade macOS and Windows installers to use SQLite 3.37.2
Steve Dower added the comment: New changeset db77bcd6092f3c174ae855522411ab83854d65a8 by Kumar Aditya in branch 'main': bpo-45925: Update Windows installer to SQLite 3.37.2 (GH-30485) https://github.com/python/cpython/commit/db77bcd6092f3c174ae855522411ab83854d65a8 -- ___ Python tracker <https://bugs.python.org/issue45925> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45925] Upgrade macOS and Windows installers to use SQLite 3.37.2
Change by Steve Dower : -- pull_requests: +29171 pull_request: https://github.com/python/cpython/pull/30991 ___ Python tracker <https://bugs.python.org/issue45925> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Steve Dower added the comment: New changeset 45faf151c693b6f13f78926761caea6df7242024 by Steve Dower in branch 'main': bpo-33125: Enables building traditional installer for Windows ARM64 (GH-30885) https://github.com/python/cpython/commit/45faf151c693b6f13f78926761caea6df7242024 -- ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46566] Support -3.11-arm64 in py.exe launcher
New submission from Steve Dower : We now have a traditional installer that runs on Windows ARM64 devices, but it omits the py.exe launcher. This is because sys.winver is "3.11-arm64" and hence the registry tag (see PEP 514) is not detected by the launcher. Currently, the launcher is not included in the installer and appears as disabled with an explanatory note. We need to add support for it eventually, and possibly block the final/RC/beta releases if we don't have it. (We don't ship the launcher with Nuget or Store packages, so nobody will miss it there, but they probably will here.) 32-bit apps can still run on ARM64, so it isn't essential to make it a native process. It just has to be able to detect the registry keys. It should still support 32-bit and 64-bit installs, because those can also be run on ARM64 devices (though there are numerous things that don't work as well as a native build). Possibly we want to just do the work to directly follow PEP 514 now? Depends on who volunteers to work on this, I guess. -- components: Windows messages: 412008 nosy: paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal stage: needs patch status: open title: Support -3.11-arm64 in py.exe launcher type: enhancement versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46566> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Steve Dower added the comment: The ARM64 installer will be part of the next 3.11 release, minus the py.exe launcher (which needs a chunk of work in issue46566) and Tcl/Tk (which needs upstream support for the platform) and hence IDLE. I'm hesitant to make a final release without these components. At the same time, I'm concerned about other release blocking issues that may arise that are unrelated, so I do want to get releases out even without them so that we have a chance to discover them. -- ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46567] Add Tcl/Tk builds for ARM64
New submission from Steve Dower : Currently our ARM64 installs omit Tcl/Tk (and implicitly tkinter and IDLE) because there appears to be no upstream support for building Tcl/Tk for ARM64. Once the upstream support exists, or we have a good enough patch to apply to our own copy of the sources, we need to add these back. -- components: Tkinter, Windows messages: 412011 nosy: paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal stage: needs patch status: open title: Add Tcl/Tk builds for ARM64 type: enhancement versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46567> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33125] Windows 10 ARM64 platform support
Steve Dower added the comment: Tcl/Tk tracking issue is issue46567 -- ___ Python tracker <https://bugs.python.org/issue33125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
