Mailman 3 August 2021 - Python-announce-list

[RELEASE] Python 3.9.7 and 3.8.12 are now available
by Łukasz Langa 30 Aug '21

30 Aug '21

Python 3.9.7 Get it here: https://www.python.org/downloads/release/python-397/ <https://www.python.org/downloads/release/python-397/> Python 3.9.7 is the newest major stable release of the Python programming language, and it contains many new features and optimizations. There’s been 187 commits since 3.9.6 which is a similar amount compared to 3.8 at the same stage of the release cycle. See the change log <https://docs.python.org/release/3.9.7/whatsnew/changelog.html> for details. On macOS, we encourage you to use the universal2 binary installer variant whenever possible. The legacy 10.9+ Intel-only variant will not be provided for Python 3.10 and the universal2 variant will become the default download for 3.9.8. You may need to upgrade third-party components, like pip, to later versions. You may experience differences in behavior in IDLE and other Tk-based applications due to using the newer version of Tk. As always, if you encounter problems when using this installer variant, please check https://bugs.python.org <https://bugs.python.org/> for existing reports and for opening new issues. The next Python 3.9 maintenance release will be 3.9.8, currently scheduled for 2021-11-01. <https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#th…>The Second Security-Only Release of Python 3.8 Get it here: https://www.python.org/downloads/release/python-3812/ <https://www.python.org/downloads/release/python-3812/> Security content in this release contains four fixes. There are also four additional fixes for bugs that might have lead to denial-of-service attacks. Finally, while we’re not providing binary installers anymore, for those users who produce installers, we upgraded the OpenSSL version used to 1.1.1l. Take a look at the change log <https://docs.python.org/release/3.8.12/whatsnew/changelog.html> for details. According to the release calendar specified in PEP 569 <https://www.python.org/dev/peps/pep-0569/>, Python 3.8 is now in “security fixes only” stage of its life cycle: 3.8 branch only accepts security fixes and releases of those are made irregularly in source-only form until October 2024. Python 3.8 isn’t receiving regular bug fixes anymore, and binary installers are no longer provided for it. Python 3.8.10 was the last full bugfix release of Python 3.8 with binary installers. <https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#se…>Security releases of 3.7.12 and 3.6.15 Those aren’t ready just yet but are soon to follow. Similarly to 3.8, Python 3.7 and 3.6 are now in “security fixes only” stage of their life cycle. Python 3.7 will be providing source archives until June 2023 while Python 3.6 ends its life in December 2021. <https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#we…>We hope you enjoy the new releases Your friendly release team, Ned Deily @nad <https://discuss.python.org/u/nad> Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower> Łukasz Langa @ambv <https://discuss.python.org/u/ambv>

1 0

[Python-announce]pytest 6.2.5
by Bruno Oliveira 30 Aug '21

30 Aug '21

pytest 6.2.5 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/stable/changelog.html. Thanks to all of the contributors to this release: * Anthony Sottile * Bruno Oliveira * Brylie Christopher Oxley * Daniel Asztalos * Florian Bruhin * Jason Haugen * MapleCCC * Michał Górny * Miro Hrončok * Ran Benita * Ronny Pfannschmidt * Sylvain Bellemare * Thomas Güttler Happy testing, The pytest Development Team

1 0

[Python-announce]argon2-cffi 21.1.0
by Hynek Schlawack 29 Aug '21

29 Aug '21

Hi everyone, I’m happy to announce the release of argon2-cffi 21.1.0! With more than 13 million downloads per month, argon2-cffi is the most popular package for using the competition-winning Argon2 password hash in Python. If you want more details on Argon2 and why it matters, check out my blog post "Storing Passwords in a Highly Parallelized World" <https://hynek.me/articles/storing-passwords/>. Heartfelt thanks go to my generous GitHub sponsors <https://github.com/sponsors/hynek>, companies subscribing on Tidelift <https://tidelift.com/subscription/pkg/pypi-argon2-cffi> (currently nobody :( – tell your boss!), and people who bought me a coffee on <https://ko-fi.com/the_hynek>! Support like that makes me work on FOSS on a Sunday afternoon, so please consider supporting me <https://hynek.me/say-thanks/> too! <3 The highlights of this release are: - abi3-wheels for all platforms. This means that argon2-cffi is ready for Python 3.10! - Good bye Python 2. --- All Changes: ============ Vendoring Argon2 @ 62358ba (20190702) Backward-incompatible changes: Microsoft stopped providing the necessary SDKs to ship Python 2.7 wheels and currenly the downloads amount to 0.09%. Therefore we have decided that Python 2.7 is not supported anymore. Deprecations: none Changes: There are indeed no changes whatsoever to the code of argon2-cffi. The Argon2 project also hasn't tagged a new release since July 2019. There also don't seem to be any important pending fixes. This release is mainly about improving the way binary wheels are built (abi3 on all platforms).

