🌐 Mailman 3 July 2018 - Python-announce-list - python.org

ANN: poliastro 0.10.0 released 🚀
by Juan Luis Cano July 21, 2018

July 21, 2018

Hi all, It fills us with astronomical joy to announce the release of poliastro 0.10.0! 🚀 poliastro is a pure Python library that allows you to simulate and analyze interplanetary orbits in a Jupyter notebook in an interactive and easy way, used in academia and the industry by people from all around the world. You can install it using pip or conda: pip install poliastro conda install poliastro --channel conda-forge This release was specially important in terms of development, and there are major changes in the structure of the code, several performance improvements, and many infrastructure changes. In particular, to pick only one highlight, we now have a website displaying benchmarks created using Airspeed Velocity: http://poliastro.github.io/poliastro-benchmarks In terms of new features, the most important one is the addition of continuous thrust (or low thrust) guidance laws for some orbital maneuvers, which means that now you can simulate spiral trajectories and much more. You can read the full release notes in the documentation: http://docs.poliastro.space/en/v0.10.0/changelog.html#poliastro-0-10-0-2018… By popular demand, the next release will be focused on improving reference frame handling in Orbit objects, which hopefully will fix one of the long standing pain points with poliastro. If you want to know more, don't miss my talk on the Open Source Cubesat Worshop held at the European Space Operations Centre: https://youtu.be/KnoYzqAw_vM?t=1h36m14s Please join our chat on Matrix/Riot and feel free to ask any questions you might have: https://riot.im/app/#/room/#poliastro:matrix.org Per Python ad astra! -- Juan Luis Cano

1 0

[RELEASED] Python 3.4.9rc1 and Python 3.5.6rc1 are now available
by Larry Hastings July 20, 2018

July 20, 2018

On behalf of the Python development community, I'm pleased to announce the availability of Python 3.4.9rc1 and Python 3.5.6rc1. Both Python 3.4 and 3.5 are in "security fixes only" mode. Both versions only accept security fixes, not conventional bug fixes, and both releases are source-only. You can find Python 3.4.9rc1 here: https://www.python.org/downloads/release/python-349rc1/ And you can find Python 3.5.6rc1 here: https://www.python.org/downloads/release/python-356rc1/ Python's entrenched bureaucracy soldiers on, //arry/

1 0

Trac 1.3.3 Released
by Ryan Ollos July 19, 2018

July 19, 2018

Trac 1.3.3 Released ==================== Trac 1.3.3, the latest development release leading up to Trac 1.4, is available. You will find this release at the usual places: https://trac.edgewall.org/wiki/TracDownload#LatestDevRelease You can find the detailed release notes for 1.3.3 on the following pages: https://trac.edgewall.org/wiki/1.3/TracChangeLog https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.3#MaintenanceReleases Now to the packages themselves: URLs: https://download.edgewall.org/trac/Trac-1.3.3-py2-none-any.whl https://download.edgewall.org/trac/Trac-1.3.3.tar.gz https://download.edgewall.org/trac/Trac-1.3.3.win32.exe https://download.edgewall.org/trac/Trac-1.3.3.win-amd64.exe MD5 sums: 22a4af92055f6aa3aab455dae6a9ec32 Trac-1.3.3-py2-none-any.whl ad156bfb7ac1ae04265fd81c4c64f333 Trac-1.3.3.tar.gz 41d88efa8e30dee3d75ea0473856700d Trac-1.3.3.win32.exe f40f10c3ea42dd51c3792d9568885fd6 Trac-1.3.3.win-amd64.exe SHA1 sums: b9029a5b552d3b6ea7d103f2f735c4d3d8a885a9 Trac-1.3.3-py2-none-any.whl 9ec984ee4a6e84af5eed999ec62c2a87f651c6aa Trac-1.3.3.tar.gz 27a77680214e9e989b505ff67beeea4d173298be Trac-1.3.3.win32.exe c2fcd37e2d558cc3895edc7905effb4a4a379200 Trac-1.3.3.win-amd64.exe Acknowledgements ================ Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we hope that Trac will be useful to like-minded programmers around the world, and that this release will be an improvement over the last version. Please let us know. /The Trac Team http://trac.edgewall.org/

1 0

Fwd: Package maintainers: verify your PyPI account email address
by Sumana Harihareswara July 19, 2018

July 19, 2018

