🌐 Mailman 3 August 2023 - Python-list - python.org

problems installing Python 3.11
by Bernd Lentes Aug. 10, 2023

Aug. 10, 2023

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.lentes(a)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

1 0

Imports and dot-notation
by Oliver Schinagl Aug. 10, 2023

Aug. 10, 2023

Dear list, First a disclaimer, I am a python novice ;) so apologies beforehand for any incorrect terms and use thereof :) I have a question about the preferred/pythonic way dealing with imports. But let me start by giving a little bit of an example (which lead me to this question). Looking at a python projects code and repository layout, we see the following directory structure. /project/core /project/components/module1 ... /project/components/moduleN /projects/util (this is far from complete, but enough to help paint a picture. Some modules import other modules, and I see (at the very least) two (kind of three?) different ways of doing so. `from project.components.module1 import function1, function2 as func, CONST1, CONST2 as CONST` or maybe even (which has as an advantage that it becomes clear which namespace something belongs to `from project.components.module1 import function1, function2 as module1_function2, CONST1, CONST2 as MODULE1_CONST2` but then it really just becomes personal preference, as the number of characters saved on typing is almost negative (due to having a more complex import). but also the dot notation being used `from project.components import module1` where obviously the functions are invoked as `module1.function1` etc I hope the above is clear enough from an example. Simply put, which of the two would be considered cleaner and more pythonic? Now for a bit more thought, looking at PEP8, we notes about imports, but sadly PEP8 does not state which method is better/preferred. While obviously in the end, it's always the maintainers choice in what they prefer, so are tabs vs spaces and PEP8 is opinionated about that too (in a good way, even though I'm not a fan :p). Likewise, if we look at PEP20, there's quite a few 'guidelines' that suggest the dot-notation. To name a few (opinionated) examples (but note I am just using PEP20 as a helper to give some arguments, I know some people feel strongly against pep20 :p): * Beautiful is better than ugly. - Personally, I think the dot notation is more beautiful, but I understand that some people find the short notation more beautiful and less of an eye sore ;) * Explicit is better than implicit. - To me, this is a strong point. Being more explicit is always better, using the dot notation (if though it's not doing the WHOLE path) is a nice balance in being explicit enough. Code readability comes from being more explicit (without being to terse of course). * Simple is better than complex. * Flat is better than nested. - I think having more flat and simple imports, and (while more characters to potentially type in the invocation) more readable invocations would be better? * Readability counts. - The dot notation seems to help in readability. For those unfamiliar (or less familiar) with a code base, it becomes incredibly clear where a something comes from (WITHOUT having to rely on IDE's; sure you can hover over something and see that the IDE has hopefully worked out where something came from, but this doesn't work when just reading a page of code, you aren't going to hover over everything and remember all that context). * In the face of ambiguity, refuse the temptation to guess. - I'd argue this is almost self-explanatory, not using dot-notation makes it more ambiguous where something is coming from. * There should be one-- and preferably only one --obvious way to do it. - This is where my confusion/question obviously comes from, as there's multiple ways of doing it, so maybe PEP8 (or a new one) should more strongly favor one? * Namespaces are one honking great idea -- let's do more of those! - Basically, this question/proposal would 'force/nudge' you into writing more with namespaces by using the namespace as prefix. So what IS the preferred/more pythonic/recommended way to deal with imports? Why was this not mentioned in PEP8? Is it worth while to introduce a new PEP or amend PEP8? For what it's worth, hallucinating chatgpt/google bard both say the same about this topic, that within the python community, it is generally preferred and a good idea to use dot-notation. But how correct are they lol. Thank you for reading, Olliver

4 3

SQLObject 3.10.2
by Oleg Broytman Aug. 9, 2023

Aug. 9, 2023

Hello! I'm pleased to announce version 3.10.2, a minor feature release and the second bugfix release of branch 3.10 of SQLObject. What's new in SQLObject ======================= The contributor for this release is Igor Yudytskiy. Thanks! Minor features -------------- * Class ``Alias`` grows a method ``.select()`` to match ``SQLObject.select()``. Bug fixes --------- * Fixed a bug in ``SQLRelatedJoin`` in the case where the table joins with itself; in the resulting SQL two instances of the table must use different aliases. Thanks to Igor Yudytskiy for providing an elaborated bug report. For a more complete list, please see the news: http://sqlobject.org/News.html What is SQLObject ================= SQLObject is a free and open-source (LGPL) Python object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL/MariaDB (with a number of DB API drivers: ``MySQLdb``, ``mysqlclient``, ``mysql-connector``, ``PyMySQL``, ``mariadb``), PostgreSQL (``psycopg2``, ``PyGreSQL``, partially ``pg8000`` and ``py-postgresql``), SQLite (builtin ``sqlite``, ``pysqlite``, partially ``supersqlite``); connections to other backends - Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB) - are less debugged). Python 2.7 or 3.4+ is required. Where is SQLObject ================== Site: http://sqlobject.org Download: https://pypi.org/project/SQLObject/3.10.2a0.dev20221222/ News and changes: http://sqlobject.org/News.html StackOverflow: https://stackoverflow.com/questions/tagged/sqlobject Mailing lists: https://sourceforge.net/p/sqlobject/mailman/ Development: http://sqlobject.org/devel/ Developer Guide: http://sqlobject.org/DeveloperGuide.html Example ======= Install:: $ pip install sqlobject Create a simple class that wraps a table:: >>> from sqlobject import * >>> >>> sqlhub.processConnection = connectionForURI('sqlite:/:memory:') >>> >>> class Person(SQLObject): ... fname = StringCol() ... mi = StringCol(length=1, default=None) ... lname = StringCol() ... >>> Person.createTable() Use the object:: >>> p = Person(fname="John", lname="Doe") >>> p <Person 1 fname='John' mi=None lname='Doe'> >>> p.fname 'John' >>> p.mi = 'Q' >>> p2 = Person.get(1) >>> p2 <Person 1 fname='John' mi='Q' lname='Doe'> >>> p is p2 True Queries:: >>> p3 = Person.selectBy(lname="Doe")[0] >>> p3 <Person 1 fname='John' mi='Q' lname='Doe'> >>> pc = Person.select(Person.q.lname=="Doe").count() >>> pc 1 Oleg. -- Oleg Broytman https://phdru.name/ phd(a)phdru.name Programmers don't die, they just GOSUB without RETURN.

1 0

zoneinfo and tzdata
by Mike Dewhirst Aug. 9, 2023

Aug. 9, 2023

The zoneinfo module does not work on Windows unless you have installed tzdata. On Ubuntu that data seems to exist already. Not sure how or why but it obviously isn't there in a Windows virtualenv unless deliberately installed. I just spent a bit of time trying to switch from pytz to zoneinfo in Django without luck. I then asked and greatly embarrassed ChatGPT which kept apologizing when I fed back all the zoneinfo errors its advice caused. It wasn't until I read the docs that I saw zoneinfo would get timezone data from tzdata if the real info wasn't where it first looked. As soon as I installed tzdata, ChatGPT's advice started to work. When I reported this, it was very grateful and assured me my generosity in bothering to correct it would be very beneficial for other users having similar problems. Might I suggest that if zoneinfo comes up empty-handed it should raise an error saying no timezone information was found? Currently, it just nominates the timezone key you attempt to use. Behind the scenes it surely knows there are no such keys. In that case it might suggest installing tzdata. Cheers Mike

1 0

Mtg ANN: Using computer vision AI to help protect the worlds rarest dolphin
by dn Aug. 8, 2023

Aug. 8, 2023

Wed 16 Aug 2023, 1800~20:30 NZST (0600~0830 UTC, late-Tue in US) Details and RSVP at https://www.meetup.com/nzpug-auckland/events/295091858/ Teaching a computer to see. How computer vision is helping to protect the world’s rarest dolphin and how you can train your own model. Tane van der Boon will talk about the MAUI63 project, and then lead us through how to train and utilise a custom computer vision object detector. Essentially allowing our software to be able to see. MAUI63 was given its name because when the venture began, there were only 63 Māui dolphins left in existence. Using drone technology and AI to collect and process visual data, the founders took action to collect data to help save the world’s rarest dolphin from extinction and influence future marine conservation efforts. The MAUI63 team uses a customised drone to find and track the movement of dolphins, and enables individual dolphins to be identified through their fin markings. The information collected can then be used to inform better data driven decisions on how best to protect them. Later, Tane will lead us through a smaller task to build our own image recognizer. (more details in due course...) The Auckland Branch of the New Zealand Python Users' Group meet twice monthly. You're very welcome to attend online or in-person (as available). Meeting location-details or URL will be sent to those who RSVP. We are a healthy mix of Python users. Students, academics, hobbyists, industry professionals, and many completely new to Python. The "room" opens at 1800 (local time) with an opportunity to network with colleagues. Everything should be wrapped up by 2030. We are always keen to hear suggestions for meeting-topics, and to meet with folk who'd like to present or lead - eg a brief lightning talk, a practical coaching-session, a full lecture... Help is available if you've never done such a thing before! We follow the NZPUG Code of Conduct (https://python.nz/code-of-conduct) to create an inclusive and friendly environment. We express thanks to, and encourage you to investigate, our sponsors: Catalyst Cloud, New Zealand Open Source Society, JetBrains, and IceHouse Ventures. -- Regards =dn -- Regards, =dn

1 0

Cheetah 3.3.2
by Oleg Broytman Aug. 8, 2023

Aug. 8, 2023

Hello! I'm pleased to announce version 3.3.2, the 2nd bug-fix of branch 3.3 of CheetahTemplate3. What's new in CheetahTemplate3 ============================== The contributor for this release is nate.k. Thanks! Bug fixes: - Fixed printing to stdout in ``CheetahWrapper``. CI: - CI(GHActions): Install all Python and PyPy versions from ``conda-forge``. What is CheetahTemplate3 ======================== Cheetah3 is a free and open source (MIT) Python template engine. It's a fork of the original CheetahTemplate library. Python 2.7 or 3.4+ is required. Where is CheetahTemplate3 ========================= Site: https://cheetahtemplate.org/ Download: https://pypi.org/project/CT3/3.3.2 News and changes: https://cheetahtemplate.org/news.html StackOverflow: https://stackoverflow.com/questions/tagged/cheetah Mailing lists: https://sourceforge.net/p/cheetahtemplate/mailman/ Development: https://github.com/CheetahTemplate3 Developer Guide: https://cheetahtemplate.org/dev_guide/ Example ======= Install:: $ pip install CT3 # (or even "ct3") Below is a simple example of some Cheetah code, as you can see it's practically Python. You can import, inherit and define methods just like in a regular Python module, since that's what your Cheetah templates are compiled to :) :: #from Cheetah.Template import Template #extends Template #set $people = [{'name' : 'Tom', 'mood' : 'Happy'}, {'name' : 'Dick', 'mood' : 'Sad'}, {'name' : 'Harry', 'mood' : 'Hairy'}] <strong>How are you feeling?</strong> <ul> #for $person in $people <li> $person['name'] is $person['mood'] </li> #end for </ul> Oleg. -- Oleg Broytman https://phdru.name/ phd(a)phdru.name Programmers don't die, they just GOSUB without RETURN.

1 0

Where is the error?
by Peter J. Holzer Aug. 6, 2023

Aug. 6, 2023

Mostly, error messages got a lot better in Python 3.10, but this one had me scratching my head for a few minutes. Consider this useless and faulty script: ------------------------------------------------------------------------ r = { "x": (1 + 2 + 3) "y": (4 + 5 + 6) "z": (7 + 8 + 9) } ------------------------------------------------------------------------ Python 3.9 (and earlier) reports: ------------------------------------------------------------------------ File "/home/hjp/tmp/foo", line 3 "y": (4 + 5 + 6) ^ SyntaxError: invalid syntax ------------------------------------------------------------------------ This isn't great, but experience with lots of programming languages tells me that an error is noticed where or after it actually occurs, so it's easy to see that there is a comma missing just before the "y". Python 3.10 and 3.11 report: ------------------------------------------------------------------------ File "/home/hjp/tmp/foo", line 2 "x": (1 + 2 + 3) ^^^^^^^^^^ SyntaxError: invalid syntax. Perhaps you forgot a comma? ------------------------------------------------------------------------ The error message is now a lot better, of course, but the fact that it points at the expression *before* the error completely threw me. The underlined expression is clearly not missing a comma, nor is there an error before that. My real program was a bit longer of course, so I checked the lines before that to see if I forgot to close any parentheses. Took me some time to notice the missing comma *after* the underlined expression. Is this "clairvoyant" behaviour a side-effect of the new parser or was that a deliberate decision? hp -- _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp(a)hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!"

5 5

[RELEASE] Python 3.12.0 release candidate 1 released
by Thomas Wouters Aug. 6, 2023

Aug. 6, 2023

I'm pleased to announce the release of Python 3.12.0rc1: https://www.python.org/downloads/release/python-3120rc1/ This is the first release candidate of Python 3.12.0 This release, *3.12.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 scheduled for Monday, 2023-09-04, while the official release of 3.12.0 is scheduled for Monday, 2023-10-02. There will be *no ABI changes* from this point forward in the 3.12 series, and the goal is that there will be as few code changes as possible. <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…>Call to action We strongly encourage maintainers of third-party Python projects to prepare their projects for 3.12 compatibilities during this phase, and where necessary publish Python 3.12 wheels on PyPI to be ready for the final release of 3.12.0. Any binary wheels built against Python 3.12.0rc1 will work with future versions of Python 3.12. As always, report any issues to the Python bug tracker <https://github.com/python/cpython/issues>. Please keep in mind that this is a preview release and while it’s as close to the final release as we can get it, its use is *not* recommended for production environments. <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…>Core developers: time to work on documentation now - Are all your changes properly documented? - Are they mentioned in What’s New <https://docs.python.org/3.12/whatsnew/3.12.html>? - Did you notice other changes you know of to have insufficient documentation? <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…>Major new features of the 3.12 series, compared to 3.11 <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…>New features - More flexible f-string parsing <https://docs.python.org/3.12/whatsnew/3.12.html#pep-701-syntactic-formaliza…>, allowing many things previously disallowed (PEP 701 <https://peps.python.org/pep-0701/>). - Support for the buffer protocol <https://docs.python.org/3.12/whatsnew/3.12.html#pep-688-making-the-buffer-p…> in Python code (PEP 688 <https://peps.python.org/pep-0688/>). - A new debugging/profiling API (PEP 669 <https://peps.python.org/pep-0669/>). - Support for isolated subinterpreters <https://docs.python.org/3.12/whatsnew/3.12.html#pep-684-a-per-interpreter-g…> with separate Global Interpreter Locks (PEP 684 <https://peps.python.org/pep-0684>). - Even more improved error messages <https://docs.python.org/3.12/whatsnew/3.12.html#improved-error-messages>. More exceptions potentially caused by typos now make suggestions to the user. - Support for the Linux perf profiler <https://docs.python.org/3.12/howto/perf_profiling.html> to report Python function names in traces. - Many large and small performance improvements <https://docs.python.org/3.12/whatsnew/3.12.html#optimizations> (like PEP 709 <https://peps.python.org/pep-0709/>), delivering an estimated 5% overall performance improvementcitation needed. <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…>Type annotations - New type annotation syntax <https://docs.python.org/3.12/whatsnew/3.12.html#pep-695-type-parameter-synt…> for generic classes (PEP 695 <https://peps.python.org/pep-0695/>). - New override decorator <https://docs.python.org/3.12/whatsnew/3.12.html#pep-698-override-decorator-…> for methods (PEP 698 <https://peps.python.org/pep-0698>). <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…> Deprecations - The deprecated wstr and wstr_length members of the C implementation of unicode objects were removed, per PEP 623 <https://peps.python.org/pep-0623/>. - In the unittest module, a number of long deprecated methods and classes were removed. (They had been deprecated since Python 3.1 or 3.2). - The deprecated smtpd and distutils modules have been removed (see PEP 594 <https://peps.python.org/pep-0594/> and PEP 632 <https://peps.python.org/pep-0632/>. The setuptools package continues to provide the distutils module. - A number of other old, broken and deprecated functions, classes and methods <https://docs.python.org/3.12/whatsnew/3.12.html#removed> have been removed. - Invalid backslash escape sequences in strings now warn with SyntaxWarning instead of DeprecationWarning, making them more visible. (They will become syntax errors in the future.) - The internal representation of integers has changed in preparation for performance enhancements. (This should not affect most users as it is an internal detail, but it may cause problems for Cython-generated code.) (Hey, *fellow core developer,* if a feature you find important is missing from this list, let Thomas know <thomas(a)python.org>.) For more details on the changes to Python 3.12, see What’s new in Python 3.12 <https://docs.python.org/dev/whatsnew/3.12.html>. The next pre-release of Python 3.12 will be 3.12.0rc2, the *final release candidate*, currently scheduled for 2023-09-04. <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…>More resources - Online Documentation <https://docs.python.org/3.12/>. - PEP 693 <https://www.python.org/dev/peps/pep-0693/>, the Python 3.12 Release Schedule. - Report bugs via GitHub Issues <https://github.com/python/cpython/issues>. - Help fund Python and its community <https://www.python.org/psf/donations/>. <https://discuss.python.org/t/python-3-12-0-release-candidate-1-released/311…>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-landing/>. Your release team, Thomas Wouters Ned Deily Steve Dower Łukasz Langa -- Thomas Wouters <thomas(a)python.org>

1 0

Re: isinstance()
by Jon Ribbens Aug. 5, 2023

Aug. 5, 2023

On 2023-08-02, dn <PythonList(a)DancesWithMice.info> wrote: > Can you please explain why a multi-part second-argument must be a tuple > and not any other form of collection-type? The following comment may hold a clue: if (PyTuple_Check(cls)) { /* Not a general sequence -- that opens up the road to recursion and stack overflow. */ https://github.com/python/cpython/blob/main/Objects/abstract.c#L2684 Plus an almost total lack of demand for change I should think.

4 5

How to find the full class name for a frame
by Jason Friedman Aug. 4, 2023

Aug. 4, 2023

import inspect def my_example(arg1, arg2): print(inspect.stack()[0][3]) my_frame = inspect.currentframe() args,_,_,values = inspect.getargvalues(my_frame) args_rendered = [f"{x}: {values[x]}" for x in args] print(args_rendered) my_example("a", 1) The above "works" in the sense it prints what I want, namely the method name (my_example) and the arguments it was called with. My question is: let's say I wanted to add a type hint for my_frame. my_frame: some_class_name = inspect.currentframe() What would I put for some_class_name? "frame" (without quotations) is not recognized, Nor is inspect.frame.

3 4