Mailman 3 October 2020 - Python-announce-list

PyCon ZA 2020 - Call for Submissions
by Neil Muller Nov. 12, 2020

Nov. 12, 2020

PyCon ZA 2020 will take place on the 8th & 9th of October, 2020. This year, due to the ongoing uncertainty of when conference facilities will be allowed to open, we will be running PyCon ZA as an online event. We are looking for the following presentations: - Keynotes (45 minute long talks on a subject of general interest) - Talks (30 minute long talks on more specific topics) If you would like to give a presentation, please register at https://za.pycon.org/ and submit your proposal, following the instructions at https://za.pycon.org/talks/submit-talk/ . We have a number of tracks available, including: Data Science, Teaching and Learning with Python, Web, Scientific Computing, Testing and Other (which includes all talks that don't fall under the mentioned tracks). We hope to notify accepted presenters by no later than the 31st of August 2020. Speakers will be expected to be available after the presentation for a short Q&A session. Shared sessions are also possible. The presentations will be in English. PyCon ZA offers a mentorship program for inexperienced speakers. If you would like assistance preparing your submission, email team(a)za.pycon.org with a rough draft of your talk proposal and we'll find a suitable experienced speaker to act as a mentor. If you want to present something else at PyCon ZA, please contact the organising committee at team(a)za.pycon.org . We’re researching which software platforms will be most suitable for running PyCon ZA. As soon as we have finalised this decision, we’ll make it public and update potential presenters. If you have experience with presenting on particular platforms, we'd love to hear from you at team(a)za.pycon.org . -- Neil Muller On behalf of the PyCon ZA organising committee

2 1

[ANN] RISE 5.7.1 is out!
by Damián Avila Oct. 30, 2020

Oct. 30, 2020

We're pleased to announce the release of *RISE* 5.7.1! *What is RISE?* RISE lets you show your Jupyter notebook rendered as an executable *Reveal.js*-based slideshow. It is your very same notebook but in a *slidy* way! For more information about this release, please visit the following blog post: https://damianavila.github.io/blog/posts/rise-571-is-out.html Have fun!! -- *Damián Avila*

1 0

pygame 2
by René Dudfield Oct. 30, 2020

Oct. 30, 2020

