Python-announce-list

python-announce-list@python.org

9 participants
12448 discussions

EuroPython 2020: Live Stream Recordings available

by M.-A. Lemburg

We’re happy to announce the public availability of the live stream recordings from EuroPython 2020. They were already available to all conference attendees since the sprint days. * EuroPython YouTube Channel * http://europython.tv/ We have collected the videos in a EuroPython 2020 Live Stream playlist: https://www.youtube.com/playlist?list=PL8uoeex94UhG33fVP7GZEo06gOHlhb0hk Unedited Videos --------------- What we are releasing today are unedited videos recorded for the main track rooms and days. The poster track recordings will be added today or tomorrow. You can use the schedule to navigate the videos. Linking to a specific time in the videos can be done by right-clicking in the video to create a URL which points to the current position. Feel free to share interesting links on social media. Edited Videos ------------- Our video editing company is already busy creating the cut videos. Those should be ready in a month or two. Help spread the word -------------------- Please help us spread this message by sharing it on your social networks as widely as possible. Thank you ! Link to the blog post: https://blog.europython.eu/post/626322517228961792/europython-2020-live-str… Tweet: https://twitter.com/europython/status/1293828734143864833 Thanks, -- EuroPython 2020 Team https://ep2020.europython.eu/ https://www.europython-society.org/

2 days, 7 hours

[RELEASE] Python 3.9.0rc1 is now available

by Łukasz Langa

Python 3.9.0 is *almost* ready. This release, *3.9.0rc1*, is the penultimate release preview. You can get it here: https://www.python.org/downloads/release/python-390rc1/ 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 2020-09-14. Please keep in mind that this is a preview release and its use is *not* recommended for production environments. Calls 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.9 compatibility during this phase. As always, report any issues to the Python bug tracker <https://bugs.python.org/>. Installer news This is the first version of Python to default to the 64-bit installer on Windows. The installer now also actively disallows installation on Windows 7. Python 3.9 is incompatible with this unsupported version of Windows. Major new features of the 3.9 series, compared to 3.8 Some of the new major new features and changes in Python 3.9 are: * PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in `dict` * PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In Standard Collections * PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and variable annotations * PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable annual release cadence * PEP 615 <https://www.python.org/dev/peps/pep-0615/>, Support for the IANA Time Zone Database in the Standard Library * PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove prefixes and suffixes * PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython * BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not block on resurrected objects; * BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows process management without races and signals; * BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to version 13.0.0; * BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized multiple times in the same process, it does not leak memory anymore; * A number of Python builtins (range, tuple, set, frozenset, list, dict) are now sped up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall; * A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, _functools, _json, _locale, operator, resource, time, _weakref) now use multiphase initialization as defined by PEP 489 <https://www.python.org/dev/peps/pep-0489/>; * A number of standard library modules (audioop, ast, grp, _hashlib, pwd, _posixsubprocess, random, select, struct, termios, zlib) are now using the stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.

3 days, 23 hours

Vulture 2.0

by Jendrik Seipp

Vulture - Find dead code ======================== Vulture finds unused code in Python programs. This is useful for cleaning up and finding errors in large code bases. If you run Vulture on both your library and test suite you can find untested code. Due to Python's dynamic nature, static code analyzers like Vulture are likely to miss some dead code. Also, code that is only called implicitly may be reported as unused. Nonetheless, Vulture can be a very helpful tool for higher code quality. Download ======== https://github.com/jendrikseipp/vulture http://pypi.python.org/pypi/vulture Features ======== * fast: uses static code analysis * tested: tests itself and has complete test coverage * complements pyflakes and has the same output syntax * sorts unused classes and functions by size with ``--sort-by-size`` * supports Python Python 3.6+ News ==== * Parse `# type: ...` comments if on Python 3.8+ (jingw, #220). * Bump minimum Python version to 3.6 (Jendrik Seipp, #218). The last Vulture release that supports Python 2.7 and Python 3.5 is version 1.6. * Consider all files under `test` or `tests` directories test files (Jendrik Seipp). * Ignore `logging.Logger.propagate` attribute (Jendrik Seipp). Cheers Jendrik

3 days, 23 hours

Webinar and training about pytest basics (German / Switzerland)

by Florian Bruhin

Hey, (Back in June, I've sent a mail about a pytest workshop I'm giving in September. I'm not sure if it made it through everywhere, as I accidentally used a mail address which wasn't subscribed to the lists I was posting to. Since I also have a second announcement to make, I'm taking the freedom to post another "marketing" mail - after that, things will likely be silent for a while from my side again!) Webinar ------- On August 18th (next week, if you read this mail on the same day I'm writing it), I'm giving a 1h webinar about pytest basics in German: https://mylearning.ch/kurse/online-kurse/tech-webinar/ This is in collaboration with the Institute for Networked Solutions (INS) at a local university (Hochschule Rapperswil / HSR), hence the webinar is in German. If you'd be interested in something similar in English, please let me know - if there's enough interest, I'll repeat it in English at a later point in time. Training -------- On September 8th, I teach a full-day pytest training as part of the CH Open "Workshoptage" in Rotkreuz, Switzerland: https://workshoptage.ch/workshops/2020/pytest-test-driven-development-nicht… Of course COVID-19 is still a concern for the physical training - the organizer allows to cancel your ticket (with a full refund) up to two weeks before the training takes place and also closesly monitors the situation in Switzerland. Would be delighted to see some of you there! :) For the webinar, there should also be a recording available later. Florian -- me(a)the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/

