Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution
Ok, had received response on pyinstaller mailing list, but, also just related to trying clean uninstall/reinstall of modules, but, while checking that out, something else occurred to me, and, it now operates as it should. Anyway, what seemed to be causing issue was actually that, since, while am working under windows 11, quite often you might need to work with case-sensitivity in file names, not by choice, but, since a lot of target platforms, like linux, etc. are case-sensitive, and, at times, when working with external modules, this might cause hassles, etc. In other words, the folder/directory where all my python source code is stored is set to be case-sensitive - there are a couple of ways to implement this under windows 10 and windows 11, via some external utilities, or by running the following command from a terminal/power-shell window, running it as administrator: fsutil.exe file SetCaseSensitiveInfo C:\folder\path enable If you instead use disable argument at the end, it then disables case-sensitivity, and, what did now was, under current project/test code, I created an additional sub-folder, copied code files, etc. over into it, disabled case-sensitivity on it, recreated the virtual environment, and installed all required modules, including pyinstaller using pip, and, when I then run pyinstaller from there, it works fine, and, does what I want it to. In other words, something to do with having case-sensitivity enabled recursively on the folder/directory containing the code and the virtual environment seemed to be causing these errors/issues, specific to altgraph, which doesn't really make sense to me, but, it's now working, so, will archive this to memory, for later reference. Jacob Kruger +2782 413 4791 "Resistance is futile!...Acceptance is versatile..." On 2024/04/02 17:11, Barry wrote: On 1 Apr 2024, at 15:52, Jacob Kruger via Python-list wrote: Found many, many mentions of errors, with some of the same keywords, but, no resolutions that match my exact issue at all. Try asking the pyinstaller developers. I think there is a mailing list. Barry As in, most of them are mentioning older versions of python, and, mainly different platforms - mac and linux, but, various google searches have not mentioned much of using it on windows, and having it just stop working. Now did even try shifting over to python 3.12, but, still no-go. If launch pyinstaller under python 3.10 on this exact same machine, pyinstaller runs - just keep that older version hovering around for a couple of occasional tests, partly since some of my target environments are still running older versions of python, but anyway. Also, not really relevant, but, cx_freeze is perfectly able to generate executables for this same code, but, then not combining all output into a single file - will stick to that for now, but, not always as convenient, and, still wondering what changed here. Jacob Kruger +2782 413 4791 "Resistance is futile!...Acceptance is versatile..." On 2024/03/31 14:51, Barry wrote: On 31 Mar 2024, at 13:24, Jacob Kruger via Python-list wrote: pkg_resources.DistributionNotFound: The 'altgraph' distribution was not found and is required by the application I think I have seen this error being discussed before… A web search for pyinstaller and that error leads to people discussing why it happens it looks like. Barry -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution
Ok, last update for now - checked out the following page on pyinstaller.org, and, ended up posting to the mailing list, so, let's see: https://pyinstaller.org/en/latest/when-things-go-wrong.html Jacob Kruger +2782 413 4791 "Resistance is futile!...Acceptance is versatile..." On 2024/04/02 17:11, Barry wrote: On 1 Apr 2024, at 15:52, Jacob Kruger via Python-list wrote: Found many, many mentions of errors, with some of the same keywords, but, no resolutions that match my exact issue at all. Try asking the pyinstaller developers. I think there is a mailing list. Barry As in, most of them are mentioning older versions of python, and, mainly different platforms - mac and linux, but, various google searches have not mentioned much of using it on windows, and having it just stop working. Now did even try shifting over to python 3.12, but, still no-go. If launch pyinstaller under python 3.10 on this exact same machine, pyinstaller runs - just keep that older version hovering around for a couple of occasional tests, partly since some of my target environments are still running older versions of python, but anyway. Also, not really relevant, but, cx_freeze is perfectly able to generate executables for this same code, but, then not combining all output into a single file - will stick to that for now, but, not always as convenient, and, still wondering what changed here. Jacob Kruger +2782 413 4791 "Resistance is futile!...Acceptance is versatile..." On 2024/03/31 14:51, Barry wrote: On 31 Mar 2024, at 13:24, Jacob Kruger via Python-list wrote: pkg_resources.DistributionNotFound: The 'altgraph' distribution was not found and is required by the application I think I have seen this error being discussed before… A web search for pyinstaller and that error leads to people discussing why it happens it looks like. Barry -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution
> On 1 Apr 2024, at 15:52, Jacob Kruger via Python-list > wrote: > > Found many, many mentions of errors, with some of the same keywords, but, no > resolutions that match my exact issue at all. Try asking the pyinstaller developers. I think there is a mailing list. Barry > > > As in, most of them are mentioning older versions of python, and, mainly > different platforms - mac and linux, but, various google searches have not > mentioned much of using it on windows, and having it just stop working. > > > Now did even try shifting over to python 3.12, but, still no-go. > > > If launch pyinstaller under python 3.10 on this exact same machine, > pyinstaller runs - just keep that older version hovering around for a couple > of occasional tests, partly since some of my target environments are still > running older versions of python, but anyway. > > > Also, not really relevant, but, cx_freeze is perfectly able to generate > executables for this same code, but, then not combining all output into a > single file - will stick to that for now, but, not always as convenient, and, > still wondering what changed here. > > > Jacob Kruger > +2782 413 4791 > "Resistance is futile!...Acceptance is versatile..." > > >> On 2024/03/31 14:51, Barry wrote: >> On 31 Mar 2024, at 13:24, Jacob Kruger via Python-list wrote: >>> >>> pkg_resources.DistributionNotFound: The 'altgraph' distribution was not >>> found and is required by the application >> I think I have seen this error being discussed before… >> >> A web search for pyinstaller and that error leads to people discussing why >> it happens it looks like. >> >> Barry >> >> > -- > https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution
Found many, many mentions of errors, with some of the same keywords, but, no resolutions that match my exact issue at all. As in, most of them are mentioning older versions of python, and, mainly different platforms - mac and linux, but, various google searches have not mentioned much of using it on windows, and having it just stop working. Now did even try shifting over to python 3.12, but, still no-go. If launch pyinstaller under python 3.10 on this exact same machine, pyinstaller runs - just keep that older version hovering around for a couple of occasional tests, partly since some of my target environments are still running older versions of python, but anyway. Also, not really relevant, but, cx_freeze is perfectly able to generate executables for this same code, but, then not combining all output into a single file - will stick to that for now, but, not always as convenient, and, still wondering what changed here. Jacob Kruger +2782 413 4791 "Resistance is futile!...Acceptance is versatile..." On 2024/03/31 14:51, Barry wrote: On 31 Mar 2024, at 13:24, Jacob Kruger via Python-list wrote: pkg_resources.DistributionNotFound: The 'altgraph' distribution was not found and is required by the application I think I have seen this error being discussed before… A web search for pyinstaller and that error leads to people discussing why it happens it looks like. Barry -- https://mail.python.org/mailman/listinfo/python-list
Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution
> On 31 Mar 2024, at 13:24, Jacob Kruger via Python-list > wrote: > > pkg_resources.DistributionNotFound: The 'altgraph' distribution was not found > and is required by the application I think I have seen this error being discussed before… A web search for pyinstaller and that error leads to people discussing why it happens it looks like. Barry -- https://mail.python.org/mailman/listinfo/python-list
Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution
This started happening this past week, and, while it's worked fine in
the past, the moment I try to launch the pyinstaller process at all, to
generate compiled output, or even if just launch it with no command line
options, I receive the following error message:
pkg_resources.DistributionNotFound: The 'altgraph' distribution was not
found and is required by the application
The full contents of the output string when I even try to just launch
pyinstaller with no commands/arguments is the following:
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File
"C:\pythonScripts\monitoring_nssm\venv\Scripts\pyinstaller.exe\__main__.py",
line 7, in
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\__main__.py",
line 228, in _console_script_run
run()
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\__main__.py",
line 170, in run
parser = generate_parser()
^
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\__main__.py",
line 136, in generate_parser
import PyInstaller.building.build_main
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\building\build_main.py",
line 28, in
from PyInstaller.building.api import COLLECT, EXE, MERGE, PYZ
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\building\api.py",
line 32, in
from PyInstaller.building.splash import Splash # argument type
validation in EXE
^^
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\building\splash.py",
line 23, in
from PyInstaller.depend import bindepend
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\depend\bindepend.py",
line 25, in
from PyInstaller.depend import dylib, utils
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\depend\utils.py",
line 31, in
from PyInstaller.lib.modulegraph import modulegraph
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\PyInstaller\lib\modulegraph\modulegraph.py",
line 34, in
from altgraph.ObjectGraph import ObjectGraph
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\altgraph\__init__.py",
line 144, in
__version__ = pkg_resources.require("altgraph")[0].version
^
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\pkg_resources\__init__.py",
line 952, in require
needed = self.resolve(parse_requirements(requirements))
^^
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\pkg_resources\__init__.py",
line 813, in resolve
dist = self._resolve_dist(
^^^
File
"C:\pythonScripts\monitoring_nssm\venv\Lib\site-packages\pkg_resources\__init__.py",
line 854, in _resolve_dist
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'altgraph' distribution was not
found and is required by the application
# ---end of output---
I have tried completely removing python's installation, and,
reinstalling it, but, same issue more or less immediately.
If I freeze pip's installed list within this specific virtual
environment, it lists the following:
altgraph==0.17.4
packaging==24.0
pefile==2023.2.7
pyinstaller==6.5.0
pyinstaller-hooks-contrib==2024.3
pywin32-ctypes==0.2.2
# ---end of requirements.txt---
And, if, just for testing, I launch python interpreter, and, ask it to
import altgraph, it provides the same last line of error output?
If relevant, running with python 3.11.8, under windows 11 64-bit, and,
can't think of anything that specifically occurred/changed this past
week, besides normal things like windows updates, etc., but, don't
really think that's likely to be relevant, unless something to do with
pywin32 has caused an issue?
Should I try installing python 3.12 version instead and see if it changes?
Also, if relevant, while running under latest up-to-date version of
windows 11 64 bit, have in any case enabled case-sensitivity on the
folder I store all my python code in, just in case.
TIA
--
Jacob Kruger
+2782 413 4791
"Resistance is futile!...Acceptance is versatile..."
--
https://mail.python.org/mailman/listinfo/python-list
RE: Writing to clipboard in Python 3.11
It doesn't work in python 3.12.0
-Original Message-
From: Python-list On
Behalf Of Thomas Passin via Python-list
Sent: Tuesday, November 7, 2023 12:08 PM
To: python-list@python.org
Subject: Re: Writing to clipboard in Python 3.11
On 11/5/2023 7:51 PM, Rob Cliffe via Python-list wrote:
> Recently I switched from Python 3.8.3 to Python 3.11.4. A strange
> problem appeared which was not there before:
> I am using the win32clipboard backage (part of pywin32), and when I
> use
> SetClipboardData() to write text which consists ENTIRELY OF DIGITS to
> the clipboard, I either get an error (not always the same error
> message) or a program crash. The problem does not appear if I use
> SetClipboardText() instead.
> Sample program:
>
> from win32clipboard import *
> OpenClipboard()
> SetClipboardData(CF_UNICODETEXT, "A")
> SetClipboardData(CF_UNICODETEXT, "A0")
> SetClipboardData(CF_UNICODETEXT, "0A") SetClipboardText("0",
> CF_UNICODETEXT) print("OK so far") SetClipboardData(CF_UNICODETEXT,
> "0")
> CloseClipboard()
>
> Sample output:
>
> OK so far
> Traceback (most recent call last):
>File "R:\W.PY", line 8, in
> SetClipboardData(CF_UNICODETEXT, "0")
> pywintypes.error: (0, 'SetClipboardData', 'No error message is
> available')
>
> I can get round the problem by using SetClipboardText(). But can
> anyone shed light on this?
No, but I use pyperclip. It's cross platform. Maybe it doesn't have this
problem, though I don't know for sure.
--
https://mail.python.org/mailman/listinfo/python-list
--
https://mail.python.org/mailman/listinfo/python-list
Re: Writing to clipboard in Python 3.11
On 11/5/2023 7:51 PM, Rob Cliffe via Python-list wrote:
Recently I switched from Python 3.8.3 to Python 3.11.4. A strange
problem appeared which was not there before:
I am using the win32clipboard backage (part of pywin32), and when I use
SetClipboardData() to write text which consists ENTIRELY OF DIGITS to
the clipboard, I either get an error (not always the same error message)
or a program crash. The problem does not appear if I use
SetClipboardText() instead.
Sample program:
from win32clipboard import *
OpenClipboard()
SetClipboardData(CF_UNICODETEXT, "A")
SetClipboardData(CF_UNICODETEXT, "A0")
SetClipboardData(CF_UNICODETEXT, "0A")
SetClipboardText("0", CF_UNICODETEXT)
print("OK so far")
SetClipboardData(CF_UNICODETEXT, "0")
CloseClipboard()
Sample output:
OK so far
Traceback (most recent call last):
File "R:\W.PY", line 8, in
SetClipboardData(CF_UNICODETEXT, "0")
pywintypes.error: (0, 'SetClipboardData', 'No error message is available')
I can get round the problem by using SetClipboardText(). But can anyone
shed light on this?
No, but I use pyperclip. It's cross platform. Maybe it doesn't have
this problem, though I don't know for sure.
--
https://mail.python.org/mailman/listinfo/python-list
Re: Writing to clipboard in Python 3.11
On 2023-11-06 00:51, Rob Cliffe via Python-list wrote:
Recently I switched from Python 3.8.3 to Python 3.11.4. A strange
problem appeared which was not there before:
I am using the win32clipboard backage (part of pywin32), and when I use
SetClipboardData() to write text which consists ENTIRELY OF DIGITS to
the clipboard, I either get an error (not always the same error message)
or a program crash. The problem does not appear if I use
SetClipboardText() instead.
Sample program:
from win32clipboard import *
OpenClipboard()
SetClipboardData(CF_UNICODETEXT, "A")
SetClipboardData(CF_UNICODETEXT, "A0")
SetClipboardData(CF_UNICODETEXT, "0A")
SetClipboardText("0", CF_UNICODETEXT)
print("OK so far")
SetClipboardData(CF_UNICODETEXT, "0")
CloseClipboard()
Sample output:
OK so far
Traceback (most recent call last):
File "R:\W.PY", line 8, in
SetClipboardData(CF_UNICODETEXT, "0")
pywintypes.error: (0, 'SetClipboardData', 'No error message is available')
I can get round the problem by using SetClipboardText(). But can anyone
shed light on this?
It also happens in Python 3.10, but not Python 3.9.
--
https://mail.python.org/mailman/listinfo/python-list
Writing to clipboard in Python 3.11
Recently I switched from Python 3.8.3 to Python 3.11.4. A strange
problem appeared which was not there before:
I am using the win32clipboard backage (part of pywin32), and when I use
SetClipboardData() to write text which consists ENTIRELY OF DIGITS to
the clipboard, I either get an error (not always the same error message)
or a program crash. The problem does not appear if I use
SetClipboardText() instead.
Sample program:
from win32clipboard import *
OpenClipboard()
SetClipboardData(CF_UNICODETEXT, "A")
SetClipboardData(CF_UNICODETEXT, "A0")
SetClipboardData(CF_UNICODETEXT, "0A")
SetClipboardText("0", CF_UNICODETEXT)
print("OK so far")
SetClipboardData(CF_UNICODETEXT, "0")
CloseClipboard()
Sample output:
OK so far
Traceback (most recent call last):
File "R:\W.PY", line 8, in
SetClipboardData(CF_UNICODETEXT, "0")
pywintypes.error: (0, 'SetClipboardData', 'No error message is available')
I can get round the problem by using SetClipboardText(). But can anyone
shed light on this?
Best wishes
Rob Cliffe
--
https://mail.python.org/mailman/listinfo/python-list
RE: problems installing Python 3.11
>-Original Message-
>From: Python-list muenchen...@python.org> On Behalf Of Bernd Lentes via Python-list
>Sent: Friday, August 11, 2023 12:01 PM
>To: Terry Reedy
>Cc: Python ML (python-list@python.org)
>Subject: RE: problems installing Python 3.11
Hi,
I read the readme.rst and found something helpful.
I reran explicitly the test which failed:
=
localhost:~/Python-3.11.4 # make test TESTOPTS="-v test_tools"
CC='gcc -pthread' LDSHARED='gcc -pthread -shared' OPT='-DNDEBUG -g -fwrapv
-O3 -Wall' ./python -E ./setup.py build
running build
running build_ext
The necessary bits to build these optional modules were not found:
_bz2 _curses _curses_panel
_dbm _gdbm _hashlib
_lzma _ssl _tkinter
_uuid nis readline
To find the necessary bits, look in setup.py in detect_modules() for the
module's name.
The following modules found by detect_modules() in setup.py have not
been built, they are *disabled* by configure:
_sqlite3
Could not build the ssl module!
Python requires a OpenSSL 1.1.1 or newer
running build_scripts
copying and adjusting /root/Python-3.11.4/Tools/scripts/pydoc3 ->
build/scripts-3.11
copying and adjusting /root/Python-3.11.4/Tools/scripts/idle3 ->
build/scripts-3.11
copying and adjusting /root/Python-3.11.4/Tools/scripts/2to3 ->
build/scripts-3.11
changing mode of build/scripts-3.11/pydoc3 from 644 to 755
changing mode of build/scripts-3.11/idle3 from 644 to 755
changing mode of build/scripts-3.11/2to3 from 644 to 755
renaming build/scripts-3.11/pydoc3 to build/scripts-3.11/pydoc3.11
renaming build/scripts-3.11/idle3 to build/scripts-3.11/idle3.11
renaming build/scripts-3.11/2to3 to build/scripts-3.11/2to3-3.11
./python -E ./Tools/scripts/run_tests.py -v test_tools
/root/Python-3.11.4/python -u -W default -bb -E -E -m test -r -w -j 0 -u
all,-largefile,-audio,-gui -v test_tools
== CPython 3.11.4 (main, Aug 11 2023, 00:05:59) [GCC 7.5.0]
== Linux-5.14.21-150500.55.12-default-x86_64-with-glibc2.31 little-endian
== cwd: /root/Python-3.11.4/build/test_python_8347æ
== CPU count: 32
== encodings: locale=UTF-8, FS=utf-8
Using random seed 9455548
0:00:00 load avg: 0.07 Run tests in parallel using 34 child processes
0:00:30 load avg: 2.51 running: test_tools (30.0 sec)
0:01:00 load avg: 2.44 running: test_tools (1 min)
0:01:30 load avg: 2.16 running: test_tools (1 min 30 sec)
0:01:40 load avg: 2.21 [1/1] test_tools passed (1 min 40 sec)
test_alter_comments (test.test_tools.test_fixcid.Test.test_alter_comments) ...
ok
test_directory (test.test_tools.test_fixcid.Test.test_directory) ... ok
test_parse_strings (test.test_tools.test_fixcid.Test.test_parse_strings) ... ok
test_freeze_simple_script
(test.test_tools.test_freeze.TestFreeze.test_freeze_simple_script) ... creating
the script to be frozen at /tmp/tmp73do0elf/app.py
copying the source tree into /tmp/tmp73do0elf/cpython...
configuring python in /tmp/tmp73do0elf/python-build...
CalledProcessError: Command '['/tmp/tmp73do0elf/cpython/python', '-c', 'import
sysconfig; print(sysconfig.get_config_var("CONFIG_ARGS"))']' returned non-zero
exit status 1.
--- STDOUT ---
--- STDERR ---
Traceback (most recent call last):
File "", line 1, in
File "/tmp/tmp73do0elf/cpython/Lib/sysconfig.py", line 715, in get_config_var
return get_config_vars().get(name)
^
File "/tmp/tmp73do0elf/cpython/Lib/sysconfig.py", line 670, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/tmp/tmp73do0elf/cpython/Lib/sysconfig.py", line 531, in _init_posix
_temp = __import__(name, globals(), locals(), ['build_time_vars'], 0)
^
ModuleNotFoundError: No module named '_sysconfigdata__linux_x86_64-linux-gnu'
END
building python parallel='-j21' in /tmp/tmp73do0elf/python-build...
installing python into /tmp/tmp73do0elf/python-installation...
freezing /tmp/tmp73do0elf/app.py...
ok
test_gprof (test.test_tools.test_gprof2html.Gprof2htmlTests.test_gprof) ... ok
test_POT_Creation_Date
(test.test_tools.test_i18n.Test_pygettext.test_POT_Creation_Date)
Match the date format from xgettext for POT-Creation-Date ... ok
test_calls_in_fstring_with_keyword_args
(test.test_tools.test_i18n.Test_pygettext.test_calls_in_fstring_with_keyword_args)
... ok
test_calls_in_fstring_with_multiple_args
(test.test_tools.test_i18n.Test_pygettext.test_calls_in_fstring_with_multiple_args)
... ok
test_calls_in_fstring_with_partially_wrong_expression
(test.test_tools.test_i18n.Test_pygettext.test_calls_in_fstring_with_partially_wrong_expression)
... ok
test_calls_in_fstri
RE: problems installing Python 3.11
>-Original Message- >From: Terry Reedy >Sent: Thursday, August 10, 2023 9:55 PM >To: Bernd Lentes >Subject: Re: problems installing Python 3.11 > >On 8/10/2023 3:28 PM, Bernd Lentes via Python-list wrote: > >Private response because cannot post at present. > >It appears that what failed is building a C++ extension. (You can dig into >the test >code to check. It is skipped on my Windows.) If you do not need to do that, >you >should not have a problem. > Hi Terry, I found out that cc1plus was missing. I installed g++, rerun make and this error disappeared. But another has arised: --- STDERR --- Traceback (most recent call last): File "", line 1, in File "/tmp/tmphpwu2qwj/cpython/Lib/sysconfig.py", line 715, in get_config_var return get_config_vars().get(name) ^ File "/tmp/tmphpwu2qwj/cpython/Lib/sysconfig.py", line 670, in get_config_vars _init_posix(_CONFIG_VARS) File "/tmp/tmphpwu2qwj/cpython/Lib/sysconfig.py", line 531, in _init_posix _temp = __import__(name, globals(), locals(), ['build_time_vars'], 0) ^ ModuleNotFoundError: No module named '_sysconfigdata__linux_x86_64-linux-gnu' END building python parallel='-j21' in /tmp/tmphpwu2qwj/python-build... installing python into /tmp/tmphpwu2qwj/python-installation... freezing /tmp/tmphpwu2qwj/app.py... ok -- Ran 1 test in 95.606s OK == Tests result: FAILURE then SUCCESS == 404 tests OK. 30 tests skipped: test_bz2 test_curses test_dbm_gnu test_dbm_ndbm test_devpoll test_gdb test_idle test_ioctl test_kqueue test_launcher test_lzma test_msilib test_nis test_ossaudiodev test_readline test_smtpnet test_sqlite3 test_ssl test_startfile test_tcl test_tix test_tk test_ttk_guionly test_ttk_textonly test_turtle test_winconsoleio test_winreg test_winsound test_zipfile64 test_zoneinfo 1 re-run test: test_tools Total duration: 29 min 56 sec Tests result: FAILURE then SUCCESS Or does " FAILURE then SUCCESS" mean that everything is ok now ? Bernd Helmholtz Zentrum München – Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH) Ingolstädter Landstraße 1, D-85764 Neuherberg, https://www.helmholtz-munich.de Geschäftsführung: Prof. Dr. med. Dr. h.c. Matthias Tschöp, Daniela Sommer (komm.) | Aufsichtsratsvorsitzende: MinDir’in Prof. Dr. Veronika von Messling Registergericht: Amtsgericht München HRB 6466 | USt-IdNr. DE 129521671 -- https://mail.python.org/mailman/listinfo/python-list
problems installing Python 3.11
Hi ML,
i hope this is the right place for my question. If not please tell me where I
can ask.
I tried to install python 3.11.4 on a SLES 15 SP5.
./configure ran fine, just one package missing. Installed the package,
configure ran fine with complaints.
make was ok, make test not.
This is what I got to the end:
===
===
ERROR: test_build_cpp11 (test.test_cppext.TestCPPExt.test_build_cpp11)
--
Traceback (most recent call last):
File "/root/Python-3.11.4/Lib/test/test_cppext.py", line 21, in
test_build_cpp11
self.check_build(False, '_testcpp11ext')
File "/root/Python-3.11.4/Lib/test/test_cppext.py", line 39, in check_build
self._check_build(std_cpp03, extension_name)
File "/root/Python-3.11.4/Lib/test/test_cppext.py", line 80, in _check_build
run_cmd('Build', cmd)
File "/root/Python-3.11.4/Lib/test/test_cppext.py", line 64, in run_cmd
subprocess.run(cmd, check=True)
File "/root/Python-3.11.4/Lib/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['env/bin/python', '-X', 'dev',
'/root/Python-3.11.4/Lib/test/setup_testcppext.py', 'build_ext', '--verbose']'
returned non-zero exit status 1.
--
Ran 2 tests in 9.939s
FAILED (errors=2)
test test_cppext failed
1 test failed again:
test_cppext
== Tests result: FAILURE then FAILURE ==
403 tests OK.
1 test failed:
test_cppext
30 tests skipped:
test_bz2 test_curses test_dbm_gnu test_dbm_ndbm test_devpoll
test_gdb test_idle test_ioctl test_kqueue test_launcher test_lzma
test_msilib test_nis test_ossaudiodev test_readline test_smtpnet
test_sqlite3 test_ssl test_startfile test_tcl test_tix test_tk
test_ttk_guionly test_ttk_textonly test_turtle test_winconsoleio
test_winreg test_winsound test_zipfile64 test_zoneinfo
2 re-run tests:
test___all__ test_cppext
Total duration: 28 min 23 sec
Tests result: FAILURE then FAILURE
make: *** [Makefile:1798: test] Error 2
=
I'm not very familiar with compiling software, normally I use the packages from
my distro.
Can you help me ? Or maybe there is no big problem, afterall 403 tests were
fine and just two not.
I need Python 3.11 for borgbackup.
Thanks.
Bernd
Bernd Lentes
--
Bernd Lentes
System Administrator
MCD
Helmholtzzentrum München
+49 89 3187 1241
bernd.len...@helmholtz-munich.de
https://www.helmholtz-munich.de/en/mcd
Helmholtz Zentrum München – Deutsches Forschungszentrum für Gesundheit und
Umwelt (GmbH)
Ingolstädter Landstraße 1, D-85764 Neuherberg, https://www.helmholtz-munich.de
Geschäftsführung: Prof. Dr. med. Dr. h.c. Matthias Tschöp, Daniela Sommer
(komm.) | Aufsichtsratsvorsitzende: MinDir’in Prof. Dr. Veronika von Messling
Registergericht: Amtsgericht München HRB 6466 | USt-IdNr. DE 129521671
--
https://mail.python.org/mailman/listinfo/python-list
Re: Python 3.11 with Pygame
On 10/25/22 11:47, Joni Ekholm wrote: Hi, Does Pygame work with 3.11? with 3.10 no problems. Br Joni It often takes a while for projects with binary wheels to to catch up to new Python releases. You can always go check: https://pypi.org/project/pygame/#files From that, it seems there aren't 3.11 wheels yet. -- https://mail.python.org/mailman/listinfo/python-list
Python 3.11 with Pygame
Hi, Does Pygame work with 3.11? with 3.10 no problems. Br Joni -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.11 final (3.11.0) is available
Python 3.11 is finally released. In the CPython release team, we have put a
lot of effort into making 3.11 the best version of Python possible. Better
tracebacks, faster Python, exception groups and except*, typing
improvements and much more. Get it here:
https://www.python.org/downloads/release/python-3110/
## This is the stable release of Python 3.11.0
Python 3.11.0 is the newest major release of the Python programming
language, and it contains many new features and optimizations.
# Major new features of the 3.11 series, compared to 3.10
Some of the new major new features and changes in Python 3.11 are:
## General changes
* [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include
Fine-Grained Error Locations in Tracebacks
* [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups
and `except*`
* [PEP 680](https://www.python.org/dev/peps/pep-0680/) -- tomllib: Support
for Parsing TOML in the Standard Library
* [gh-90908](https://github.com/python/cpython/issues/90908) -- Introduce
task groups to asyncio
* [gh-34627](https://github.com/python/cpython/issues/34627/) -- Atomic
grouping (`(?>...)`) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are
now supported in regular expressions.
* The [Faster CPython Project](https://github.com/faster-cpython/) is
already yielding some exciting results. Python 3.11 is up to 10-60% faster
than Python 3.10. On average, we measured a 1.22x speedup on the standard
benchmark suite. See [Faster CPython](
https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details.
## Typing and typing language changes
* [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type
* [PEP 646](https://www.python.org/dev/peps/pep-0646/) -- Variadic Generics
* [PEP 675](https://www.python.org/dev/peps/pep-0675/) -- Arbitrary Literal
String Type
* [PEP 655](https://www.python.org/dev/peps/pep-0655/) -- Marking
individual TypedDict items as required or potentially-missing
* [PEP 681](https://www.python.org/dev/peps/pep-0681/) -- Data Class
Transforms
# More resources
* [Online Documentation](https://docs.python.org/3.11/)
* [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release
Schedule
* Report bugs at [
https://github.com/python/cpython/issues](https://github.com/python/cpython/issues)
.
* [Help fund Python and its community](/psf/donations/).
# And now for something completely different
When a spherical non-rotating body of a critical radius collapses under its
own gravitation under general relativity, theory suggests it will collapse
to a single point. This is not the case with a rotating black hole (a Kerr
black hole). With a fluid rotating body, its distribution of mass is not
spherical (it shows an equatorial bulge), and it has angular momentum.
Since a point cannot support rotation or angular momentum in classical
physics (general relativity being a classical theory), the minimal shape of
the singularity that can support these properties is instead a ring with
zero thickness but non-zero radius, and this is referred to as a
ringularity or Kerr singularity.
This kind of singularity has the following peculiar property. The spacetime
allows a geodesic curve (describing the movement of observers and photons
in spacetime) to pass through the center of this ring singularity. The
region beyond permits closed time-like curves. Since the trajectory of
observers and particles in general relativity are described by time-like
curves, it is possible for observers in this region to return to their
past. This interior solution is not likely to be physical and is considered
a purely mathematical artefact.
There are some other interesting free-fall trajectories. For example, there
is a point in the axis of symmetry that has the property that if an
observer is below this point, the pull from the singularity will force the
observer to pass through the middle of the ring singularity to the region
with closed time-like curves and it will experience repulsive gravity that
will push it back to the original region, but then it will experience the
pull from the singularity again and will repeat this process forever. This
is, of course, only if the extreme gravity doesn’t destroy the observer
first.
# We hope you enjoy the new releases!
Thanks to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation.
https://www.python.org/psf/
If you have any questions, please reach out to me or another member of the
release team :)
Your friendly release team,
Ned Deily @nad https://discuss.python.org/u/nad
Steve Dower @steve.dower https://discuss.python.org/u/steve.dower
Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal
--
https://mail.python.org/mailman/listinfo/python-list
python 3.11
Is python 3.11 still being release today? Just wondering. Not sure when during the day this is done. Thanks. -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.11 release candidate 2 (3.11.0rc2) is available
Python 3.11 is one month away, can you believe it? This snake is still
trying to bite as it has been an interesting day of fighting fires, release
blockers, and a bunch of late bugs but your friendly release team always
delivers :)
You can get this new release while is still fresh here:
https://www.python.org/downloads/release/python-3110rc2/
## This is the second release candidate of Python 3.11
This release, **3.11.0rc2**, is the last preview before the final release
of Python 3.11.0 on 2022-10-24.
Entering the release candidate phase, only reviewed code changes which are
clear bug fixes are allowed between this release candidate and the final
release. The second candidate and the last planned release preview is
currently planned for Monday, 2022-09-05 while the official release is
planned for Monday, 2022-10-24.
There will be no ABI changes from this point forward in the 3.11 series and
the goal is that there will be as few code changes as possible.
## Modification of the final release
Due to the fact that we needed to delay the last release candidate by a
week and because of personal scheduling problems I am delaying the final
release to 2022-10-24 (three weeks from the original date).
## Call to action
⚠️⚠️⚠️⚠️⚠️⚠️⚠️
The 3.11 branch is now accepting changes for 3.11.**1**. To maximize
stability, the final release will be cut from the v3.11.0rc2 tag. If you
need the release manager (me) to cherry-pick any critical fixes, mark
issues as release blockers, and/or add me as a reviewer on a critical
backport PR on GitHub. To see which changes are currently cherry-picked for
inclusion in 3.11.0, look at the short-lived branch-v3.11.0
https://github.com/python/cpython/tree/branch-v3.11.0 on GitHub.
⚠️⚠️⚠️⚠️⚠️⚠️⚠️
---
Core developers: all eyes on the docs now
* Are all your changes properly documented?
* Did you notice other changes you know of to have insufficient
documentation?
Community members
We strongly encourage maintainers of third-party Python projects to prepare
their projects for 3.11 compatibilities during this phase. As always,
report any issues to [the Python bug tracker ](https://github.com/issues).
Please keep in mind that this is a preview release and its use is **not**
recommended for production environments.
# Major new features of the 3.11 series, compared to 3.10
Some of the new major new features and changes in Python 3.11 are:
## General changes
* [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include
Fine-Grained Error Locations in Tracebacks
* [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups
and `except*`
* [PEP 680](https://www.python.org/dev/peps/pep-0680/) -- tomllib: Support
for Parsing TOML in the Standard Library
* [gh-90908](https://github.com/python/cpython/issues/90908) -- Introduce
task groups to asyncio
* [gh-34627](https://github.com/python/cpython/issues/34627/) -- Atomic
grouping (`(?>...)`) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are
now supported in regular expressions.
* The [Faster CPython Project](https://github.com/faster-cpython/) is
already yielding some exciting results. Python 3.11 is up to 10-60% faster
than Python 3.10. On average, we measured a 1.22x speedup on the standard
benchmark suite. See [Faster CPython](
https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details.
## Typing and typing language changes
* [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type
* [PEP 646](https://www.python.org/dev/peps/pep-0646/) -- Variadic Generics
* [PEP 675](https://www.python.org/dev/peps/pep-0675/) -- Arbitrary Literal
String Type
* [PEP 655](https://www.python.org/dev/peps/pep-0655/) -- Marking
individual TypedDict items as required or potentially-missing
* [PEP 681](https://www.python.org/dev/peps/pep-0681/) -- Data Class
Transforms
(Hey, **fellow core developer,** if a feature you find important is
missing from this list, [let Pablo know](mailto:pablog...@python.org
).)
The next release will be the final release of Python 3.11.0, which is
currently scheduled for Monday, 2022-10-24.
# More resources
* [Online Documentation](https://docs.python.org/3.11/)
* [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release
Schedule
* Report bugs at [
https://github.com/python/cpython/issues](https://github.com/python/cpython/issues)
.
* [Help fund Python and its community](/psf/donations/).
# And now for something completely different
In general relativity, a white hole is a theoretical region of spacetime
and singularity that cannot be entered from the outside, although
energy-matter, light and information can escape from it. In this sense, it
is the reverse of a black hole, which can be entered only from the outside
and from which energy-matter, light and information cannot escape. White
holes appear in the theory of eternal black holes. In addition to a black
hole region in the future, such a solution of the Einstein field equations
has a white h
Re: [python-committers] [RELEASE] Python 3.11 release candidate 1 (3.11.0rc1) is available
On 8/8/2022 12:59 PM, Pablo Galindo Salgado wrote: Python 3.11.0 is almost ready. This release, 3.11.0rc1, is the penultimate release preview. You can get it here: ## This is the first release candidate of Python 3.11 https://www.python.org/downloads/release/python-3110rc1/ <https://www.python.org/downloads/release/python-3110rc1/> This release, **3.11.0rc1**, is the penultimate release preview. Entering the release candidate phase, only reviewed code changes which are clear bug fixes are allowed between this release candidate and the final release. The second candidate and the last planned release preview is currently planned for Monday, 2022-09-05 while the official release is planned for Monday, 2022-10-03. There will be no ABI changes from this point forward in the 3.11 series and the goal is that there will be as few code changes as possible. Core developers: all eyes on the docs now * Are all your changes properly documented? * Did you notice other changes you know of to have insufficient documentation? Pablo, are you going to unlock 3.11 and revert merges you don't like, or keep it locked and merge PRs you think are OK? -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] Python 3.11 release candidate 1 (3.11.0rc1) is available
Python 3.11.0 is almost ready. This release, 3.11.0rc1, is the penultimate
release preview. You can get it here:
## This is the first release candidate of Python 3.11
https://www.python.org/downloads/release/python-3110rc1/
This release, **3.11.0rc1**, is the penultimate release preview. Entering
the release candidate phase, only reviewed code changes which are clear bug
fixes are allowed between this release candidate and the final release. The
second candidate and the last planned release preview is currently planned
for Monday, 2022-09-05 while the official release is planned for Monday,
2022-10-03.
There will be no ABI changes from this point forward in the 3.11 series and
the goal is that there will be as few code changes as possible.
## Call to action
Core developers: all eyes on the docs now
* Are all your changes properly documented?
* Did you notice other changes you know of to have insufficient
documentation?
Community members
We strongly encourage maintainers of third-party Python projects to prepare
their projects for 3.11 compatibilities during this phase. As always,
report any issues to [the Python bug tracker ](https://github.com/issues).
Please keep in mind that this is a preview release and its use is **not**
recommended for production environments.
# Major new features of the 3.11 series, compared to 3.10
Some of the new major new features and changes in Python 3.11 are:
## General changes
* [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include
Fine-Grained Error Locations in Tracebacks
* [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups
and `except*`
* [PEP 680](https://www.python.org/dev/peps/pep-0680/) -- tomllib: Support
for Parsing TOML in the Standard Library
* [gh-90908](https://github.com/python/cpython/issues/90908) -- Introduce
task groups to asyncio
* [gh-34627](https://github.com/python/cpython/issues/34627/) -- Atomic
grouping (`(?>...)`) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are
now supported in regular expressions.
* The [Faster CPython Project](https://github.com/faster-cpython/) is
already yielding some exciting results. Python 3.11 is up to 10-60% faster
than Python 3.10. On average, we measured a 1.22x speedup on the standard
benchmark suite. See [Faster CPython](
https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details.
## Typing and typing language changes
* [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type
* [PEP 646](https://www.python.org/dev/peps/pep-0646/) -- Variadic Generics
* [PEP 675](https://www.python.org/dev/peps/pep-0675/) -- Arbitrary Literal
String Type
* [PEP 655](https://www.python.org/dev/peps/pep-0655/) -- Marking
individual TypedDict items as required or potentially-missing
* [PEP 681](https://www.python.org/dev/peps/pep-0681/) -- Data Class
Transforms
(Hey, **fellow core developer,** if a feature you find important is
missing from this list, [let Pablo know](mailto:pablog...@python.org
).)
The next pre-release of Python 3.11 will be 3.11.0rc2, currently scheduled
for Monday, 2022-09-05.
# More resources
* [Online Documentation](https://docs.python.org/3.11/)
* [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release
Schedule
* Report bugs at [
https://github.com/python/cpython/issues](https://github.com/python/cpython/issues)
.
* [Help fund Python and its community](/psf/donations/).
# And now for something completely different
A quark star is a hypothetical type of compact, exotic star, where
extremely high core temperature and pressure have forced nuclear particles
to form quark matter, a continuous state of matter consisting of free
quarks.
Some massive stars collapse to form neutron stars at the end of their life
cycle, as has been both observed and explained theoretically. Under the
extreme temperatures and pressures inside neutron stars, the neutrons are
normally kept apart by degeneracy pressure, stabilizing the star and
hindering further gravitational collapse. However, it is hypothesized that
under even more extreme temperature and pressure, the degeneracy pressure
of the neutrons is overcome, and the neutrons are forced to merge and
dissolve into their constituent quarks, creating an ultra-dense phase of
quark matter based on densely packed quarks. In this state, a new
equilibrium is supposed to emerge, as a new degeneracy pressure between the
quarks, as well as repulsive electromagnetic forces, will occur and hinder
total gravitational collapse.
If these ideas are correct, quark stars might occur, and be observable,
somewhere in the universe. Theoretically, such a scenario is seen as
scientifically plausible, but it has been impossible to prove both
observationally and experimentally because the very extreme conditions
needed for stabilizing quark matter cannot be created in any laboratory nor
observed directly in nature. The stability of quark matter, and hence the
existence of quark stars, is for th
Re: [RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available
BSD-style checksum format hashes for the release artefacts: SHA256 (python-3.11.0b4-embed-arm64.zip) = 272c6bb4948c597f6578f64c2b15a70466c5dfb49f9b84dba57a84e59e7bd4ef SHA256 (python-3.11.0b4-amd64.exe) = a3514b0401e6a85416f3e080586c86ccd9e2e62c8a54b9119d9e6415e3cadb62 SHA256 (python-3.11.0b4-macos11.pkg) = 860647775d4e6cd1a8d71412233df5dbe3aa2886fc16d82a59ab2f625464f2d7 SHA256 (python-3.11.0b4-embed-win32.zip) = 36b81da7986f8d59be61adb452681dbd3257ebb90bd89092b2fbbd9356e06425 SHA256 (python-3.11.0b4-arm64.exe) = ad0d1429682ba1edc0c0cf87f68a3d1319b887b715da70a91db41d02be4997a4 SHA256 (python-3.11.0b4-embed-amd64.zip) = 66e6bb44c36da36ecc1de64efdb92f52ba3a19221dba2a89e22e39f715bd205b SHA256 (Python-3.11.0b4.tar.xz) = 1d93b611607903e080417c1a9567f5fbbf5124cc5c86f4afbba1c8fd34c5f6fb SHA256 (python-3.11.0b4.exe) = 6febc152711840337f53e2fd5dc12bb2b1314766f591129282fd372c855fa877 SHA256 (Python-3.11.0b4.tgz) = 257e753db2294794fa8dec072c228f3f53fd541a303de9418854b3c2512ccbec -- https://mail.python.org/mailman/listinfo/python-list
[RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available
I cannot believe I am writing this, but Python 3.11.b4 is finally
available!! [image: :scream:] [image: :tada:] [image: :tada:] [image:
:tada:]
https://www.python.org/downloads/release/python-3110b4/
##[image: :warning:][image: :warning:][image: :warning:] PLEASE HELP US TO
TEST THIS RELEASE [image: :warning:][image: :warning:][image: :warning:]
Due to the modified release schedule and the stability concerns regarding
the past beta releases, please, please, please, please, help us to test
Python 3.11 by testing this beta releases.
* if you maintain a library or a third-party package. Test the beta
releases!
* If you have code that you maintain at work/research
centre/classroom/whatever. Test the beta releases!
* If you are a multi-million corporation that uses Python. Test the beta
releases!
* If you are a single-person company that uses Python. Test the beta
releases!
* If you have a bunch of Python scripts. Test the beta releases!
* If you use Python for work, research, teaching or literally for anything.
Test the beta releases!
* If you ...
In summary: no matter who you are or what you do. Test the beta releases!
Is **very** important for us that we identify all possible things that may
break your code **before** the final release is done and we can only do
this if you help us by testing the beta releases and then report anything
that doesn't work!
## Credit where credit is due [image: :pray:]
Lots of thanks to Christian Heimes, Brandt Bucher, Irit Katriel, Mark
Shannon, Dennis Sweeney, Kumar Aditya and other contributors (sorry if I am
missing any names) that worked really hard against time to help me and the
release team with the release blockers. They are all awesome and we and the
Python community are very lucky to have them in the team [image: :heart:]
## What happens with the next betas?
As stated in [my previous communication](
https://mail.python.org/archives/list/python-...@python.org/thread/3JWVCSBPBFWY5ZWSJ7RYB6FS5NIMCEOY/)
we are in a special situation regarding beta releases. As the requirements
to continue with the regular schedule are met, we are going to still target
the final release of Monday, 2022-10-03.
Python 3.11.0b5 was supposed to be released two days ago, so we are
obviously delayed. As we are targeting the regular release schedule, I'm
going to try to release 3.11.0b5 on Thursday, 2022-07-25.
## This is a beta preview of Python 3.11
Python 3.11 is still in development. 3.11.0b4 is the fourth of five planned
beta release previews. Beta release previews are intended to give the wider
community the opportunity to test new features and bug fixes and to prepare
their projects to support the new feature release.
We **strongly encourage** maintainers of third-party Python projects to
**test with 3.11** during the beta phase and report issues found to [the
Python bug tracker](https://github.com/python/cpython/issues) as soon as
possible. While the release is planned to be feature complete entering the
beta phase, it is possible that features may be modified or, in rare cases,
deleted up until the start of the release candidate phase (Monday,
2021-08-02). Our goal is have no ABI changes after beta 5 and as few code
changes as possible after 3.11.0rc1, the first release candidate. To
achieve that, it will be **extremely important** to get as much exposure
for 3.11 as possible during the beta phase.
Please keep in mind that this is a preview release and its use is **not**
recommended for production environments.
# Major new features of the 3.11 series, compared to 3.10
Some of the new major new features and changes in Python 3.11 are:
## General changes
* [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include
Fine-Grained Error Locations in Tracebacks
* [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups
and except*
* [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support
for Parsing TOML in the Standard Library
* [PEP 681](https://www.python.org/dev/peps/pep-0681/)-- Data Class
Transforms
* [bpo-46752](https://bugs.python.org/issue46752)-- Introduce task groups
to asyncio
* [bpo-433030](https://github.com/python/cpython/issues/34627/) -- Atomic
grouping ((?>...)) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are
now supported in regular expressions.
* The [Faster Cpython Project](https://github.com/faster-cpython/) is
already yielding some exciting results. Python 3.11 is up to 10-60% faster
than Python 3.10. On average, we measured a 1.22x speedup on the standard
benchmark suite. See [Faster CPython](
https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details.
## Typing and typing language changes
* [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type
* [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics
* [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal
String Type
* [PEP 655](https://www.python.org/dev/peps/pep-065
[RELEASE] The second Python 3.11 beta (3.11.0b2) is available
Does anyone want bug fixes? Because we have 164 new commits fixing
different things, from code to documentation. If you have reported some
issue after 3.11.0b1, you should check if is fixed and if not, make sure
you tell us so we can take a look. We still have two more betas to go so
help us to make sure we don't miss anything so everything is ready for the
final release!!
https://www.python.org/downloads/release/python-3110b2/
## This is a beta preview of Python 3.11
Python 3.11 is still in development. 3.11.0b2 is the second of four planned
beta release previews. Beta release previews are intended to give the wider
community the opportunity to test new features and bug fixes and to prepare
their projects to support the new feature release.
We **strongly encourage** maintainers of third-party Python projects to
**test with 3.11** during the beta phase and report issues found to [the
Python bug tracker](https://github.com/python/cpython/issues) as soon as
possible. While the release is planned to be feature complete entering the
beta phase, it is possible that features may be modified or, in rare cases,
deleted up until the start of the release candidate phase (Monday,
2021-08-02). Our goal is to have no ABI changes after beta 4 and as few
code changes as possible after 3.11.0rc1, the first release candidate. To
achieve that, it will be **extremely important** to get as much exposure
for 3.11 as possible during the beta phase.
Please keep in mind that this is a preview release and its use is **not**
recommended for production environments.
# Major new features of the 3.11 series, compared to 3.10
Many new features for Python 3.11 are still being planned and written.
Among the new major new features and changes so far:
* [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include
Fine-Grained Error Locations in Tracebacks
* [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups
and except*
* [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type
* [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics
* [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support
for Parsing TOML in the Standard Library
* [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal
String Type
* [PEP 655](https://www.python.org/dev/peps/pep-0655/)-- Marking individual
TypedDict items as required or potentially-missing
* [PEP 681](https://www.python.org/dev/peps/pep-0681/)-- Data Class
Transforms
* [bpo-46752](https://bugs.python.org/issue46752)-- Introduce task groups
to asyncio
* [bpo-433030](https://github.com/python/cpython/issues/34627/) -- Atomic
grouping ((?>...)) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are
now supported in regular expressions.
* The [Faster Cpython Project](https://github.com/faster-cpython/) is
already yielding some exciting results. Python 3.11 is up to 10-60% faster
than Python 3.10. On average, we measured a 1.22x speedup on the standard
benchmark suite. See [Faster CPython](
https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details.
* (Hey, **fellow core developer,** if a feature you find important
is missing from this list, [let Pablo know](mailto:pablog...@python.org
).)
The next pre-release of Python 3.11 will be 3.11.0b3, currently scheduled
for Thursday, 2022-06-16.
# More resources
* [Online Documentation](https://docs.python.org/3.11/)
* [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release
Schedule
* Report bugs at [https://bugs.python.org](https://bugs.python.org).
* [Help fund Python and its community](/psf/donations/).
# And now for something completely different
The Planck time is the time required for light to travel a distance of 1
Planck length in a vacuum, which is a time interval of approximately
`5.39*10^(−44)` s. No current physical theory can describe timescales
shorter than the Planck time, such as the earliest events after the Big
Bang, and it is conjectured that the structure of time breaks down on
intervals comparable to the Planck time. While there is currently no known
way to measure time intervals on the scale of the Planck time, researchers
in 2020 found that the accuracy of an atomic clock is constrained by
quantum effects on the order of the Planck time, and for the most precise
atomic clocks thus far they calculated that such effects have been ruled
out to around `10^−33` s, or 10 orders of magnitude above the Planck scale.
# We hope you enjoy the new releases!
Thanks to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation.
https://www.python.org/psf/
Regards from sunny London,
Pablo Galindo Salgado
--
https://mail.python.org/mailman/listinfo/python-list
[RELEASE] The first Python 3.11 beta (3.11.0b1) is available - Feature freeze is here
We did it, team!! After quite a bumpy release process and a bunch of last-time fixes, we have reached **beta 1** and **feature freeze**. What a ride eh? You can get the shiny new release artefacts from here: https://www.python.org/downloads/release/python-3110b1/ ## This is a beta preview of Python 3.11 Python 3.11 is still in development. 3.11.0b1 is the first of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We **strongly encourage** maintainers of third-party Python projects to **test with 3.11** during the beta phase and report issues found to [the Python bug tracker](https://bugs.python.org) as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Monday, 2021-08-02). Our goal is to have no ABI changes after beta 4 and as few code changes as possible after 3.11.0rc1, the first release candidate. To achieve that, it will be **extremely important** to get as much exposure for 3.11 as possible during the beta phase. Please keep in mind that this is a preview release and its use is **not** recommended for production environments. # Major new features of the 3.11 series, compared to 3.10 Python 3.11 is still in development. This release, 3.11.0b1 is the **first** of four beta releases. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. Many new features for Python 3.11 are still being planned and written. Among the new major new features and changes so far: * [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include Fine-Grained Error Locations in Tracebacks * [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups and except* * [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type * [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics * [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support for Parsing TOML in the Standard Library * [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal String Type * [PEP 655](https://www.python.org/dev/peps/pep-0655/)-- Marking individual TypedDict items as required or potentially-missing * [bpo-46752](https://bugs.python.org/issue46752)-- Introduce task groups to asyncio * The Faster Cpython Project <https://github.com/faster-cpython> is already yielding some exciting results. Python 3.11 is up to 10-60% faster than Python 3.10. On average, we measured a 1.22x speedup on the standard benchmark suite. See Faster CPython <https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython>for details. * Hey, **fellow core developer,** if a feature you find important is missing from this list, let me know. The next pre-release of Python 3.11 will be 3.11.0b2, currently scheduled for Monday, 2022-05-30. # More resources * [Online Documentation](https://docs.python.org/3.11/) * [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release Schedule * Report bugs at [https://bugs.python.org](https://bugs.python.org). * [Help fund Python and its community](/psf/donations/). # And now for something completely different The holographic principle is a tenet of string theories and a supposed property of quantum gravity that states that the description of a volume of space can be thought of as encoded on a lower-dimensional boundary to the region—such as a light-like boundary like a gravitational horizon. First proposed by Gerard 't Hooft, it was given a precise string-theory interpretation by Leonard Susskind, who combined his ideas with previous ones of 't Hooft and Charles Thorn.[ Leonard Susskind said, “The three-dimensional world of ordinary experience––the universe filled with galaxies, stars, planets, houses, boulders, and people––is a hologram, an image of reality cited on a distant two-dimensional (2D) surface." As pointed out by Raphael Bousso, Thorn observed in 1978 that string theory admits a lower-dimensional description in which gravity emerges from it in what would now be called a holographic way. The holographic principle was inspired by black hole thermodynamics, which conjectures that the maximal entropy in any region scales with the radius squared, and not cubed as might be expected. In the case of a black hole, the insight was that the informational content of all the objects that have fallen into the hole might be entirely contained in surface fluctuations of the event horizon. The holographic principle resolves the black hole information paradox within the framework of string theory. However, there exist classical solutions to the Einstein equations that allow values
[RELEASE] The last Python 3.11 alpha (3.11.0a7) is available - Prepare for beta freeze
Br. do you feel that? That's the chill of *beta freeze* coming closer. Meanwhile, your friendly CPython release team doesn’t rest and we have prepared a shiny new release for you: Python 3.11.0a7. Dear fellow core developer: This alpha is the last release before feature freeze (Friday, 2022-05-06), so make sure that all new features and PEPs are landed in the master branch before we release the first beta. Please, be specially mindfully to check the CI and the buildbots, maybe even using the test-with-buildbots label in GitHub before merging so the release team don’t need to fix a bunch of reference leaks or platform-specific problems on the first beta release. *Go get the new alpha here:* https://www.python.org/downloads/release/python-3110a7/ **This is an early developer preview of Python 3.11** # Major new features of the 3.11 series, compared to 3.10 Python 3.11 is still in development. This release, 3.11.0a7 is the last of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2022-05-06) and, if necessary, may be modified or deleted up until the release candidate phase (2022-08-01). Please keep in mind that this is a preview release and its use is **not** recommended for production environments. Many new features for Python 3.11 are still being planned and written. Among the new major new features and changes so far: * [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include Fine-Grained Error Locations in Tracebacks * [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups and except* * [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type * [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics * [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support for Parsing TOML in the Standard Library * [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal String Type * [PEP 655](https://www.python.org/dev/peps/pep-0655/)-- Marking individual TypedDict items as required or potentially-missing * [bpo-46752](https://bugs.python.org/issue46752)-- Introduce task groups to asyncio * The [Faster Cpython Project](https://github.com/faster-cpython) is already yielding some exciting results: this version of CPython 3.11 is ~12% faster on the geometric mean of the [PyPerformance benchmarks]( speed.python.org), compared to 3.10.0. * Hey, **fellow core developer,** if a feature you find important is missing from this list, let me know. The next pre-release of Python 3.11 will be 3.11.0b1, currently scheduled for Friday, 2022-05-06. # More resources * [Online Documentation](https://docs.python.org/3.11/) * [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release Schedule * Report bugs at [https://bugs.python.org](https://bugs.python.org). * [Help fund Python and its community](/psf/donations/). # And now for something completely different In mathematics, the Dirac delta distribution (δ distribution) is a generalized function or distribution over the real numbers, whose value is zero everywhere except at zero, and whose integral over the entire real line is equal to one. The current understanding of the impulse is as a linear functional that maps every continuous function to its value at zero. The delta function was introduced by physicist Paul Dirac as a tool for the normalization of state vectors. It also has uses in probability theory and signal processing. Its validity was disputed until Laurent Schwartz developed the theory of distributions where it is defined as a linear form acting on functions. Defining this distribution as a "function" as many physicist do is known to be one of the easier ways to annoy mathematicians :) # We hope you enjoy those new releases! Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. Your friendly release team, Pablo Galindo @pablogsal Ned Deily @nad Steve Dower @steve.dower -- https://mail.python.org/mailman/listinfo/python-list