<https://user-images.githubusercontent.com/9541/97474395-5b9a9b80-194c-11eb-…> The 28th of October 2020 is the pygame <https://pygame.org/wiki/about> 2.0 release date, because pygame turns 20 years of age. ------------------------------ ,--. | oo| | ~~| o o o o o o o o o o o o o |/\/\| python3 -m pip install pygame==2.0.0 What's the best feature of pygame 2? Maybe it's "*backwards compatibility*". For many, many apps pygame 2 is backwards compatible. Have an pygame app from the year 2000? It will probably work. We still have some known issues and open backwards compatibility issues(see below), but a lot of things work just as they did before. Yes, we still have python 2 support. How does one summarize the 3306 changes since we started the pygame 2 series in July of 2018 based on patches going back to 2012 and even earlier? - Support for Metal, Direct 3d, Vulkan, OpenGL 3.0+ in various profiles (core, compatibility, debug, robust, etc), OpenGL ES, and other modern hardware accelerated video APIs across many platforms. - SSE2/Neon assembly image drawing. Much faster drawing routines, image loading, and alpha blending. - Type Hints, for code completion (and to help you make the squiggly lines disappear) in editors and IDEs. - Code cleanup, using lots of code robustness tools like static analyzers, and automated CI/CD. We've been able to help dozens of people new to community projects contribute. We have lots of work to go on code quality, but we're currently the highest rated Python and highest rate C large project on LGTM. - Many, many bug fixes including in our pygame.draw routines, pygame.math(for vectors), and pygame.mask for pixel perfect collision detection. - better support for PyPy (the fast JIT based implementation of python). See our milestone Are we pypy yet? No. <https://github.com/pygame/pygame/milestone/6> for our progress on making PyPy the best python for games. - libsdl version 2 support. Technically pygame 2.0 still works with SDL 1, but we recommend SDL2 which is vastly improved over SDL1 for most use cases. Probably we will remove SDL 1 support starting pygame 2.1. - Touch support (multitouch, gestures, etc) - Audio input support (make games with your microphone!). - Message alert boxes (Press OK, or Cancel). - Better keyboard support. Proper unicode input and IME support. - Much improved game controller support. - Better image and audio format support. Including: webp, 32bit wav files, and much more reliable mp3 support. - Multiple display support, and multiple window support (multi window support is still experimental, more will come in pygame 2.1). - Android support through python for android (fork of pygame subset for android). Better documentation, and better support will come in future releases. - to make distributing your apps easier, a built in "pyinstaller hook"and compatibility with cxfreeze. - binary "wheels" on many platforms and versions of python from the old python 2.7 - to the latest python 3.9 (and with pypy!). - lots of quality of life improvements like Surface.fill('black') instead of Surface.fill(pygame.Color(0, 0, 0)). Also keywords are supported for many more function arguments. You can draw rounded corners on rects. - plenty of new examples, like python3 -m pygame.examples.font_viewer, and python3 -m pygame.examples.music_drop_fade. Additionally the example source code has been cleaned up a lot to follow a more current python style. - Hundreds of documentation improvements, include a new Korean tutorial. - a special SCALED mode which takes low pixel games and automatically translates them to a larger window. Imagine your 320x200 resolution game of glorious pixel art... on modern screens that would be a very tiny windows. Now with SCALED it shows up big on a Full HD screen, or even a 4K/8K screen and the translation of mouse coordinates and up-scaling of pixels is done for you (hardware accelerated of course). That was a summary of some of the goodies in pygame 2. We will be releasing more articles and tutorials on new features as time goes on. You can also look at the previous release notes for more info (see end of this post). thank you 🎉 Probably one of the better realizations thinking about pygame on its 20th birthday is that there is a much larger group of people who have contributed to crafting pygame in recent years. Some have moved onto other things like jobs, family or writing cookbooks in the Canadian wilderness. Much respect for volunteering time to a community project like pygame. *Firstly thanks to the pygame team members* who contributed to the pygame 2 series, new and old... David Lönnhager (@dlon <https://github.com/dlon>) | René Dudfield (@illume <https://github.com/illume>) | Charles (@charlesej <https://github.com/charlesej>) | Dan Lawrence (@MyreMylar <https://github.com/MyreMylar>) | Ankith (@ankith26 <https://github.com/ankith26>) | Niels Thykier (@nthykier <https://github.com/nthykier>) | Lenard Lindstrom (@llindstrom <https://github.com/llindstrom>) | Sigurður Sveinn Halldórsson (@siggisv <https://github.com/siggisv>) | @robertpfeiffer <https://github.com/robertpfeiffer> | Josip Komljenović (@MightyJosip <https://github.com/MightyJosip>) | Travis Chang (@Reminisque <https://github.com/Reminisque>) | xFly_Dragon (@husano896 <https://github.com/husano896>) | Adam Andrews (@adamandrews1 <https://github.com/adamandrews1>) | (@galexandreg <https://github.com/galexandreg>) | Thiago Jobson (@thiagojobson <https://github.com/thiagojobson>) | (@mcpalmer1980 <https://github.com/mcpalmer1980>) | @charlesoblack <https://github.com/charlesoblack> | Daniel Pope (@lordmauve <https://github.com/lordmauve>) | Thomas Kluyver (@takluyver <https://github.com/takluyver>) | @e1000 <https://github.com/e1000> | Andy Nguyen (@anguye13 <https://github.com/anguye13>) | @Starbuck5 <https://github.com/Starbuck5> | Ian Mallett (@imallett <https://github.com/imallett>) Equally important thank you go out to all the other contributors, some of which contributed to a community project for the first time. Pedro de la Peña @pedrodelapena <https://github.com/pedrodelapena> | @lkito <https://github.com/lkito> | @khuang0312 <https://github.com/khuang0312> | @tsadama <https://github.com/tsadama> | @Bottersnike <https://github.com/Bottersnike> | @alphaCTzo7G <https://github.com/alphaCTzo7G> | Amos Bastian (@amosbastian <https://github.com/amosbastian>) | Andrey Lopukhov (@andreyx86 <https://github.com/andreyx86>) | Augusto Noronha (@augusto2112 <https://github.com/augusto2112>) | Bernardo Sulzbach (@bernardosulzbach <https://github.com/bernardosulzbach>) | (@Bottersnike <https://github.com/Bottersnike>) | Cai Q.T. (@CAIQT <https://github.com/CAIQT>) | (@Cerealdragon) | (@ChrisWeissNike <https://github.com/ChrisWeissNike>) | (@cmtrapp02 <https://github.com/cmtrapp02>) | Daniel Molina (@daniel-molina <https://github.com/daniel-molina>) | David Caughell (@DavidCaughell) | ( @dr0id <https://github.com/dr0id>) | burmer (@dtschirmer <https://github.com/dtschirmer>) | (@IchMageBaume <https://github.com/IchMageBaume>) | (@LambdaGoblin <https://github.com/LambdaGoblin>) | François Magimel (@Linkid <https://github.com/Linkid>) | (@LiquidFenrir <https://github.com/LiquidFenrir>) | Mark Hurley (@markph0204 <https://github.com/markph0204>) | Marius Gedminas (@mgedmin <https://github.com/mgedmin>) | (@metulburr <https://github.com/metulburr>) | Michael Farrell (@micolous <https://github.com/micolous>) | Dominik George (@Natureshadow <https://github.com/Natureshadow>) | Nik (@nikolas) | Nunu-Willump (@Nunu-Willump) | (@pleboulanger) | Rebecca Chen (@rchen152) | (@robertpfeiffer <https://github.com/robertpfeiffer>) | Sett (@sw00) | @seenemikk | Nguyễn Gia Phong (@McSinyx)| Sebastian Henz | @BastiHz | Alice Lia Stapleton (@slimelia) raphacosta27 (@raphacosta27) | Bill (@AdditionalPylons) | Gabriel Moreira (@gabsmoreira) | zoldalma999 (@zoldalma999) | amipy (@amipy) | DGMcKenney (@DGMcKenney) | Grigoris Tsopouridis ((@gtsopus)) | Ilia Gogotchuri (@Gogotchuri) | Jim Quach (@jiquach) | Aaron Li (@AaronLi) | Clark Seanor (@cruxicheiros) | K Duggan (@kduggan15) | Michał Górny (@mgorny) | Clark Seanor (@cruxicheiros) | jtoloff (@jtoloff) | 41aaronb (@41aaronb) | Prasanna Venkatesh (@hanzohasashi33) | zoldalma999 (@zoldalma999) | Nihal Mittal (@codescientist703) | leopoldwe (@leopoldwe) | Scott Noyes (@snoyes) Vicente González Ruiz (@vicente-gonzalez-ruiz)| Douglas (@douglas-cpp) | wuzh07 (@wuzh07) | Gerardo Antonio Hagad (@ginohagad) | Evan Kanter (@evank28) | Inada Naoki (@methane) | Jani Tiainen (@jtiaicomparison) | Christian Clauss (@cclauss) | Gosha Zacharov (@Gosha) | Steven Chua (@Graphcalibur) | K Duggan (@kduggan15) | PeanutbutterWarrior (@PeanutbutterWarrior) | Nachiket Naganure (@NachiketUN) | Pierre Haou (@pierrehaou) | Daniel Gillet (@dangillet) | Stefano Rivera (@stefanor) | Andre Miras (@AndreMiras) | glennmackintosh (@glennmackintosh) | Vilhelm Prytz (@vilhelmprytz) | DotMars (@DotMars) | Gabriel Duque (@zuh0) | Mark Hurley (@markph0204 <https://github.com/markph0204>) | Henrik Petersson (@hnrkcode) | Grigoriy (@flaambe) | Matt Sheppard (@mampersat) | s0lst1ce (@s0lst1ce) | Norman Packard (@nhpackard) | peanutbutterandcrackers (@peanutbutterandcrackers) A special thanks to all the people who help out others. From making videos, to answering questions, to writing guides (and even whole books). MyreMylar, MichaelCPalmer, jtiai, claudeb, DaFluffyPotato, Rabbid76, The Big Kahuna, sloth, Kingsley, ... and lots of other people. Thanks to the mods on forums, chat rooms and Q&A sites. Special thanks to Zireael07 for cheering on pull requests that people make 🎉 Thanks to people adding support and integration to libraries and tools like pgzero(lordmauve and co), Mu Editor (Nicholas and team), and pymunk (Victor Blomqvist). Very many people have contributed by reporting issues. This is fantastic help for people 👏 👏 👏 Without these issue reports and help in testing bugs and new features many parts simply wouldn't work. Thanks to the SDL folk, to the fluidsynth crew, to numpy devs (Matti and co), python for android, pypy project, and the python community at large. Thanks to the folks running game jams like ludumdare(Mike), pyweek(lordmauve), and alakajam. Thanks to renpytom for pygame subset for android and pygame_sdl2, thanks to Marcus von Appen for pysdl2. Thanks to people sharing your work with others on the pygame website, or on places like the pygame reddit, discord, or youtube. Thanks to the kind folk who work on packaging pygame from Debian, Ubuntu, Arch, FreeBSD, and piwheels (@bennuttall). Thanks for the people teaching and learning with pygame all over the world. Last but not least... a very special thanks to everyone we've missed that should be listed here. Really. Thank you (you). Thanks. Known issues We have an up to date list of issues marked with the Compatibility Python 2 <https://github.com/pygame/pygame/issues?q=is%3Aissue+is%3Aopen+label%3A%22C…> label. These are compatibility issues where something worked in pygame 1, but doesn't work in pygame 2. At the time of writing this included: - the pygame.cdrom package not being there (mainly because it isn't in SDL2 anymore). - pygame.scrap is only working with text, not images (needs some porting and testing done). - pygame.event.post is having issues with some event types. - pygame.display.set_palette is not implemented (not in SDL2). - display.set_mode() ignores depth value. It just returns one it thinks is appropriate. We've already investigated many of these issues, and even have some work in progress on some of them. If you're particularly interested in one of them please let us know. Also if you have any issues with your existing apps, we are very interested in finding out. 🌺🌻🌹🥀🌷🌼🌸💐💮🌺🌻🌹🥀🌷🌼🌸💐💮🌺🌻 🌼🌸 python3 -m pip install pygame==2.0.0 🌺🌻🌹🥀🌷🌼🌸💐💮🌺🌻🌹🥀🌷🌼🌸💐💮🌺🌻 Happy pygame 20th birthday all! 🎉 🍰 🥳 <https://user-images.githubusercontent.com/9541/97467489-8bde3c00-1944-11eb-…> ------------------------------ - 937 merged PRs <https://github.com/pygame/pygame/pulls?q=is%3Apr+is%3Aclosed+merged%3A2018-…> since we started the pygame 2 series in Jul 19, 2018. - 3306 Commits since 1.9.4 stable release <https://github.com/pygame/pygame/compare/1.9.4...2.0.0> - previous pygame release notes <https://github.com/pygame/pygame/releases>