If you maintain any PyPI packages, please verify your address on PyPI. Details below. -------- Forwarded Message -------- Subject: Package maintainers: verify your PyPI account email address Date: Mon, 16 Jul 2018 21:57:38 -0400 From: Sumana Harihareswara <sh(a)changeset.nyc> To: DistUtils mailing list <distutils-sig(a)python.org> Heads-up: if you have a pypi.org or test.pypi.org account, please verify your email address: https://pypi.org/manage/account/ https://test.pypi.org/manage/account/ Reason: > We have a problem with a bit of our data, namely that due to historical reasons we have a fair amount of users in the database that do not have a verified primary email address. The side effect of this is that we're currently sending emails to email addresses that we have not had verified. This is a bad situation to be in, because in order to keep our bounce/spam rate low, we should be confirming all email addresses before sending email to them. In addition the way our bounce handling code works is it un-verifies the email address, which the intent was to stop sending email to it until the user has reverified their email address. > > In total there are about 193k user accounts with a unverified email address for their primary address, and 44k that do have a verified email address for their primary account. > > So we need to come up with a strategy to resolve this, because it's pretty important that we don't send email to unverified addresses. (quoting from Donald Stufft's explanation https://github.com/pypa/warehouse/issues/3632 which goes on to detail the step-by-step plan) Package maintainers should especially do this soon. As of a few days ago, any user whose primary email address is unverified can't upload a file: https://github.com/pypa/warehouse/pull/4292 Please forward to other package maintainers. After we iron out any issues I figure we'll email the announce list https://mail.python.org/mm3/mailman3/lists/pypi-announce.python.org/ . -- Sumana Harihareswara Changeset Consulting https://changeset.nyc

1 0

EuroPython 2018: Day passes now also valid for Sprints Weekend
by M.-A. Lemburg July 19, 2018

July 19, 2018

Due to popular demand, we are making it possible to attend the Sprints Weekend (July 28-29), even if you only have a day pass or are considering to buy one and not a regular conference tickets which includes the sprints as well. * EuroPython 2018 Sprints (Hackathons) * https://ep2018.europython.eu/en/events/sprints/ If you have never been to a sprint, you’ll be amazed at how much you can learn from others while working on simple or more complex projects. If you have already run sprints yourself, why not run one at EuroPython and get to know new people for your project ? Please head on to our EuroPython Sprints page for more details. Come and join the sprinters ! 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/176026105657/europython-2018-day-passes-now… Tweet: https://twitter.com/europython/status/1019630424883113985 Enjoy, -- EuroPython 2018 Team https://ep2018.europython.eu/ https://www.europython-society.org/

1 0

pygame 1.9.4 released
by René Dudfield July 19, 2018

July 19, 2018