4 days, 5 hours

ANN: PythonQwt 0.6.2

by Pierre Raybaut

Hi all, I am pleased to announce that PythonQwt v0.6.2 has been released (https://github.com/PierreRaybaut/PythonQwt). This is a maintenance release, compatible with Python 2.7, 3.4-3.8, PyQt4 and PyQt5. The PythonQwt package is a 2D-data plotting library using Qt graphical user interfaces for the Python programming language. It is compatible with both PyQt4 and PyQt5 (PySide is currently not supported but it could be in the near future). The PythonQwt project was initiated to solve -at least temporarily (at the time...)- the obsolescence issue of PyQwt (the Python-Qwt C++ bindings library) which is no longer maintained. The idea was to translate the original Qwt C++ code to Python and then to optimize some parts of the code by writing new modules based on NumPy and other libraries. The PythonQwt package consists of a single Python package named qwt which is a pure Python implementation of Qwt C++ library with some limitations: efforts were concentrated on basic plotting features, leaving higher level features to the guiqwt library. The PythonQwt documentation with examples, API reference, etc. is available here: https://pythonqwt.readthedocs.io/en/latest/ Python package index page: https://pypi.org/project/PythonQwt/ -- Pierre Raybaut

6 days, 6 hours

[ANN] PyInstaller 4.0

by Hartmut Goebel

Hello, on behalf of the PyInstaller development team I'm happy to announce PyInstaller 4.0. http://www.pyinstaller.org Thanks for all those who contributed questions, bug-reports or pull-requests. PyInstaller is in urgent need of funding to make future security fixes happen, see <https://github.com/pyinstaller/pyinstaller/issues/4404> for details. === Important Changes === Release 4.0 adds support for 3rd-party packages to provide PyInstaller hooks along with the package. This allows Maintainers of other Python packages to deliver up-to-date PyInstaller hooks as part of their package. See our sample project <https://github.com/pyinstaller/hooksample> for more information. PyInstaller uses this option itself to provide updated hooks much faster: Many hooks are moved into the new package pyinstaller-hooks-contrib <https://github.com/pyinstaller/pyinstaller-hooks-contrib>, which is updated monthly. This package is installed automatically when installing PyInstaller, but can also be updated independently. Finally, this version drops support for Python 2.7, which is end-of-life since January 2020.. The minimum required version is now Python 3.5. The last version supporting Python 2.7 was PyInstaller 3.6. The full changelog for this release can be found at: https://pyinstaller.readthedocs.io/en/v4.0/CHANGES.html === What it is === PyInstaller bundles a Python application and all its dependencies into a single package. The user can run the packaged app without installing a Python interpreter or any modules. PyInstaller reads a Python script written by you. It analyzes your code to discover every other module and library your script needs in order to execute. Then it collects copies of all those files – including the active Python interpreter! – and puts them with your script in a single folder, or optionally in a single executable file. PyInstaller is tested against Windows, Mac OS X, and Linux. However, it is not a cross-compiler: to make a Windows app you run PyInstaller in Windows; to make a Linux app you run it in Linux, etc. PyInstaller has been used successfully with AIX, Solaris, and FreeBSD, but is not tested against them. === Help keeping PyInstaller alive === Maintaining PyInstaller is a huge amount of work. PyInstaller development can only continue if users and companies provide sustainable funding. Please consider recurring donations. See http://www.pyinstaller.org/funding.html for how to support PyInstaller. === Installation === PyInstaller can be installed from PyPi using pip install pyinstaller === Important Changes === The full changelog for this release can be found at: https://pyinstaller.readthedocs.io/en/v4.0/CHANGES.html === Feedback === We're eager to listen to your feedback on using PyInstaller: Bug tracker: https://github.com/pyinstaller/pyinstaller/issues Mailing list: http://groups.google.com/group/PyInstaller -- Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: http://www.goebel-consult.de/blog/warum-sie-nicht-perl-programmiern-sollten Kolumne: http://www.cissp-gefluester.de/2012-02-bring-your-own-life-glosse

6 days, 8 hours

ANN: guidata v1.7.7

by Pierre Raybaut

Hi all, I am pleased to announce that `guidata` v1.7.7 has been released (https://github.com/PierreRaybaut/guidata). This is a maintenance release with a couple of bugfixes (compatibility with Spyder v4) -- guidata is compatible with Python 2.7, 3.4-3.8, PyQt4 and PyQt5. Based on the Qt GUI library (PyQt4, PyQt5, and mostly compatible with PySide), guidata is a Python library generating graphical user interfaces for easy dataset editing and display. It also provides helpers and application development tools for PyQt. guidata also provides the following features: * guidata.qthelpers: PyQt helpers * guidata.disthelpers: cx_Freeze/py2exe helpers (or how to build a self-consistent executable in three lines of code!) * guidata.userconfig: .ini configuration management helpers (based on Python standard module ConfigParser) * guidata.configtools: library/application data management * guidata.gettext_helpers: translation helpers (based on the GNU tool gettext) * guidata.guitest: automatic GUI-based test launcher * guidata.utils: miscelleneous utilities guidata has been successfully tested on GNU/Linux and Windows platforms. The `guidata` documentation with examples, API reference, etc. is available here: https://guidata.readthedocs.io/en/latest/ Python package index page: http://pypi.python.org/pypi/guidata/ -- Pierre Raybaut

6 days, 12 hours

Vulture 1.6

by Jendrik Seipp

Vulture - Find dead code ======================== Vulture finds unused code in Python programs. This is useful for cleaning up and finding errors in large code bases. If you run Vulture on both your library and test suite you can find untested code. Due to Python's dynamic nature, static code analyzers like Vulture are likely to miss some dead code. Also, code that is only called implicitly may be reported as unused. Nonetheless, Vulture can be a very helpful tool for higher code quality. Download ======== https://github.com/jendrikseipp/vulture http://pypi.python.org/pypi/vulture Features ======== * fast: uses static code analysis * tested: tests itself and has complete test coverage * complements pyflakes and has the same output syntax * sorts unused classes and functions by size with ``--sort-by-size`` * supports Python 2.7 and Python 3.5+ News ==== * Differentiate between functions and methods (Jendrik Seipp, #112, #209). * Move from Travis to GitHub actions (RJ722, #211). Cheers Jendrik

1 week, 1 day

Announce: openfoodfacts-python 0.1.1 released

by Andrea Stagi

I'm happy to announce that openfoodfacts-python 0.1.1 has been released! https://github.com/openfoodfacts/openfoodfacts-python What is Open Food Facts? Open Food Facts is a database of food products with ingredients, allergens, nutrition facts and all the tidbits of information we can find on product labels. Open Food Facts is a non-profit association of volunteers. 1800+ contributors like you have added 700 000+ products from 150 countries using our Android, iPhone or their camera to scan barcodes and upload pictures of products and their labels. Data about food is of public interest and has to be open. The complete database is published as open data and can be reused by anyone and for any use. Check-out the cool reuses or make your own! More on https://world.openfoodfacts.org -- *Andrea Stagi (@4stagi) - CTO @ Lotrèk* Linkedin: http://linkedin.com/in/andreastagi Blog: https://dev.to/astagi Code: http://github.com/astagi

1 week, 2 days

Released logassert 5

by Facundo Batista

I'm happy to bring you a new release of logassert, a simple logging assertion mechanism for Python unittests. Because we all know that we must test the logging calls in our programs, right? With `logassert` this is very easy. This new release brings the functionality of logassert as a pytest fixture, with totally renewed semantics (for "classic unittest" structures, logassert is not changing much, to be backwards compatibile). So, for pytest all you need to do is to declare `logs` in your test arguments (it works just like any other fixture), and then just check (using `assert`, as usual with *pytest*) if a specific line is in the logs for a specific level. See this example, with several log lines, and a specific assertion: logger.info("Starting system") places = ['/tmp/', '~/temp'] logger.debug("Checking for config XYZ in all these places %s", places) logger.warning("bad config XYZ") assert "bad config XYZ" in logs.debug See how the test failure message is super helpful: assert for regex 'bad config XYZ' check in DEBUG, failed; logged lines: INFO 'Starting system' DEBUG "Checking for config XYZ in all these places ['/tmp/', '~/temp']" WARNING 'bad config XYZ' You can install logassert from PyPI: https://pypi.org/project/logassert/ The project is in Github: https://github.com/facundobatista/logassert Interested on more detail about how this work? As I said above, you include the `logs` fixture and just assert. Example: def test_bleh(logs) (...) assert "The meaning of life is 42" in logs.debug Actually, the line you write is a regular expression, so you can totally do (in case you're not exactly sure which the meaning of life is): assert "The meaning of life is \d+" in logs.debug The indicated string is searched to be inside the log lines, it doesn't need to be exact whole line. If you want that, just indicate it as with any regular expression: assert "^The meaning of life is \d+$" in logs.debug In a similar way you can also express the desire to check if it's at the beginning or at the end of the log lines. **NOTE**: the message checked is the final one, after the logging system replaced all the indicated parameters in the indicated string. If you want to verify that a text was logged, no matter at which level, just do: assert "The meaning of life is 42" in logs.any_level To verify that some text was NOT logged, just juse the Python's syntax! For example: assert "A problem happened" not in logs.error If you don't like regexes just import `Exact` from `logassert` and wrap the string with that. For example, in this case the `..` means exactly two dots, no regex semantics at all: assert Exact("The meaning of life is ..") in logs.any_level If you need help, or have any question, or found any issue, please open a ticket [here](https://github.com/facundobatista/logassert/issues/new). Thanks in advance for your time. -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org.ar/ Twitter: @facundobatista

1 week, 2 days

Jump to page:

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Python-announce-list