1 0

[Python-announce]Announcing PyData/Sparse 0.13.0
by Hameer Abbasi 28 Aug '21

28 Aug '21

Hello everyone. I’m happy to announce version 0.13.0 of PyData/Sparse. PyData/Sparse provides sparse arrays for the PyData ecosystem: It mimics the NumPy API but provides sparse storage. Version 0.13.0 was mainly a bugfix-centred release, fixing many bugs and regressions reported by users for versions 0.12.0 and 0.11.0. Python 3.6 was dropped for this release, and version 3.9 support was formally added. Some minor features were also added. Source Code: https://github.com/pydata/sparse/tree/0.13.0 <https://github.com/pydata/sparse/tree/0.13.0> Documentation: https://sparse.pydata.org/en/0.13.0/ <https://sparse.pydata.org/en/0.13.0/> Changelog: https://sparse.pydata.org/en/0.13.0/changelog.html <https://sparse.pydata.org/en/0.13.0/changelog.html> Best regards, Hameer Abbasi

1 0

[Python-announce]PyCA cryptography 3.4.8 released
by Paul Kehrer 24 Aug '21

24 Aug '21

PyCA cryptography 3.4.8 has been released to PyPI. cryptography includes both high level recipes and low level interfaces to common cryptographic algorithms such as symmetric ciphers, asymmetric algorithms, message digests, X509, key derivation functions, and much more. We support Python 3.6+, and PyPy3. Changelog (https://cryptography.io/en/latest/changelog.html#v3-4-8): * Updated Windows, macOS, and manylinux wheels to be compiled with OpenSSL 1.1.1l. -Paul Kehrer (reaperhulk)

1 0

[Python-announce]ANN: Astropy v4.3 and v4.0.6 released
by Erik Tollerud 24 Aug '21

24 Aug '21

Dear colleagues, We are very happy to announce the v4.3 release of the Astropy package, a core Python package for Astronomy: http://www.astropy.org Astropy is a community-driven Python package intended to contain much of the core functionality and common tools needed for astronomy and astrophysics. It is part of the Astropy Project, which aims to foster an ecosystem of interoperable astronomy packages for Python. New and improved major functionality in this release includes: * Transformations to AltAz are now much more precise (and faster) * Improvements in making Astropy thread-safe * Performance improvements to sigma clipping * Changes in the Time and IERS leap second handling * Support for multidimensional and object columns in ECSV * Support for reading and writing tables to QDP format * Append table to existing FITS file * General masked class for Quantity and other ndarray subclasses * Configuration file improvements * Support for different solvers and bracket option in z_at_value In addition, hundreds of smaller improvements and fixes have been made. An overview of the changes is provided at: http://docs.astropy.org/en/stable/whatsnew/4.3.html Instructions for installing Astropy are provided on our website, and extensive documentation can be found at: http://docs.astropy.org If you usually use pip/vanilla Python, you can do: pip install astropy --upgrade Note that this will yield astropy v4.3.1 instead of 4.3, which is expected - a significant bug reported between the 4.3 release and this announcement means that the correct version is indeed 4.3.1. If you make use of the Anaconda Python Distribution, soon you will be able update to Astropy v4.3.1 with: conda update astropy Or if you cannot wait for Anaconda to update their default version, you can use the conda-forge channel: conda update -c conda-forge astropy Please report any issues, or request new features via our GitHub repository: https://github.com/astropy/astropy/issues Over 400 people have contributed code to Astropy so far, and you can find out more about the team behind Astropy here: https://www.astropy.org/team.html The LTS (Long Term Support) version of Astropy at the time of v4.3's release is v4.0 - this version will be maintained until the next LTS release (v5.0, scheduled for Fall 2021). v4.0.6 is the latest version, also just released. Additionally, note that the Astropy 4.x series only supports Python 3. Python 2 users can continue to use the 2.x series but it is no longer supported (as Python 2 itself is no longer supported). For assistance converting Python 2 code to Python 3, see the Python 3 for scientists conversion guide. If you use Astropy directly for your work, or as a dependency to another package, please remember to acknowledge it by citing the appropriate Astropy paper. For the most up-to-date suggestions, see the acknowledgement page, but as of this release the recommendation is: This research made use of Astropy, a community-developed core Python package for Astronomy (Astropy Collaboration, 2013, 2018). We hope that you enjoy using Astropy as much as we enjoyed developing it! Erik Tollerud v4.3 Release Coordinator on behalf of The Astropy Project https://www.astropy.org/announcements/release-4.3.html

1 0

[Python-announce]Pygame 2.0.2.dev2 - Drumroll release
by René Dudfield 22 Aug '21

22 Aug '21

💐💐😉😊💐💐 ☕ Cheer Up! 🍵 🍂 ✨ )) ✨ 🍂 🍂┃ (( * ┣┓ 🍂 we have a python3 -m pip install pygame==2.0.2.dev2 🍂┃*💗 ┣┛ 🍂 🍂┗━━┛ 🍂 🎂 For YOU 🍰 💐💐😌😊💐💐 Hello internet strangers. We’re back with a new release, packed with tons of mundane bug fixes and unexciting improvements! It’s been a while since the last release, but in that time pygame development has been moving ahead. This release, 36 contributors (25 new ones!) contributed over 75 pull requests. Since 2.0.1, over 200 files were edited, with more than 16,000 lines added, and more than 7,000 lines deleted. This is a development pre-release, so we can test out new release machinery. Probably we will do a couple more dev pre-releases, but we hope to have a full 2.0.2 release soon. There's a bunch of PRs still open that we want to help resolve and merge in before that. So grab a beverage, and doom scroll our release notes, we prepared just for you, (&& those other interweb weirdos) Bug Fixes 🐛 Artisanal source code like ours has the best intentions, but there's nothing like computers to bamboozle our best efforts. It used to be actual bugs climbing inside the pipe organs programmed to play and the looms programmed to weave, but these days that excuse doesn't really work. Our bad. <https://camo.githubusercontent.com/2dee2c6c9f12fe8eda3e8f1652931750d4a00bf4…> *Bugs in this 1910 Jacquard loom would be actual bugs* New contributor @mhollands <https://github.com/mhollands> fixed an issue where arcs wouldn’t fully draw in #2480 <https://github.com/pygame/pygame/pull/2480> [image: arc drawing image] <https://www.youtube.com/watch?v=1PBd3VJrfDw> (See more the video at https://www.youtube.com/watch?v=1PBd3VJrfDw if you're interested) @ankith26 <https://github.com/ankith26> fixed - the init systems to prevent bugs from init-quit-init (#2428 <https://github.com/pygame/pygame/pull/2428>) - an error handling bug in pixelarray in #2444 <https://github.com/pygame/pygame/pull/2444> - the pygame default font would break when packaged with PyInstaller ( #2604 <https://github.com/pygame/pygame/pull/2604>) @Starbuck5 <https://github.com/Starbuck5> fixed: - 20 second load times for SysFont on Mac, and also gave Windows SysFont some love (#2594 <https://github.com/pygame/pygame/pull/2594>, #2640 <https://github.com/pygame/pygame/pull/2640>). - A bug where freetype would think coordinates of -1 represented an error was fixed in #2576 <https://github.com/pygame/pygame/pull/2576>. - A rare segfault in mixer.pre_init() on Mac, in #2494 <https://github.com/pygame/pygame/pull/2494> - Where window size couldn't be reduced after leaving SCALED mode on Windows (#2587 <https://github.com/pygame/pygame/pull/2587>) - Exiting fullscreen would put your window at (0, 0) in #2460 <https://github.com/pygame/pygame/pull/2460> - A failure in display.set_gamma() in #2524 <https://github.com/pygame/pygame/pull/2524> - The pygame.scrap module building properly on Mac and Windows (#2499 <https://github.com/pygame/pygame/pull/2499>, #2495 <https://github.com/pygame/pygame/pull/2495>). @MightyJosip <https://github.com/MightyJosip> fixed duplicate entries in display.list_modes() in #2470 <https://github.com/pygame/pygame/pull/2470> @robertpfeiffer <https://github.com/robertpfeiffer> fixed - IME placement in SCALED mode in #2451 <https://github.com/pygame/pygame/pull/2451> - A rare bug where Color.hsva would return invalid values in #2467 <https://github.com/pygame/pygame/pull/2467> Sysfont fixes One module in particular has come a long way in this release — sysfont. Thanks to @Starbuck5 <https://github.com/Starbuck5> As well as working better on windows and mac... Before, if you requested "Cambria," pygame would silently give out Cambria bold. [image: before] <https://user-images.githubusercontent.com/46412508/126018762-01786bdd-a8ee-…> Now, Cambria is Cambria [image: after] <https://user-images.githubusercontent.com/46412508/126019070-bdeaa29d-c898-…> (Of course you can still request bold from SysFont and it will hook you up, at least for Cambria) New Features ✨ @dr0id <https://github.com/dr0id> added - vector projection to the Vector2 and Vector3 classes in #2510 <https://github.com/pygame/pygame/pull/2510> - a “touch” attribute to all mouse events in #2514 <https://github.com/pygame/pygame/pull/2514> projected = v3.project(v3) This is useful for collision detection in finding the components in a certain direction (e.g. in direction of the wall). For a more detailed explanation see Wikipedia < https://en.wikipedia.org/wiki/Vector_projection>_. The .touch attribute is for events that were generated by a touch input device, and not a real mouse. You might want to ignore such events, if your application already handles finger events. @robertpfeiffer <https://github.com/robertpfeiffer> added an exclude argument to pygame.event.get(), allowing inverse filtering, in #2512 <https://github.com/pygame/pygame/pull/2512>, with a test in #2546 <https://github.com/pygame/pygame/pull/2546>. @MyreMylar <https://github.com/MyreMylar> worked on - changing mixer.set_reserved() to return the number of channels actually reserved in #2490 <https://github.com/pygame/pygame/pull/2490> - adding an actual implementation to the force parameter of mixer.find_channel() in #2491 <https://github.com/pygame/pygame/pull/2491> Before it simply wasn't implemented, only documented. @Starbuck5 <https://github.com/Starbuck5> added - a namehint argument to mixer.music.load() for easier loading of music from file-like objects. (#2497 <https://github.com/pygame/pygame/pull/2497>) - Vector2 support to the transform, display, and Mask modules, as well as keyword argument support to the transform and Mask modules (#2536 <https://github.com/pygame/pygame/pull/2536>, #2557 <https://github.com/pygame/pygame/pull/2557>, #2581 <https://github.com/pygame/pygame/pull/2581>) Internal / Portability New contributor @Muxelmann <https://github.com/Muxelmann> fixed the path to homebrew in #2636 <https://github.com/pygame/pygame/pull/2636>, fixing some pygame issues on M1 Mac! New contributor @odidev <https://github.com/odidev> and @illume <https://github.com/illume> added aarch64 wheel build support, along with a docker file, and github actions tests for it in #2610 <https://github.com/pygame/pygame/pull/2610> and #2675 <https://github.com/pygame/pygame/pull/2675> New contributor @fniephaus <https://github.com/fniephaus> made a compatibility fix for GraalPython in #2580 <https://github.com/pygame/pygame/pull/2580> @MyreMylar <https://github.com/MyreMylar> updated the sse2neon header to make it build alpha blitter on arm in #2425 <https://github.com/pygame/pygame/pull/2425> @ankith26 <https://github.com/ankith26> and @illume <https://github.com/illume> added github actions, disabled travis builds except arm64 in #2507 <https://github.com/pygame/pygame/pull/2507> and #2600 <https://github.com/pygame/pygame/pull/2600>. This was crucial to keep pygame development functional after the shutdown of travis-ci.org. @Pierre-Sassoulas <https://github.com/Pierre-Sassoulas> used their pylint expertise to keep pygame’s code base clean and functional in #2509 <https://github.com/pygame/pygame/pull/2509>, #2579 <https://github.com/pygame/pygame/pull/2579>, and #2634 <https://github.com/pygame/pygame/pull/2634>. @Starbuck5 <https://github.com/Starbuck5> added Python 3.10 support in #2586 <https://github.com/pygame/pygame/pull/2586>, updated functions to return bools rather than ints in #2534 <https://github.com/pygame/pygame/pull/2534>, and moved to SDL 2.0.16 on Windows in #2670 <https://github.com/pygame/pygame/pull/2670>. @illume <https://github.com/illume> moved to SDL 2.0.16 on Linux, as well as many other dependency updates, in #2676 <https://github.com/pygame/pygame/pull/2676> Docs _________________________ =(__ ___ __ __)= | | | | | python -m pygame.docs | | | | A large number | | documentation fixes | | were made in this | | release. | | | |__ ___ __ _____| =(_________________________)= @llindstrom <https://github.com/llindstrom>, @Pierre-Sassoulas <https://github.com/Pierre-Sassoulas>, and @Starbuck5 <https://github.com/Starbuck5> corrected incorrection information in: #2485 <https://github.com/pygame/pygame/pull/2485>, #2582 <https://github.com/pygame/pygame/pull/2582>, #2654 <https://github.com/pygame/pygame/pull/2654>. @robertpfeiffer <https://github.com/robertpfeiffer> added to the TEXTINPUT documentation in #2456 <https://github.com/pygame/pygame/pull/2456>. New contributors @SplatRT <https://github.com/SplatRT>, @bambalamm <https://github.com/bambalamm>, @deek80 <https://github.com/deek80>, @NKID00 <https://github.com/NKID00>, @MaukWM <https://github.com/MaukWM>, and @shawnbyday <https://github.com/shawnbyday> all cleaned up the documentation with grammar and typo fixes, in: #2431 <https://github.com/pygame/pygame/pull/2431>, #2437 <https://github.com/pygame/pygame/pull/2437>, #2519 <https://github.com/pygame/pygame/pull/2519>, #2555 <https://github.com/pygame/pygame/pull/2555>, #2583 <https://github.com/pygame/pygame/pull/2583>, #2644 <https://github.com/pygame/pygame/pull/2644>. @Starbuck5 <https://github.com/Starbuck5> contributed to this worthy goal in #2590 <https://github.com/pygame/pygame/pull/2590> New contributor @Grimmys <https://github.com/Grimmys> and @Starbuck5 <https://github.com/Starbuck5> worked on the documentation build system, upgrading it from Sphinx 1 to Sphinx 3, hiding the obsolete Overlay and cdrom modules from the top bar, and adding the --fullgeneration flag to setup.py docs. #2513 <https://github.com/pygame/pygame/pull/2513>, #2511 <https://github.com/pygame/pygame/pull/2511>, #2617 <https://github.com/pygame/pygame/pull/2617>, #2624 <https://github.com/pygame/pygame/pull/2624>. New contributor @Taffer <https://github.com/Taffer> added a page to showcase all of pygame’s named colors, in #2559 <https://github.com/pygame/pygame/pull/2559>. When it is live, it will be at https://www.pygame.org/docs/ref/color_list.html. New contributor @kaiec <https://github.com/kaiec> noticed that SDL_Image, pygame’s image loading backend, supports more than we had documented, so updated the documentation accordingly, in #2619 <https://github.com/pygame/pygame/pull/2619>. (We support WebP and SVG, who knew?) New contributor @duthades <https://github.com/duthades> continued this by adding tests for the new image formats in #2656 <https://github.com/pygame/pygame/pull/2656>. Finally, new contributor @ayushbisht2001 <https://github.com/ayushbisht2001> added a nice logo to the README in #2441 <https://github.com/pygame/pygame/pull/2441>, sprucing it up nicely. Type Hints Typehints got some neat updates in this release as well, so that you can code with pygame in your favourite IDE and you get that sweet auto-correct/autocomplete and type-checking to catch bugs even before they are reported! New contributor @jakebailey <https://github.com/jakebailey> made tons of good typehint fixes in #2537 <https://github.com/pygame/pygame/pull/2537>, the most important ones being, correctly exporting submodules in a way that typehints are recognized for the submodules, and generic types used in annotations being fixed to include the missing type params, among other fixes. New contributors: - @w-v <https://github.com/w-v> fix set_mods() type hint in #2457 <https://github.com/pygame/pygame/pull/2457> - @nathanielconroy <https://github.com/nathanielconroy> less strict type checking for AbstractGroup.add in #2646 <https://github.com/pygame/pygame/pull/2646> - @sandipanpanda <https://github.com/sandipanpanda> Fixed wrong kwargs types in sprite.pyi in #2652 <https://github.com/pygame/pygame/pull/2652> - @vnmabus <https://github.com/vnmabus> Fix syntax for typing AbstractGroup attributes in #2663 <https://github.com/pygame/pygame/pull/2663> - @bydariogamer <https://github.com/bydariogamer> Update Vector3 overloaded constructor signature in #2674 <https://github.com/pygame/pygame/pull/2674> - @shingo-kagami <https://github.com/shingo-kagami> Fixed mouse.get_pressed() type hint in #2685 <https://github.com/pygame/pygame/pull/2685> @MyreMylar <https://github.com/MyreMylar> Add str and RGBA tuple types to freetype/font type hints in #2462 <https://github.com/pygame/pygame/pull/2462>, and Correct blits typehint sequence arg to cover blit inputs in #2482 <https://github.com/pygame/pygame/pull/2482> @ankith26 <https://github.com/ankith26> and @zoldalma999 <https://github.com/zoldalma999> overhauled many incorrect uses of Optional in #2678 <https://github.com/pygame/pygame/pull/2678> Examples New contributor @jonozw <https://github.com/jonozw> added a needed pg.quit() for IDLE compatibility in the stars example (#2560 <https://github.com/pygame/pygame/pull/2560>). Many other examples needed this too, so another expeditious new contributor (@AnudeepGunukula <https://github.com/AnudeepGunukula>) swept through and made sure it was on every example in #2643 <https://github.com/pygame/pygame/pull/2643>. @MightyJosip <https://github.com/MightyJosip> fixed a crash in the mask example in #2606 <https://github.com/pygame/pygame/pull/2606>. New contributor @mljli <https://github.com/mljli> improved the aliens example in #2608 <https://github.com/pygame/pygame/pull/2608>, new contributor @njbradley <https://github.com/njbradley> improved the font_viewer example in #2655 <https://github.com/pygame/pygame/pull/2655> (it’s cool check it out), and @Starbuck5 <https://github.com/Starbuck5> overhauled the chimp example in #2651 <https://github.com/pygame/pygame/pull/2651>. Experimental super secret _sdl2 things TODO: this section is supposed to be top secret! No one is supposed to know about these new APIs yet, except people wanting to give feedback and live dangerously. So I guess bikers, and skydivers can know about this stuff? @galexandreg <https://github.com/galexandreg> added blend_mode, color tuples, origin=None, to _sdl2.Image in #2426 <https://github.com/pygame/pygame/pull/2426> and draw_blend_mode to Renderers in #2520 <https://github.com/pygame/pygame/pull/2520> @Starbuck5 <https://github.com/Starbuck5> added prototype docs to the _sdl2.video system in #2533 <https://github.com/pygame/pygame/pull/2533>. They will be live at https://www.pygame.org/docs/ref/sdl2_video.html. @zoldalma999 <https://github.com/zoldalma999> did lots of work getting the SDL2 controller system ported in #2423 <https://github.com/pygame/pygame/pull/2423>. Thank Yous - To all the returning contributors who helped improve pygame this release: Josip Komljenović (@MightyJosip <https://github.com/MightyJosip>) | Dan Lawrence (@MyreMylar <https://github.com/MyreMylar>) | Pierre Sassoulas ( @Pierre-Sassoulas <https://github.com/Pierre-Sassoulas>) | Charlie Hayden (@Starbuck5 <https://github.com/Starbuck5>) | Ankith (@ankith26 <https://github.com/ankith26>) | @droid <https://github.com/droid> | @galexandreg <https://github.com/galexandreg> | Rene Dudfield (@illume <https://github.com/illume>) | Lenard Lindstrom (@llindstrom <https://github.com/llindstrom>) | @robertpfeiffer <https://github.com/robertpfeiffer> | @zoldalma999 <https://github.com/zoldalma999> - And to all the new contributors who put themselves out there by volunteering fixes: @MaukWM <https://github.com/MaukWM> | Chris Herborth (@Taffer <https://github.com/Taffer>) | NKID00 (NK) (@NKID00 <https://github.com/NKID00>) | Fabio Niephaus (@fniephaus <https://github.com/fniephaus>) | Ayush Bisht (@ayushbisht2001 <https://github.com/ayushbisht2001>) | Nathaniel Conroy (@nathanielconroy <https://github.com/nathanielconroy>) | Kai Eckert (@kaiec <https://github.com/kaiec>) | Anudeep Gunukula (@AnudeepGunukula <https://github.com/AnudeepGunukula>) | @bydariogamer <https://github.com/bydariogamer> | Don Patterson (@deek80 <https://github.com/deek80>) | @njbradley <https://github.com/njbradley> | @odidev <https://github.com/odidev> | @SplatRT <https://github.com/SplatRT> | Max Zangs (@Muxelmann <https://github.com/Muxelmann>) | mljli (@mljli <https://github.com/mljli>) | shawnbyday (@shawnbyday <https://github.com/shawnbyday>) | Bambalam (@bambalamm <https://github.com/bambalamm>) | Grimmys (@Grimmys <https://github.com/Grimmys>) | Carlos Ramos Carreño (@vnmabus <https://github.com/vnmabus>) | Jake Bailey (@jakebailey <https://github.com/jakebailey>) | Sanket Duthade (@duthades <https://github.com/duthades>) | Matt Hollands (@mhollands <https://github.com/mhollands>) | @w-v <https://github.com/w-v> | @sandipanpanda <https://github.com/sandipanpanda> | jonozw (@jonozw <https://github.com/jonozw>) | Shingo Kagami (@shingo-kagami <https://github.com/shingo-kagami>) - As all releases, this one too would not have been possible without support from the community, from people submitting issues, to people making PRs for all kinds of improvements, from typo fixes, to fixing complex segfaults in C code, every contribution matters a lot! - patreon.com/pygame sponsors: Christopher Cacho, Daniel Lawrence, Tommi Sinivuo, Leif Theden, zoldalma, rosa, and Bob Johnson. With their help half of the first patreon goal of covering the monthly hosting costs has been covered and a number of pygame tutorials have been made. - The people supporting pygame financially by buying the pre-release of a pygame book. It's a book by a long time pygame contributor where all funds go towards pygame development. - People helping out the community in general, from making youtube tutorials, to answering questions on various forums of discussions, to helping with packaging pygame! ------------------------------ - merged PRs <https://github.com/pygame/pygame/pulls?q=is%3Apr+is%3Aclosed+merged%3A2020-…> since we started the pygame 2.0.2 series on the 24th of December 2020 - 305 Commits since 2.0.1 stable release <https://github.com/pygame/pygame/compare/2.0.1...2.0.2.dev2> - previous pygame release notes <https://github.com/pygame/pygame/releases> (Special thanks to Ankith & Charlie for sending this release out)

1 0

[Python-announce]Announcing sqlalchemy-bigquery 1.0.0
by Tim Swast 19 Aug '21

19 Aug '21

We’re happy to announce the general-availability <https://github.com/googleapis/google-cloud-python/blob/master/README.rst#ge…> of sqlalchemy-bigquery <https://googleapis.dev/python/sqlalchemy-bigquery/latest/index.html> version 1.0.0, the Google BigQuery dialect for SQLAlchemy <https://www.sqlalchemy.org/>, allowing SQLAlchemy to be used with BigQuery, including schema definition, querying and schema migration with Alembic <https://alembic.sqlalchemy.org/en/latest/>. This release builds on and replaces the earlier pybigquery <https://pypi.org/project/pybigquery/> project. The release can be installed from PyPI python -m pip install sqlalchemy-bigquery==1.0.0 Please share any feedback as an issue on GitHub: https://github.com/googleapis/python-bigquery-sqlalchemy/issues Thanks! * • **Tim Swast* * • *Senior Software Friendliness Engineer, Data & Analytics * • *Google Cloud Developer Relations * • *Chicago, IL, USA

1 0

[Python-announce]FlaskCon's Call For Volunteers Is On
by Abdur-Rahmaan Janhangeer 17 Aug '21

17 Aug '21

Greetings list, As preparations for FlaskCon intensifies, the call for volunteers goes live: https://twitter.com/FlaskCon/status/1427542892642410502?s=20 You can also chip in directly here: https://docs.google.com/forms/d/e/1FAIpQLSfsHNBcclWSmVkk4LDD_EnlhrlKdWlGOak… According to previsions, it might be the last Python conf of the year! Kind Regards, Abdur-Rahmaan Janhangeer about <https://compileralchemy.github.io/> | blog <https://www.pythonkitchen.com> github <https://github.com/Abdur-RahmaanJ> Mauritius

1 0

[Python-announce]ANN: Blue 0.7.0 Released
by Grant Jenks 16 Aug '21

16 Aug '21

Announcing the release of Blue version 0.7.0! 2021-08-16 (0.7.0) ------------------ - Bump dependency on Black to 21.7b0 - Prefer double quotes for non-docstring triple quoted strings (GH#10) - Add support for "py39" as target-version (GH#44) - Docstrings now always use triple-double-quoted strings (GH#5) ==== Blue ==== Some folks like `black <https://black.readthedocs.io/en/stable/>`_ but I prefer `blue <https://blue.readthedocs.io/en/latest/>`_. What is blue? ============= ``blue`` is a somewhat less uncompromising code formatter than ``black``, the OG of Python formatters. We love the idea of automatically formatting Python code, for the same reasons that inspired ``black``, however we take issue with some of the decisions ``black`` makes. Kudos to ``black`` for pioneering code formatting for Python, and for its excellent implementation. Where the ``blue`` maintainers disagree with the stylistic (and unconfigurable) choices made by ``black``, we monkeypatch to change these decisions to our own liking. We intend for these differences to be minimal; even in cases where we'd prefer something different, there's a lot we can live with for the sake of consistency. We'd prefer not to fork or monkeypatch. Instead, our hope is that eventually we'll be able to work with the ``black`` maintainers to add just a little bit of configuration and merge back into the ``black`` project. We'd be ecstatic if ``blue`` eventually were retired. Until then, we'll maintain our small set of hacks on top of ``black`` and carefully consider what other deviations are needed to assuage our sensitive, but experienced, eye. How do I use blue? ================== Exactly the same as you would use ``black``. Invoke and configure ``blue`` as you would ``black`` -- just replace the ``black`` command with ``blue``, sit back, and enjoy even betterly formatted Python code! You can refer to `black's <https://black.readthedocs.io/en/stable/>`_ documentation for anything not listed here. So what's different? ==================== Here is a brief list of differences between ``blue`` and ``black``: * ``blue`` defaults to single-quoted strings. This is probably the most painful ``black`` choice to our eyes, and the thing that inspired ``blue``. We strongly prefer using single quoted strings over double quoted strings for everything *except* docstrings and triple quoted strings (TQS). Don't ask us why we prefer double-quotes for TQS; it just looks better to us! For all other strings, ``blue`` defaults to single quoted strings. In the case of docstrings, those always use TQS with double-quotes. * ``blue`` defaults to line lengths of 79 characters. Nearly every project creates a pyproject.toml just to change this one setting so making it consistent with PEP 8 seems relatively harmless. * ``blue`` preserves the whitespace before the hash mark for right hanging comments. * ``blue`` supports multiple config files: ``pyproject.toml``, ``setup.cfg``, ``tox.ini``, and ``.blue``. We are `accumulating <https://github.com/grantjenks/blue/issues/2>`_ a list of other deviations we are considering. As we decide to implement any particular suggestion, we'll turn those into individual issues and tackle them one-by-one. If you have suggestions for other deviations from ``black``'s choices, please open a separate ticket on our tracker, and we'll see how it goes! Why "blue"? =========== Several reasons! If your formatter is going to beat up your code, it'll leave it black and blue, or maybe in this case, black *or* blue. Blue is better! We also thought about "tan" because, yum! But that project name was already taken. Frankly, "blue" was also taken, but largely unused. Our thanks to Nick Ficano for donating the project namespace to us! Blue is also the color of `LinkedIn <https://www.linkedin.com/>`_, the authors' gracious employer, and we intend to socialize its use within our company code base. Contributors ============ ``blue`` thanks this list of contributors for all its wonderful goodness. * The `wonderful folks <https://github.com/psf/black#authors>`_ from the ``black`` project. * Grant Jenks * Barry Warsaw * Corey from FutureSpaceDesigns for the unofficial logo and `blue project merchandise <https://www.teepublic.com/t-shirt/6556561-tobias-blue>`_. ``blue`` is licensed under the terms of the Apache License Version 2.0. ``black`` is `licensed <https://github.com/psf/black#license>`_ under the terms of the MIT license. Project details =============== .. image:: https://img.shields.io/badge/code%20style-blue-blue.svg :target: https://blue.readthedocs.io/ .. image:: https://github.com/grantjenks/blue/workflows/integration/badge.svg :target: https://github.com/grantjenks/blue/actions?query=workflow%3Aintegration .. image:: https://github.com/grantjenks/blue/workflows/release/badge.svg :target: https://github.com/grantjenks/blue/actions?query=workflow%3Arelease * Project home: https://github.com/grantjenks/blue * Report bugs and suggestions at: https://github.com/grantjenks/blue/issues * Code hosting: https://github.com/grantjenks/blue.git * Documentation: https://blue.readthedocs.io/en/latest

1 0