[image: pygame 1.9.4] <https://www.pygame.org/wiki/about> pygame 1.9.4 has been released into the wild! TLDR; Some highlights. - python 3.7 support. - beta pypy <https://www.pypy.org/> support. See Are we pypy yet? <https://github.com/pygame/pygame/issues?q=is%3Aopen+is%3Aissue+milestone%3A…> . - pygame.draw fixes - pygame.math is not experimental anymore. Speedups and bugfixes. - Debian, Mac homebrew, mac virtualenv, manylinux and other platform fixes. - documentation fixes, jedi support for type ahead in editors like VSCode and VIM. - Surface.blits for blitting many surfaces at once more quickly. Thanks A very special thanks to the people who have volunteered commits to pygame since the last release. In alphabetical order... Adam Di Carlo (@adicarlo <https://github.com/adicarlo>) | Christian Bender ( @christianbender <https://github.com/christianbender>) | Don Kirkby ( @donkirkby <https://github.com/donkirkby>) | endolith (@endolith <https://github.com/endolith>) | hjpotter92 (@hjpotter92 <https://github.com/hjpotter92>) | Ian Mallett (@imallett <https://github.com/imallett>) | Lenard Lindstrom (@llindstrom <https://github.com/llindstrom>) | Mathias Weber (@mweb <https://github.com/mweb>) | Matti Picus (@mattip <https://github.com/mattip>) | Nicholas Tollervey (@ntoll <https://github.com/ntoll>) | (@orangudan <https://github.com/orangudan>) | Raymon Skjørten Hansen (@raymonshansen <https://github.com/raymonshansen>) | René Dudfield (@illume <https://github.com/illume>) | Stefan Bethge (@kjyv <https://github.com/kjyv>) | Stuart Axon (@stuaxo <https://github.com/stuaxo>) | Thomas Kluyver (@takluyver <https://github.com/takluyver>) | Tobias Persson (@Anisa <https://github.com/Anisa>) I'm probably missing some people, and also missing some people who contributed in other ways. For example, in discussions, issue reports, helping out on the wiki, the website, and for helping others in the community, and providing good vibes. So whilst the commits are easy to use to make a list of people to thank, it's not inclusive of everyone who deserves thanks. More details. #451 <https://github.com/pygame/pygame/pull/451> #460 <https://github.com/pygame/pygame/pull/460> #467 <https://github.com/pygame/pygame/pull/467> #468 <https://github.com/pygame/pygame/pull/468> #469 <https://github.com/pygame/pygame/pull/469> #470 <https://github.com/pygame/pygame/pull/470> #444 <https://github.com/pygame/pygame/pull/444> link to help pages when compile fails. #443 <https://github.com/pygame/pygame/pull/443> In set_error get_error tests ignore first error. Could be anything. #442 <https://github.com/pygame/pygame/pull/442> Freetype requires pkg-config instead of freetype-config now. #439 <https://github.com/pygame/pygame/pull/439> Surface.blits #435 <https://github.com/pygame/pygame/pull/435> Adding pypy builds for Mac on travis. #432 <https://github.com/pygame/pygame/pull/432> Appveyor pypy and pypy3 windows 32bit. #431 <https://github.com/pygame/pygame/pull/431> Implement object alloc caching for rect.c to improve on pypy. #427 <https://github.com/pygame/pygame/pull/427> PixelArray.close(), with PixelArray(surf) as px, context manager. #426 <https://github.com/pygame/pygame/pull/426> Skip tests that rely on arrinter and pythonapi on pypy. #420 <https://github.com/pygame/pygame/pull/420> pypy didn't like tp_dictoffset hack in events. Make our own setter, getter. #418 <https://github.com/pygame/pygame/pull/418> draw.aaline should work with ARGB surfaces (like on mac). #416 <https://github.com/pygame/pygame/pull/416> Vector cleanup #415 <https://github.com/pygame/pygame/pull/415> So virtualenv gets a focused window on Mac too. #414 <https://github.com/pygame/pygame/pull/414> Mac Travis homebrew fix #413 <https://github.com/pygame/pygame/pull/413> Jedi confused by pygame imports. Make it happy. #408 <https://github.com/pygame/pygame/pull/408> pygame.transform.threshold tests, keyword arguments, docs. #403 <https://github.com/pygame/pygame/pull/403> pygame.math.Vector2/3 not experimental #398 <https://github.com/pygame/pygame/pull/398> Clean up _camera_vidcapture.py unused code, and document a bit. #394 <https://github.com/pygame/pygame/pull/394> Add pitch bend to MIDI library #392 <https://github.com/pygame/pygame/pull/392> Add pypy builder to travis ci, and allow it to fail. #391 <https://github.com/pygame/pygame/pull/391> ppc64le and other Debian fixes #389 <https://github.com/pygame/pygame/pull/389> pygame.draw.circle with a thickness had a weird moiré pattern. #387 <https://github.com/pygame/pygame/pull/387> test python 3.7 on travis CI. #386 <https://github.com/pygame/pygame/pull/386> python 3.7 fixes. #384 <https://github.com/pygame/pygame/pull/384> pygame.display doc fixes. #381 <https://github.com/pygame/pygame/pull/381> import rect.inflate docs. #363 <https://github.com/pygame/pygame/pull/363> Fix several typos, and improve grammar in the introduction. #361 <https://github.com/pygame/pygame/pull/361> Add unit test for some key functions. #360 <https://github.com/pygame/pygame/pull/360> update math.c for pypy. #357 <https://github.com/pygame/pygame/pull/357> add UYVY support for better linux camera support. #356 <https://github.com/pygame/pygame/pull/356> Fix aaellipse artifacts 703350f <https://github.com/pygame/pygame/commit/703350f68182641fe72ef1f41d81998fb6d…> Update Rect slicing for Python 3 6d0e97a <https://github.com/pygame/pygame/commit/6d0e97a38b5d2d549f1fee8b912a072731e…> bug fix for freetype.Font.render_to() #78 <https://github.com/pygame/pygame/issues/78> Add environment PYGAME_EXTRA_BASE to add an extra base directory to the start of the search path. #77 <https://github.com/pygame/pygame/issues/77> Build alsa libs ourselves for manylinux builds. #76 <https://github.com/pygame/pygame/issues/76> Docs fixup.

