Hi Python Software Foundation team -
Hope this note finds you well. Today, open source language automation provider, ActiveState announced a new commercial support offering for Python 2 beyond its impending end of life date.
Please find the press release below.
Let me know if there’s any additional information that I can provide.
ActiveState Offers Extended Support for Python 2 Beyond EOL
Open Source Leader Provides Enterprises with Support Safety Net for Python 2 Applications
VANCOUVER, British Columbia – July 16, 2019 – ActiveState today announced a commercial support offering that includes security fixes for Python 2 beyond its impending End of Life (EOL) date.
Community support for Python 2 will expire on Jan. 1, 2020. After that date, the Python core team and many third-party package authors will no longer be supporting, maintaining or updating any of their Python 2.x releases. Organizations with Python 2 deployments are faced with a key decision: whether to rewrite, migrate or maintain their existing applications. No matter which option they choose, the safety net of a commercial support provider can help reduce risk and save developer time.
Click to Tweet<https://ctt.ac/f6S7f>: @ActiveState offers commercial support for Python 2 beyond EOL. Get security fixes for your Python 2 applications after community support expires on Jan. 1 2020 here: http://bit.ly/2XIsXqM #python
The ActiveState offering includes:
● Support for both the Python 2 core language and standard libraries, as well as the third-party, open source packages, libraries and modules listed in the Python Package Index (PyPI).
● Backported security fixes implemented in Python 3 core language code and third-party packages.
● Resolution of Python 2 specific issues by ActiveState’s Python experts in conjunction with the Python community.
ActiveState has more than 20 years of experience in supporting Python for enterprises. Commercial Python support is available today for both Python 2 and Python 3 developers. Extended support for Python 2 begins on Jan. 1, 2020. For more information about the support ActiveState offers, click here.<http://bit.ly/2XIsXqM>
Jeff Rouse, vice president, product management, said: “The majority of Python deployments are currently Python 2 applications, services and scripts. We’ve spoken to many organizations that are worried about the impending Python 2 EOL. Universally, they’re concerned about inevitable code vulnerabilities and the impact they’ll have on application security. ActiveState’s commercial support offering is designed to provide these organizations with peace of mind.”
ActiveState helps enterprises scale securely with open source languages and gives developers the kinds of tools they love to use. More than 2 million developers and 97 percent of Fortune 1,000 enterprises use ActiveState to support mission-critical systems and speed up software development while enhancing oversight and increasing quality. https://www.activestate.com
Jessica M. Pasko
Nadel Phelan, Inc.
This is a second call for talk proposals for PyCon ZA 2019. While
we've already received several great talk proposals, we still have a
number of open talk slots and are thus keen to see further talk
PyCon ZA 2019 will take place on the 10th & 11th of October at The
Wanders Club in Illovo, Johannesburg, South Africa (location link:
https://www.thewanderersclub.co.za/contact/). There will also be
tutorial sessions the day before the conference (the 9th) and we will
hold sprints on the 12th & 13th of October.
We are currently accepting proposals for talks. 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 2019.
The presentation slots will be 30 minutes long, with an additional 10
minutes for discussion at the end. 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.
PyCon ZA offers limited financial assistance for attendees. To apply
for assitance, please follow the instructions at
https://za.pycon.org/tickets/financial-aid/ . Requests for assistance
will be reviewed on a case-by-case basis.
I've got a gmail account. Why haven't I become cool?
I'm proud to release version 1.6.1 of Roundup which has been possible
due to the help of several contributors. This release is a
bug fix release. If you are upgrading from a release earlier than
1.6.0 it includes important security enhancements, so make sure to
<http://www.roundup-tracker.org/docs/upgrading.html>`_ to bring your
tracker up to date.
- doc updates. Link rot fixed and some grammar changes.
'Provisional User' config example fixed. Issue tracker is
now https. (John Rouillard)
- issue2550994: avoid breakage caused by use of backports of Python 3
configparser module to Python 2. (Joseph Myers)
- issue2551023: Fix CSRF headers for use with wsgi and cgi. The
env variable array used - separators rather than _. Compare:
HTTP_X-REQUESTED-WITH to HTTP_X_REQUESTED_WITH. The last is
correct. Also fix roundup-server to produce the latter form. (Patch
by Cedric Krier, reviewed/applied John Rouillard.)
- issue2551035 - fix XSS issue in wsgi and cgi when handing url not
found/404. Reported by hannob at
https://github.com/python/bugs.python.org/issues/34, issue opened by
- issue2551029: Jinja2 template install error. Remove config.ini
from templates to make sure that roundup-admin install writes a new
default config.ini based on configuration.py.
- issue2551029: Jinja2 template install error. Handle issue with
template's config.ini not getting updated. Provide an alternate
file: config_ini.ini for required config settings that are merged
into the default values producing an up to date config.ini on
If you're upgrading from an older version of Roundup you *must* follow
the "Software Upgrade" guidelines given in the maintenance documentation.
Roundup requires python 2.7 or later (but not 3+) for correct operation.
To give Roundup a try, just download (see below), unpack and run::
Release info and download page:
Source and documentation is available at the website:
Mailing lists - the place to ask questions:
Roundup is a simple-to-use and -install issue-tracking system with
command-line, web and e-mail interfaces. It is based on the winning design
from Ka-Ping Yee in the Software Carpentry "Track" design competition.
Note: Ping is not responsible for this project. The contact for this
project is richard(a)users.sourceforge.net.
Roundup manages a number of issues (with flexible properties such as
"description", "priority", and so on) and provides the ability to:
(a) submit new issues,
(b) find and edit existing issues, and
(c) discuss issues with other participants.
The system will facilitate communication among the participants by managing
discussions and notifying interested parties when issues are edited. One of
the major design goals for Roundup that it be simple to get going. Roundup
is therefore usable "out of the box" with any python 2.7+ (but not 3+)
installation. It doesn't even need to be "installed" to be operational,
though an install script is provided.
It comes with five issue tracker templates
* a classic bug/feature tracker
* a minimal skeleton;
* a more extensive devel tracker for bug/features etc.
* a responsive version of the devel tracker
* a jinja2 based template based on devel
and can use any of four database back-ends (anydbm, sqlite, mysql and
Wing Python IDE 7.0.4 has been released. Some of the highlights of this
Fix debugging notebooks with newer Jupyter versions
Fix setting up a Django project with the default Python Executable
Don't lose retained Debug I/O buffers after 60 seconds
Avoid several incorrect code warnings
Fix refactoring or finding points of use in code that has type hints
Fix Move Program Counter in remote files
Fix remote searching and Find Uses to include files that are not
open in the editor
Avoid displaying spurious Disk File is Newer dialogs when saving
Fix comparing two directories
Avoid hanging up in file comparisons with large difference blocks
Fix several problems in the extension scripting API
Fix many other bugs
You can obtain this release with Check for Updates in Wing 7's Help menu
or download it now:
**New in Wing 7**
Wing 7 introduces an improved code warnings and code quality inspection
system that includes built-in error detection and tight integration with
Pylint, pep8, and mypy. This release also adds a new data frame and
array viewer, a MATLAB keyboard personality, easy inline debug data
display with Shift-Space, improved stack data display, support for PEP
3134 chained exceptions, callouts for search and other code navigation
features, four new color palettes, improved bookmarking, a high-level
configuration menu, magnified presentation mode, a new update manager,
stepping over import internals, simplified remote agent installation,
and much more.
For details see What's New in Wing 7: https://wingware.com/wingide/whatsnew
**Try Wing 7 Now!**
Wing 7 is a an exciting new step for Wingware's Python IDE product line.
Find out how Wing 7 can turbocharge your Python development by trying it
Download Wing 7.0.4: https://wingware.com/downloads
Wing 7 installs side by side with earlier versions of Wing, so there is
no need to remove old versions in order to try it. Wing 7 will read and
convert your old preferences, settings, and projects. Projects should be
saved to a new name since earlier versions of Wing cannot read Wing 7
See Upgrading https://wingware.com/doc/install/upgrading for details and
Migrating from Older Versions https://wingware.com/doc/install/migrating
for a list of compatibility notes.
I am extremely excited to announce that VisPy 0.6 has finally been released!
# What is it?
VisPy is a wrapper around OpenGL and provides an easy way to make
scientific visualizations using high performance GPU-based interfaces.
It provides "Visual" objects to provide builtin shapes, images, meshes,
cameras, volumes, and text elements.
VisPy supports Linux, Windows, and Mac. It has been shown to run on
Raspberry Pi's as well.
- Update PyQt5/PySide2 to use newer GL API
- Update to PyQt5 as default backend
- New Cython-based text rendering option
- New WindbarbVisual
- Improved JupyterLab/Notebook widget (experimental)
- Fix various memory leaks
- Various optimizations and bug fixes
This release includes new cython extensions, optional/experiment Jupyter
widgets, and some previously bundled dependencies changed to external
dependencies. This means that although we've added new features, we've
also increased the chance of build issues. That's why this is also the
first release that we're providing binary wheels on PyPI to make
installation easier (especially for Windows users). As always, VisPy is
also available with conda from conda-forge. See the installation
instructions for more info
If you encounter any issues please file them on GitHub.
# Python 2 Support
VisPy 0.6 will be the last minor release supporting Python 2. We will
still make bug releases for 0.6, if needed, until the end of the year.
You may have noticed that VisPy's releases are few and far between. I
hope to improve this in the future as build systems become more stable
and VisPy's code gets cleaned up.
That said, VisPy has a lot of room for new contributors and we welcome
any and everyone who wants to contribute. You don't need OpenGL
experience and can contribute with documentation updates, bug fixes, new
features, reviewing pull requests and issues, or answering questions on
Gitter Chat: https://gitter.im/vispy/vispy
on behalf of the PyInstaller development team I'm happy to announce
Thanks for all those who contributed questions, bug-reports or
=== 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
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
=== 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 ===
* More then 30 hooks added, more then 10 hooks fixed or improved.
* More then 20 bugs fixed.
* Python 3.4 is no longer tested, since this version is
The full changelog for this release can be found at:
=== 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
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Goebel Consult, Landshut