With JyNI alpha 5, I proudly announce the first version of JyNI that
also runs on Windows.
JyNI is a layer that allows Jython to load native CPython extensions.
Most notably ctypes and NumPy are already workable (core functionality).
Take a look at
or go directly to the release:
Binaries are provided for Linux, OS X and Windows.
It should in principle also work on other POSIX platforms.
>From JyNI alpha 4 onwards, some NumPy support is available.
For JyNI alpha 5 featuring Windows support, we explicitly asserted that
NumPy works on Windows equally well as on Linux and OS X,
i.e. up to known limitations.
For details about NumPy support see
Google Summer of Code
JyNI alpha 5 was mainly developed within a Google Summer of Code project:
https://summerofcode.withgoogle.com/projects/#4931062149939200http://gsoc2017-jyni.blogspot.de for details.
What comes next?
The Python C API is not yet fully supported. A major goal for the next
release is to add support for the buffer protocol, which is currently
blocking support for SciPy and various other extensions.
On behalf of Twisted Matrix Laboratories, I am honoured to announce the release of Twisted 17.9.0!
The highlights of this release are:
- More Python 3 porting, including twisted.mail.imap4, twisted.python.shortcut, twisted.python.rebuild, twisted.web.sux, twisted.web.microdom, and a ton of bugs and inconsistencies fixed.
- twistd on Python 3 now supports the dns, inetd, portforward, procmon, socks, and words plugins.
- HTTP/1.1 and HTTP/2 OPTIONS * request support in Twisted Web
- twist web now accepts the argument --add-header, which can be used to set things like HSTS headers without custom code
- Improvements to IMAP4 behaviour and several logic bugfixes
- Removal of outdated documentation and updates to make them work on Python 3
- Over 70 closed tickets overall.
For more information, check the NEWS file (link provided below).
You can find the downloads at <https://pypi.python.org/pypi/Twisted <https://pypi.python.org/pypi/Twisted>> (or alternatively <http://twistedmatrix.com/trac/wiki/Downloads <http://twistedmatrix.com/trac/wiki/Downloads>>). The NEWS file is also available at <https://github.com/twisted/twisted/blob/twisted-17.9.0/NEWS.rst <https://github.com/twisted/twisted/blob/twisted-17.9.0/NEWS.rst>>.
Many thanks to everyone who had a part in this release - the supporters of the Twisted Software Foundation, the developers who contributed code as well as documentation, and all the people building great things with Twisted!
Amber Brown (HawkOwl)
on behalf of the PyInstaller development team I'm happy to announce
PyInstaller 3.3. Most important change for this release is the support
for Python 3.6.
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
=== Installation ===
PyInstaller can be installed from PyPi using
pip install pyinstaller
=== Important Changes ===
* Add Support for Python 3.6! Many thanks to xiovat! (#2331, #2341)
* New command line options for adding data files (``--datas``, #1990) and
binaries (``--binaries``, #703)
* Add command line option '--runtime-tmpdir'.
* Bootloaders for Windows are now build using MSVC and statically linked with
the run-time-library (CRT). This solved a lot of issues related to .dlls
being incompatible with the ones required by ``python.dll``.
* Bootloaders for GNU/Linux are now officially no LSB binaries. This was
already the case since release 3.1, but documented the other way round. Also
the build defaults to non-LSB binaries now. (#2369)
* We improved and stabilized both building the bootloaders and the continuous
integration tests. See below for details. Many thanks to all who worked on
* To ease solving issues with packages included wrongly, the html-file with a
cross-reference is now always generated. It's visual appearance has been
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
I’m happy to announce the availability of a new mailing list, with the mission of providing security announcements to the Python community from the Python Security Response Team (PSRT):
You can sign up in the usual Mailman way:
This joins our suite of security related forums. As always, if you believe you’ve found a security issue in Python, you should contact the PSRT directly and securely via:
For more information on how you can contact us, see:
We also have a public security-focused discussion mailing list that you can subscribe and contribute to.
Please don’t report security vulnerabilities here, since this is a publicly archived mailing list. We welcome you to collaborate here to help make Python and its ecosystem even more secure than it already is.
Once a security vulnerability is identified and fixed, it becomes public knowledge. Generally, these are captured in a ReadTheDocs site for posterity:
This new security-announce mailing list fills a void — one-way communication about security related matters from the PSRT back to the community. This is an area that we’ve not done a great job at, frankly, and this new announcement list is intended to improve that situation. The PSRT will use this low traffic, high value forum as the primary way the PSRT will communicate security issues of high importance back to the wider Python community. All follow-ups to postings to this list are redirected to the security-sig mailing list.
-Barry (on behalf of the PSRT)
PyDev 6.0.0 Release Highlights
*Important* PyDev now requires Java 8 and Eclipse 4.6 (Neon) onwards.
- PyDev 5.2.0 is the last release supporting Eclipse 4.5 (Mars).
- The *list of packages* installed in the interpreter is shown in the
IDE (supports either *pip* or *conda*).
- It's now possible to *install/uninstall* packages using either *pip*
or *conda* directly from the IDE.
- Provides a way to *load variables* if interpreter is from a *conda
environment* (Load conda env vars before run configuration).
- A default string substitution variable named *PY* is now created
with the major and minor version of the created interpreter.
- It's now possible to configure a project to always use a grammar
compatible with the interpreter version (default for new projects --
- *Subword* navigation is now available (and enabled by default -- can
be customized at *PyDev > Editor*).
- Changed default config for minimap (smaller and not showing
elements -- can be customized at *PyDev > Editor > Overview Ruler
- Code completion no longer active in comments in last line of editor
- Fix find_module signature (patch by James Blackburn).
- Fix qt_loader to support *PEP 302* correctly.
- Fix in matplotlib_options from ipython (*#PyDev-779*).
- When show all uppercase references is used as a filter, only digits
shouldn't be filtered out in variables view (#PyDev-794).
- Added setting to search *PyLint* installed in interpreter (*#PyDev-811*
- It's possible to edit a run configuration from dialog to select tests
to run (Ctrl+F9) (patch by *Robert Gomulka*).
- Test(s) name is shown in the run configuration (patch by *Robert
Gomulka* -- *#PyDev-840*).
- The modules that are known to be third party or system modules in the
PyDev configuration are passed to *isort*.
- Proper support for *isort:skip* and *isort:skip_file*.
- Internal isort caches properly being cleared between invocations
(fix for case where changes to config were not reflected in isort).
- Fix to properly interrupt infinite loop in the Interactive Console (
- Fix issue where user could do a drag n drop in system libs which
could put an entry below another entry, which actually removed
it from the
- Fix where *runfile* was not available on *interactive debugger* when
python-future is installed (*#PyDev-845*).
- Fix NullPointerException on code-completion.
- mutagen added to forced builtins by default (*#PyDev-819*).
What is PyDev?
PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and
It comes with goodies such as code completion, syntax highlighting, syntax
analysis, code analysis, refactor, debug, interactive console, etc.
Details on PyDev: http://pydev.org
Details on its development: http://pydev.blogspot.com
What is LiClipse?
LiClipse is a PyDev standalone with goodies such as support for Multiple
cursors, theming, TextMate bundles and a number of other languages such as
It's also a commercial counterpart which helps supporting the development
Details on LiClipse: http://www.liclipse.com/
PyDev - Python Development Environment for Eclipse
PyVmMonitor - Python Profiler
The Python build factories have been busy the last several weeks preparing
our fall lineup of releases. Today we are happy to announce three
additions: 3.6.3rc1, 3.7.0a1, and 3.3.7 final, which join last weekend's
2.7.14 and last month's 3.5.4 bug-fix releases and 3.4.7 security-fix
1. Python 3.6.3rc1 is the first release candidate for Python 3.6.3, the next
maintenance release of Python 3.6. While 3.6.3rc1 is a preview release and,
thus, not intended for production environments, we encourage you to explore
it and provide feedback via the Python bug tracker (https://bugs.python.org).
3.6.3 is planned for final release on 2017-10-02 with the next maintenance
release expected to follow in about 3 months. You can find Python 3.6.3rc1
and more information here:
2. Python 3.7.0a1 is the first of four planned alpha releases of Python 3.7,
the next feature release of Python. During the alpha phase, Python 3.7
remains under heavy development: additional features will be added
and existing features may be modified or deleted. Please keep in mind
that this is a preview release and its use is not recommended for
production environments. The next preview release, 3.6.0a2, is planned
for 2017-10-16. You can find Python 3.7.0a1 and more information here:
3. Python 3.3.7 is also now available. It is a security-fix source-only
release and is expected to be the final release of any kind for Python
3.3.x before it reaches end-of-life status on 2017-09-29, five years after
its initial release. Because 3.3.x has long been in security-fix mode,
3.3.7 may no longer build correctly on all current operating system
releases and some tests may fail. If you are still using Python 3.3.x,
we **strongly** encourage you to upgrade now to a more recent, fully
supported version of Python 3. You can find Python 3.3.7 here:
nad(a)python.org -- 
Announcing wxPython 4.0.0b2
Pip: ``pip install wxPython==4.0.0b2``
Changes in this release include the following:
* Added a deprecated compatibility helper for wx.CustomDataFormat.
* Transfer ownership of the wx.EvtHandler object when pushing/popping
them, and also for Set/RemoveEventHandler. (#443)
* Add missing wx.VScrolledWindow methods listed in the docs as
deprecated but still present. (#441)
* Fixed copy/paste error in wx.BusyInfo.__exit__ (#449)
* Added new tool wxget, (a minimal wx implementation of wget)
* Added new tools wxdocs and wxdemos to launch the respective items,
fetching and unpacking as required. (#437)
* Fixes to ensure that the locale message catalogs are included in the
release files. (#464)
* Fix wx.ListCtrl.SetItemData to check that the data value is not out
of the range of a C long. (#467)
* Changed the default port on *nix builds to be GTK3. The new
``--gtk2`` flag for build.py can be used to force a build for GTK2
instead, and the ``--gtk3`` flag still exists, but defaults to True
unless ``--gtk2`` is specified. Please note that there is currently
no auto-detection of whether GTK3 is available or not, so if you
know you need to build for GTK2 then you need to use the build flag,
and there is currently no way to specify that flag for builds
performed by pip. (#431)
* Fix parameter names in Toolbar.AddTool methods to be
* Remove inconsistent GetVirtualSize method in ScrolledWindow and let
it be inherited from wx.Window instead. (#474)
* Fix crashing bug caused by importing a module that reinitializes the
wxModule system after having imported wxpyTag. (#468)
* Fix missing methods in various DataObject classes. (They were
actually accidentally marked "private" when they should have been
* Add missing ListCtrl.DeleteAllColumns. (#486)
* Various fixes in the demo.
* Fixed improper initial scale factor in wx.lib.agw.speedmeter
* Fix for calls to wx.Notebook.HitTest calling the wrong instance
(base class version) of the method. (#499)
* Add wx.Simplebook class.
* Fix exception in wx.lib.agw.customtreectrl when calling
SortChildren. (#463, #500)
* Fix missing imports needed for drawing the legend in
* Fix other instances of list.sort using old cmp-style ordering
* Update SizedControls to do a sanity check on the parent's sizer, as
GetSizer can return None for SizedParent under certain
circumstances, such as when AUI reparents the control during pane
movement. (#523, #537)
* Added Vagrant configs for Fedora 23 and Fedora 26, and dropped
Fedora 24. Wheels built on F23 can also be used on F24 and F25, and
F26 adds Python 3.6 support.
* Fix bitwise OR bug in wx.lib.agw.aui.framemanager. (#493)
* Fix bugs in wx.lib.plot when saving file. (#526)
* Fix integer division bug in ultimatelistctrl. (#528)
* Fix bug in wx.SearchCtrl.SetCancelBitmap (#532)
* Fixed property grid SetPropertyValue method to not truncate floating
point values to integers, and a couple other possible incorrect
What is wxPython?
wxPython is a cross-platform GUI toolkit for the Python programming
language. It allows Python programmers to create programs with a
robust, highly functional graphical user interface, simply and
easily. It is implemented as a set of Python extension modules that
wrap the GUI components of the popular wxWidgets cross platform
library, which is written in C++. Supported platforms are Microsoft
Windows, Mac OS X and macOS, and Linux or other unix-like systems with
GTK2 or GTK3 libraries. In most cases the native widgets are used on
each platform to provide a 100% native look and feel for the
What is wxPython Phoenix?
wxPython's Project Phoenix is a new from-the-ground-up implementation
of wxPython, created with the intent of making wxPython “better,
stronger, faster than he was before.” In other words, this new
implementation is focused on improving speed, maintainability and
extensibility of wxPython, as well as removing most of the cruft that
had accumulated over the long life of Classic wxPython.
The project has been in development off and on, mostly behind the
scenes, for many years. For the past few years automated snapshot
builds have been available for those adventurous enough to try it, and
many people eventually started using the snapshots in their projects,
even for production releases. While there are still some things on
the periphery that need to be completed, the core of the new wxPython
extension modules which wrap the wxWidgets code has been stable for a
long time now.
Due to some things being cleaned up, reorganized, simplified and
dehackified wxPython Phoenix is not completely backwards compatible
with wxPython Classic. This is intended. In general, however, the API
differences tend to be minor and some applications can use Phoenix
with slight, or even no modifications. In some other cases the
correct way to do things was also available in Classic and it's only
the wrong way that has been removed from Phoenix. For more
information there is a Migration Guide document available at:
The new wxPython API reference documentation, including all
Python-specific additions and customizations, and docs for the wx.lib
package, is located at: https://docs.wxpython.org/