1 0

EuroPython 2018: Find a new job at the conference
by M.-A. Lemburg July 18, 2018

July 18, 2018

We’d like to draw your attention to our job board, with plenty of job ads from our sponsors: * EuroPython 2018 Job Board * https://ep2018.europython.eu/en/sponsor/job-board/ We will also send out job ad emails to attendees who have opt’ed in to receiving these emails. If you are interested, please log in, go to your profile and enable the recruiting email option in the privacy section: https://ep2018.europython.eu/accounts/profile/ Note that we will not give your email addresses to sponsors, but only send out these emails on behalf of them. 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/176025102537/europython-2018-find-a-new-job… Tweet: https://twitter.com/europython/status/1019620582445416450 Enjoy, -- EuroPython 2018 Team https://ep2018.europython.eu/ https://www.europython-society.org/

1 0

PyCA cryptography 2.3 released
by Paul Kehrer July 18, 2018

July 18, 2018

PyCA cryptography 2.2.2 has been released to PyPI. cryptography includes both high level recipes and low level interfaces to common cryptographic algorithms such as symmetric ciphers, message digests, and key derivation functions. We support Python 2.7, Python 3.4+, and PyPy. Changelog (https://cryptography.io/en/latest/changelog/#v2-3): * SECURITY ISSUE: finalize_with_tag() allowed tag truncation by default which can allow tag forgery in some cases. The method now enforces the min_tag_length provided to the GCM constructor. * Added support for Python 3.7. * Added extract_timestamp() to get the authenticated timestamp of a Fernet token. * Support for Python 2.7.x without hmac.compare_digest has been deprecated. We will require Python 2.7.7 or higher (or 2.7.6 on Ubuntu) in the next cryptography release. * Fixed multiple issues preventing cryptography from compiling against LibreSSL 2.7.x. * Added get_revoked_certificate_by_serial_number for quick serial number searches in CRLs. * The RelativeDistinguishedName class now preserves the order of attributes. Duplicate attributes now raise an error instead of silently discarding duplicates. * aes_key_unwrap() and aes_key_unwrap_with_padding() now raise InvalidUnwrap if the wrapped key is an invalid length, instead of ValueError. -Paul Kehrer (reaperhulk)

1 0

learning by contributing to FLOSS (and pygame in specific)
by René Dudfield July 18, 2018

July 18, 2018

Hello, I'm looking for a small group of 10-30 people who are interested in contributing to the pygame project as part of a class or user group meeting. Rather than a normal user group meeting or class, it could be: "contribute to an open source project". Be in touch!? Let's do it! :) *Why?* (teaching by helping people contribute to FLOSS projects.) Because you don't learn karate from a book. Builds social connections and skills. Portfolio, and evidence of talent. Sort of fun and different compared to a talks night at a user group. *Why pygame?* (rather than some other project) Because I want to do this with my pet project. It's sort of fun compared to some topics (better than watching paint dry at least). Because it's sort of well known project (millions of users). ... with almost zero full time or even part time developers (that's why it's called pygame zero). Because I will help before and during the class(es)/session(s), and have resources and issues prepared. *[hey! you could totally do this with your own pet projects too!]* *How will a gathering work?* *The goal*: At the end of the gathering, people will have learned how a FLOSS project is done, submitted a PR, and have a big thank you posted on the website. A session could run like this: 1. A short lightning talk can be done on what's happening by someone on how to write a unit test, and what is a github issue (slides can be made available). 2. A number of topics will be presented to choose from. These will be 'low hanging fruit' issues. Like, "write a test for a draw rectangle functions". 3. People will split off into small groups of 2-4 people. Each choosing an issue. Probably beginners and experts will be mixed together. 4. Project developers will be available via web chat (Discord) (or in person perhaps if it's where the developers live...). 5. results will be pasted into issues, and perhaps even pull requests made. 6. At the end one person from each group will show off what they've done and experienced to the group. (several short talks) [Hrmm... you may be thinking that this sort of sounds exactly like a Dojo (shout out to London Python Dojo) or mini conference sprint format(shout out to pypy!). Yop.) If anyone wants to do this with me please be in touch to get this going! I will announce when it's happening so people can drop by online too if they want. cheers,

1 0

[ANN] - Skyline v1.2.2-stable-luminosity
by Gary Wilson July 17, 2018

July 17, 2018

For those interested in anomaly detection and deflection in streamed time series data. I would like to announce a new release of Skyline v1.2.2 - https://github.com/earthgecko/skyline/releases/tag/v1.2.2-stable-luminosity What is Skyline? ---------------- Skyline v1.2.2 - For those interested in anomaly detection and deflection in streamed time series data. Anomaly deflection. The obvious next evolution in the use of all the anomaly detection data? Skyline is a Python based anomaly detection/deflection stack that analyses, anomaly detects, deflects, fingerprints and learns vast amounts of streamed time series data. - Skyline ingests streamed metric time series data - skyline/horizon - Skyline uses a ```CONSENSUS``` of 3-sigma algorithms to detect anomalies on batch processed, streamed metric time series data - skyline/analyzer - anomaly detector - It handles large and small seasonality in the data - skyline/mirage - anomaly deflector and detector - You can train it on what is NOT anomalous and it learns - skyline/ionosphere - anomaly deflector - It records all your anomalies - skyline/panorama - anomaly memory - It shows you all your data - skyline/webapp - anomaly view Seeing as we desire our metrics to be not anomalous most of the time and we want to know when they ARE anomalous and given the fact that we try and build systems that try to behave within not anomalous bounds so they perform well, due to this we have: - A lot of metric time series data that are not anomalous most of the time. - A lot of data to train a system on what is NOT anomalous given a time series data set, rather than simply focusing on what is anomalous, also focusing on what is not anomalous. To achieve this Skyline implements a novel time series similarities comparison algorithm and a boundary layers methodology that generates fingerprints of time series data using the sum of the values of features of the time series which have been extracted using the tsfresh features extraction package - https://github.com/blue-yonder/tsfresh and evaluation against boundary layer algorithms to determine whether a 3-sigma triggered anomaly is actually a normal, known pattern in the data. The Skyline-Ionosphere-Tsfresh Time Series Similairities Comparison Algorithm - SITTSSCA first coined here :) compares the generated fingerprints of the two time series and can determine if they closely resemble each other in terms of: - of the amount of "power/energy", range and "movement" there is within the time series data set somewhat like RMS - Erol Kalkan from United States Geological Survey, “Another approach to compute the differences between two time series is moving window root-mean-square. RMS can be run for both series separately. This way, you can compare the similarities in energy (gain) level of time series. You may vary the window length for best resolution.” (https://www.researchgate.net/post/How_can_I_perform_time_series_data_simila…) http://stackoverflow.com/questions/5613244/root-mean-square-in-numpy-and-co… The Skyline-Ionosphere-Tsfresh Time Series Similairities Comparison Algorithm compares how close the fingerprint values are as a percentage and varying this percentage variable will either focusing the algorithm with greater precision the closer to 0% the parameter gets, the perfect match (or possibly a mirror match too - unkonwn/untested) or it will incrementally increase the tolerance as the percentage variable increases and the matching will become less and less reliable. However there is a sweet spot and here SITTSSCA works extremely well :) Added to SITTSSCA is an optional layer of simple boundary algorithms that are user defined during the operator training interaction with Skyline, where the operator augments the SITTSSCA results with boundaries that describe the expected norm within the time series. Very similar to being able to describe the Active Brownian Motion of a time series - https://github.com/blue-yonder/tsfresh/pull/143#issuecomment-272314801 This results in an anomaly detection/deflection system which enables the user to very simply label time series and train Skyline on the peaks and troughs and the expected Active Brownian Motion or best effort thereof. However it takes a little effort on your part to train Skyline, however with the effort, Skyline is very good at doing anomaly detection and deflection. With your help. There is no easy anomaly detection or deflection, but there is some reward with a bit of effort. To learn more... ---------------- Project page -> https://github.com/earthgecko/skyline Documentation -> https://earthgecko-skyline.readthedocs.io/en/latest/index.html With the hope Skyline can make the universe a bit less anomalous. Regards Gary

1 0