1 0

NumPy 1.19.3 release
by Charles R Harris Oct. 29, 2020

Oct. 29, 2020

Hi All, On behalf of the NumPy team I am pleased to announce that NumPy 1.19.3 has been released. NumPy 1.19.3 is a small maintenance release with two major improvements: - Python 3.9 binary wheels on all supported platforms, - OpenBLAS fixes for Windows 10 version 2004 fmod bug. This release supports Python 3.6-3.9 and is linked with OpenBLAS 3.12 to avoid some of the fmod problems on Windows 10 version 2004. Microsoft is aware of the problem and users should upgrade when the fix becomes available, the fix here is limited in scope. NumPy Wheels for this release can be downloaded from the PyPI <https://pypi.org/project/numpy/1.19.3/>, source archives, release notes, and wheel hashes are available on Github <https://github.com/numpy/numpy/releases/tag/v1.19.3>. Linux users will need pip >= 0.19.3 in order to install manylinux2010 and manylinux2014 wheels. *Contributors* A total of 8 people contributed to this release. People with a "+" by their names contributed a patch for the first time. - Charles Harris - Chris Brown + - Daniel Vanzo + - E. Madison Bray + - Hugo van Kemenade + - Ralf Gommers - Sebastian Berg - @danbeibei + *Pull requests merged* A total of 10 pull requests were merged for this release. - #17298: BLD: set upper versions for build dependencies - #17336: BUG: Set deprecated fields to null in PyArray_InitArrFuncs - #17446: ENH: Warn on unsupported Python 3.10+ - #17450: MAINT: Update test_requirements.txt. - #17522: ENH: Support for the NVIDIA HPC SDK nvfortran compiler - #17568: BUG: Cygwin Workaround for #14787 on affected platforms - #17647: BUG: Fix memory leak of buffer-info cache due to relaxed strides - #17652: MAINT: Backport openblas_support from master. - #17653: TST: Add Python 3.9 to the CI testing on Windows, Mac. - #17660: TST: Simplify source path names in test_extending. Cheers, Charles Harris

1 0

pytest 6.1.2 released
by Bruno Oliveira Oct. 28, 2020

Oct. 28, 2020

pytest 6.1.2 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: * Bruno Oliveira * Manuel Mariñez * Ran Benita * Vasilis Gerakaris * William Jamir Silva Happy testing, The pytest Development Team

1 0

PyCA cryptography 3.2.1 released
by Paul Kehrer Oct. 28, 2020

Oct. 28, 2020

PyCA cryptography 3.2.1 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 2.7, Python 3.5+, and PyPy. Changelog (https://cryptography.io/en/latest/changelog.html#v3-2-1): * Disable blinding on RSA public keys to address an error with some versions of OpenSSL. -Paul Kehrer (reaperhulk)

1 0

ANN: Astropy v4.1 released
by Erik Tollerud Oct. 27, 2020

Oct. 27, 2020

Dear colleagues, We are very happy to announce the v4.1 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: * A new SpectralCoord class for representing and transforming spectral quantities * Support for writing Dask arrays to FITS files * Added True Equator Mean Equinox (TEME) frame for satellite two-line ephemeris data * Support for in-place setting of array-valued SkyCoord and frame objects * Change in the definition of equality comparison for coordinate classes * Support use of SkyCoord in table vstack, dstack, and insert_row * Support for table cross-match join with SkyCoord or N-d columns * Support for custom attributes in Table subclasses * Added a new Time subformat unix_tai * Added support for the -TAB convention in FITS WCS * Support for replacing submodels in CompoundModel * Support for units on otherwise unitless models via the Model.coerce_units method. * Support for ASDF serialization of models 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.1.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 If you make use of the Anaconda Python Distribution, soon you will be able update to Astropy v4.1 with: conda update astropy Or if you cannot wait for Anaconda to update their default version, you can use the astropy channel: conda update -c astropy astropy Please report any issues, or request new features via our GitHub repository: https://github.com/astropy/astropy/issues Nearly 400 developers 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.1's release is v4.0 - this version will be maintained until next LTS release (v5.0, scheduled for Fall 2021). 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, 2018). We hope that you enjoy using Astropy as much as we enjoyed developing it! Erik Tollerud v4.1 Release Coordinator on behalf of The Astropy Project https://www.astropy.org/announcements/release-4.1.html

1 0

salabim 20.0.4 released
by Ruud van der Ham Oct. 26, 2020

Oct. 26, 2020

Salabim is a powerful discrete event simulation package in pure Python that can be used to model transport systems, production logistics, warehousing, communication systems, healthcare, mining, etc, It uses a process description methodology comparable to SimPy, but offers much more functionality: real-time animation, queue handling, monitoring of process characteristics, advanced statistical sampling and more. Go to www.salabim.org for details and resources. release notes salabim 20.0.4 2020-10-26 ======================================== New functionality (0) --------------------- A component now supports a level monitor 'status' that keeps track of all the statuses a component has been in. For instance, component.status.print_histogram(values=True) will print something like Histogram of x.1.status duration 40 value duration % data 4.300 10.8 ******** interrupted 4 10 ******** passive 11.500 28.7 *********************** requesting 10.100 25.2 ******************** scheduled 10.100 25.3 ******************** And of course, it is possible to get the duration a component was in a certain status, like passive_time = component.status.value_duration(sim.passive). You can even get the status of the component at a moment in the past, with e.g. status_4_units_ago = c1.status(env.now() - 4) In line with this change, the various statutes (passive, scheduled, ...) are no longer functions, but just strings. So now, therefore it is also possible to say passive_time = component.status.value_duration("passive") This will be quite transparent from the user. Only if the text representation of a status was required, status() had to be called, like print(f"car status={car.status()()}") From this version on, this should read print(f"car status={car.status()}") , which is also more intuitive. Alternatively, you can now also write print(f"car status={car.status.value}") This makes the methods Component.ispassive(), Component.isscheduled, etc. less required as component.status() == "passive" and component.status() == "scheduled" are arguably easier to understand. The package salabim now has a function statuses() that returns a tuple with all statuses a component can be in. So print(sim.statuses()) will print ('current', 'data', 'interrupted', 'passive', 'requesting', 'scheduled', 'standby', 'waiting') New functionality (1) --------------------- Component.mode is now a monitor. That makes it possible to get an overview of all modes a component has been in, either as a histogram or an animated monitor. And it is possible to get the duration a component was in a certain mode, with e.g. red_time = c1.mode.value_duration("red") It is even possible to get the mode a component was in at a given moment, like mode_4_units_ago = c1.mode(env.now() - 4) Because of this you can't use mode(x) anymore to set the mode directly. In order to do that, you have to use the new method set_mode: c1.set_mode("green") or c1.mode.value = "green" Both options do store the modetime correctly. Please observe that the initial value for mode is now the null string and not None. New_functionality (3) --------------------- New method: Monitor.values() to assess all values in a monitor. The values returned will be alphabetically sorted (not case sensitive), just as in Monitor.print_histogram(). The method supports both ex0 and force_numeric parameter flags. Example (with same monitor as above): print(x1.status.values()) will print ['data', 'interrupted', 'passive', 'requesting', 'scheduled'] New functionality (4) --------------------- The values parameter of print_histogram() can now also be an iterable (i.e. tuple, list or set). In that case, the statistics of only these values will be shown. Example (with same monitor as above): x1.status.print_histogram(values = sim.statuses()) will print Histogram of x.1.status duration 40 value duration % current 0 0 data 4.300 10.8 ******** interrupted 4 10 ******** passive 11.500 28.7 *********************** requesting 10.100 25.2 ******************** scheduled 10.100 25.3 ******************** standby 0 0 waiting 0 0 Any not shown values will be shown at the bottom as '<rest>'. So, again with the same monitor as above: x1.status.print_histogram(values = ("passive", "requesting", "error")) will print Histogram of x.1.status duration 40 value duration % passive 11.500 28.7 *********************** requesting 10.100 25.2 ******************** error 0 0 <rest> 18.400 46.0 ************************************ New functionality (5) --------------------- AnimateMonitor and Monitor.animate has got a new parameter: vertical_map. This parameter should be a function that accepts one argument (the value to be plotted). By default vertical_map is float. The function vertical_map should result in a float or raise a TypeError or ValueError. E.g. to map "red" to the value 1, "blue" to 2, etc., you could provide a mapping function like: vertical_map = "unknown red blue green yellow".split().index Note that in this example any value other than red, blue, green or yellow would map to 0 (via a ValueError exception). This vertical_map function can also be used to map to a logarithmic scale: vertical_map = lambda value_y: math.log(value_y) * 10 New functionality (6) --------------------- AnimateMonitor and Monitor.animate can now show labels and corresponding lines. There is full control of the colours, linewidth, fonts, placement, etc. See the docstring or documentation for details. There is a sample model (demo animation of labeled monitors.py) in the sample model folder to illustrate the usage of this new functionality with the new Component.status and Component.mode monitors. Changed functionality (0) ------------------------- The tests for which value(s) to include in Montitor.value_number_of_entries() Monitor.value_duration() Monitor.value_weight() are now direct and do not involve string conversion anymore. Normally, this won't cause any compatibility issues. Distribution change (0) ----------------------- The setup information (used in PyPI) now includes a set of classifiers as well as requires_python information. Compatibility change (0) ------------------------ Salabim requires Python 3.6 from now on. Internal change (0) ------------------- The statuses requesting and waiting were internally stored as scheduled and 'translated' in the status() method. Now, these statuses are natively stored as such (in the status monitor).

1 0

ANN: Leo 6.3 b1 released
by Edward K. Ream Oct. 26, 2020

Oct. 26, 2020

Leo 6.3 b1, http://leoeditor.com, is now available on GitHub <https://github.com/leo-editor/leo-editor>. Leo is an IDE, outliner and PIM <http://leoeditor.com/preface.html>. *The highlights of Leo 6.3* - leoAst.py: The unification of Python's token and ast worlds. - Retired all Qt Dock code. - Improved viewrendered and viewrendered3 plugins. - Improved several importer plugins. - Refactored Leo's key handling code. *Links* - Leo's home page: http://leoeditor.com - Documentation <http://leoeditor.com/leo_toc.html> - Tutorials <http://leoeditor.com/tutorial.html> - Video tutorials <http://leoeditor.com/screencasts.html> - Forum <http://groups.google.com/group/leo-editor> - Download <http://sourceforge.net/projects/leo/files/> - Leo on GitHub <https://github.com/leo-editor/leo-editor> - LeoVue <https://github.com/kaleguy/leovue#leo-vue> - What people are saying about Leo <http://leoeditor.com/testimonials.html> - A web page that displays .leo files <http://leoeditor.com/load-leo.html> - More links <http://leoeditor.com/leoLinks.html> ----------------------------------------------------------------- Edward K. Ream: edreamleo(a)gmail.com An old man, crazy about computer programming. Leo Editor: http://leoeditor.com/ -----------------------------------------------------------------

1 0

PyCA cryptography 3.2 released
by Paul Kehrer Oct. 26, 2020

Oct. 26, 2020

PyCA cryptography 3.2 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 2.7, Python 3.5+, and PyPy. Changelog (https://cryptography.io/en/latest/changelog/): * SECURITY ISSUE: Attempted to make RSA PKCS#1v1.5 decryption more constant time, to protect against Bleichenbacher vulnerabilities. Due to limitations imposed by our API, we cannot completely mitigate this vulnerability and a future release will contain a new API which is designed to be resilient to these for contexts where it is required. Credit to Hubert Kario for reporting the issue. CVE-2020-25659 * Support for OpenSSL 1.0.2 has been removed. Users on older versions of OpenSSL will need to upgrade. * Added basic support for PKCS7 signing (including SMIME) via PKCS7SignatureBuilder. -Paul Kehrer (reaperhulk)

1 0