What is Flake8?
Flake8 is a command-line tool to help developers enforce a style guide
for their project. It uses pycodestyle to enforce PEP 8's style guide,
pyflakes to lint the code base, and mccabe to provide complexity
What's new in 3.0.0b1?
See our release notes:
You can install 3.0.0b1 from PyPI, simply use either:
pip install flake8==3.0.0b1
pip install --pre flake8
This breaks my plugin
We're tracking which plugins are broken by this release on
https://gitlab.com/pycqa/flake8/issues/149 and I am submitting pull
requests to help those authors adapt their plugins for 2.x and 3.x
Please test this version and report any problems you find with it.
* **Important** PyDev now requires Java 8 and Eclipse 4.5 onwards.
* PyDev 4.5.5 is the last release supporting Java 7 and Eclipse 3.8.
* See: http://www.pydev.org/update_sites/index.html for the update site of
older versions of PyDev.
* See: the **PyDev does not appear after install** section on
http://www.pydev.org/download.html for help on using a Java 8 vm in Eclipse.
* The pytest integration was redone and should now work properly with the
* Properly showing output of tests in PyUnit view.
* Improved dealing with items filtered through Ctrl+F9.
* Better support for xdist (no longer reporting that the session finished
when only a slave finished).
* Reporting skipped items as "skip" and not "ok".
* Properly showing running tests on PyUnit view.
* Not using tokenize.open() in Python 3.2 for the execfile custom
* Expand and collapse keybindings changed to use the Numpad entries (so
that they don't override the add/subtract used for zooming). #PyDev 695.
* The hover in PyDev has an implementation which is now more flexible and
easier to extend in plugins (patch by Mark A. Leone).
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
I'm pleased to announce a major update of the RSFile I/O Library:
RSFile provides drop-in replacements for the classes of the*io *module,
and for the *open()* builtin.
Its goal is to provide a cross-platform, reliable, and comprehensive
synchronous file I/O API, with advanced
features like fine-grained opening modes, shared/exclusive file record
locking, thread-safety, cache synchronization,
file descriptor inheritability, and handy stat getters (size, inode,
Possible use cases for this library: concurrently writing to logs
without ending up with garbled data,
manipulating sensitive data like disk-based databases, synchronizing
processes when multiprocessing semaphores aren't an option...
Unix users might particularly be interested by the workaround that this
library provides, concerning
the weird semantic of fcntl() locks (when any descriptor to a disk file
is closed, the process loses ALL
locks acquired on this file through any descriptor).
RSFile has been tested with py2.7 and py3.3+, on Windows/Linux systems,
and should theoretically work on other *nix systems and python
The technical documentation of RSFile includes a comprehensive description
of concepts and gotchas encountered while developing this library, which
be useful to anyone interested in getting in touch with gory file I/O
The implementation is currently pure-python, so if you need high
performances, using standard python streams
in parallel will remain necessary.
/Why v2.1 and not v2.0 you ask ? Just some pypi constraints I wasn't
aware of, that'll teach me not to erase a just-released version to add
some cleanup commits to it.../
* Switch from Mercurial to Git
* Remove python2.6 support and its polyfills
* Move backends and test suites inside rsfile package
* Conform rsfile to the behaviour of latest "io" module and "open" builtin
* Make rsfile work against py33, py34 and py35, by leveraging their
stdlib test suites
* Rename "win32" to "windows" everywhere (even pywin32 extensions
actually handle x64 system)
* Improve the I/O benchmark runner
* Cache decorated methods to boost performances
* Add support for the new "x" mode flag in rsopen()
* Fix the corner case of uninitialized streams
* Tweak the excessive verbosity of locking tests
* Handle exceptions when closing raw streams (stream is marked as closed
* Normalize the naming of backend modules
* Fix bugs with __getattr__() lookup forwarding
* Use C/N flags for file existence on opening (-/+ supported but deprecated)
* Automatically compare the behaviour of all possible open modes,
between stdlib/io and rsfile
* Autogenerate equivalence matrix for file opening modes, using
* Switch from distutils to setuptools for setup.py
* Add support for the new "opener" parameter of open() builtin
* Strengthen tests around fileno/handle reuse and duplication
* Fix bug regarding improper value of file "modification_time" on windows
* Add implicit flush() before every sync()
* Remove heavy star imports from pywin32 backend
* Roughly test sync() parameters, via performance measurements
* Rename file "uid()" to "unique_id()", to prevent confusion with "user
id" (but an alias remains)
* Fix nasty bug where file unique_id could be None in internal registries
* Add lots of defensive assertions
* Make FileTimes repr() more friendly
* Add support for the wrapping of [non-blocking] pipes/fifos
* Reject the opening of directories properly
* Reorganize and cleanup sphinx docs
* Improve docstrings of added/updated methods/attributes
* Explain the file locking semantic better
* Update and correct typos in the "I/O Overview" article
* Document lots of corner cases: thread safety, reentrancy, sync
parameters, file-share-delete semantic...
* Remove the now obsolete "multi_syscall_lock" (thread-safe interface
* Integrate tests and doc building with Tox
* Fix bug with windows/ctypes backend on python3.5 (OVERLAPPED structure
* Add tests for the behaviour of streams after a fork()
* Add optmizations for systems without fork (no need for multiprocessing
* Normalize "__future__" imports and code formatting
* Review and document the exception types used
* Cleanup/DRY tons of obsolete TODOs and comments
* Better document the CAVEATS of rsfile, regarding fcntl and
interoperability with other I/O libs
* Add standard files to the repository (readme, contributing, changelog
* Integrate with Travis CI
* Add some tweaks to mimick the more tolerant behaviour of python2.7
regarding the mixing of str and unicode
* Add script for aggregate coverage reporting
* Strengthen tests of rsopen() usage errors
We are very happy to announce the v1.2 release of the Astropy package,
a core Python package for Astronomy:
Astropy is a community-driven Python package intended to contain much
of the core functionality and common tools needed for astronomy and
New and improved major functionality in this release includes:
* A new class to compute Lomb-Scargle periodograms efficiently using
* A number of new statistics functions including those for Jackknife
resampling, circular statistics, and the Akaike and Bayesian
* Support for getting the positions of solar system bodies in the
* The ability to compute Barycentric and Heliocentric light-travel
* Support for offset coordinate frames, which can be used to define a
coordinate system relative to a known position and rotation.
* An implementation of the zscale algorithm to determine image limits
* Support for bolometric magnitudes in the units package.
* Improvements to the NDData class and subclasses.
* Auto-downloading of IERS tables as needed, which gives information
about Earth orientation parameters necessary for high precision
coordinate calculations and conversions to/from the UT1 scale.
In addition, hundreds of smaller improvements and fixes have been
made. An overview of the changes is provided at:
Instructions for installing Astropy are provided on our website, and
extensive documentation can be found at:
If you make use of the Anaconda Python Distribution, you can update to
Astropy v1.2 with:
conda update astropy
If you normally use pip, you can upgrade with:
pip install astropy --upgrade
Note that if you install now you should get Astropy v1.2.1, as some
last-minute bug fixes were found and fixed after the v1.2 release was
created but before this announcement.
Please report any issues, or request new features via our GitHub repository:
Over 190 developers have contributed code to Astropy so far, and you
can find out more about the team behind Astropy here:
As a reminder, Astropy v1.0 (our long term support release) will
continue to be supported with bug fixes until Feb 19th 2017, so if you
need to use Astropy in a very stable environment, you may want to
consider staying on the v1.0.x set of releases (for which we have
recently released v1.0.10).
If you use Astropy directly for your work, or as a dependency to
another package, please remember to include the following
acknowledgment at the end of papers:
“This research made use of Astropy, a community-developed core Python
package for Astronomy (Astropy Collaboration, 2013).”
where (Astropy Collaboration, 2013) is a reference to the Astropy paper:
Please feel free to forward this announcement to anyone you think
might be interested in this release!
Erik Tollerud, Tom Robitaille, Kelle Cruz, and Tom Aldcroft
on behalf of The Astropy Collaboration
We are proud to announce our very own mobile app for the EuroPython
*** EuroPython 2016 Conference App ***
Engage with the conference and its attendees
The mobile app gives you access to the conference schedule (even
offline), helps you in planing your conference experience and provides
a rich social engagement platform for all attendees.
You can create a profile within the app (or link this to your existing
social accounts), share messages and photos, and easily reach out to
other fellow attendees.
Vital for all EuroPython attendees
We’d like to make use of the app to keep you updated by sending
regular updates of the schedule and inform you of important
announcements via push notifications, so please consider downloading
With gravitational regards,
EuroPython 2016 Team
PS: Please forward or retweet to help us reach all interested parties:
We all know that good food, drinks and music are essential for a
perfect EuroPython conference and so we’ve arranged a nice dinner with
local food and a party for Tuesday evening (July 19th).
*** EuroPython Conference Dinner and Party ***
If you want to join the fun, please go to the social event page, and
then proceed to the registration form (the same you use to buy
There’s a new entry available now called “Pyntxos Social Event” which
you can order using the form. Leave the conference tickets fields
blank if you only want to purchase social event tickets.
*** Buy Social Event Tickets ***
We have 550 tickets available for the conference dinner and party, so
please book early. The tickets are valid for one person. Please see
the social events page for details of what is included in the ticket
With gravitational regards,
EuroPython 2016 Team
PS: Please forward or retweet to help us reach all interested parties:
I'm glad to announce the release of psutil 4.3.0:
psutil (process and system utilities) is a cross-platform library for
retrieving information on running processes and system utilization (CPU,
memory, disks, network) in Python. It is useful mainly for system
monitoring, profiling and limiting process resources and management of
running processes. It implements many functionalities offered by command
line tools such as: ps, top, lsof, netstat, ifconfig, who, df, kill, free,
nice, ionice, iostat, iotop, uptime, pidof, tty, taskset, pmap. It
currently supports Linux, Windows, OSX, Sun Solaris, FreeBSD, OpenBSD and
NetBSD, both 32-bit and 64-bit architectures, with Python versions from 2.6
to 3.5 (users of Python 2.4 and 2.5 may use 2.1.3 version). PyPy is also
known to work.
Main features / fixes
- #819: [Linux] different speedup improvements:
Process.ppid() is 20% faster
Process.status() is 28% faster
Process.name() is 25% faster
Process.num_threads is 20% faster on Python 3
- #810: [Windows] Windows wheels are incompatible with pip 7.1.2.
- #812: [NetBSD] fix compilation on NetBSD-5.x.
- #823: [NetBSD] virtual_memory() raises TypeError on Python 3.
- #829: [UNIX] psutil.disk_usage() percent field takes root reserved space
- #816: [Windows] fixed net_io_counter() values wrapping after 4.3GB in
Windows Vista (NT 6.0) and above using 64bit values from newer win APIs.
- Home page: https://github.com/giampaolo/psutil
- Downloads: https://pypi.python.org/pypi/psutil
- Documentation: http://pythonhosted.org/psutil/
Giampaolo - http://grodola.blogspot.com
Wingware has released version 5.1.12 of Wing IDE, our cross-platform
integrated development environment for the Python programming language.
Wing IDE features a professional code editor with vi, emacs, visual
studio, and other key bindings, auto-completion, call tips,
context-sensitive auto-editing, goto-definition, find uses, refactoring,
a powerful debugger, version control, unit testing, search, project
management, and many other features.
This release includes the following minor improvements:
Updated German localization (thanks to Christoph Heitkamp)
Fixed Configure Project for Django to work if Start Django Project
was not used first
Don't show deprecation warnings for inspect.getargspec for debug
processes and Python Shell running with Python 3.5
Fixed failure to analyze files in the background
8 other minor bug fixes
For details see http://wingware.com/news/2016-06-17 and
What's New in Wing 5.1:
Wing IDE 5.1 adds multi-process and child process debugging, syntax
highlighting in the shells, support for pytest, Find Symbol in Project,
persistent time-stamped unit test results, auto-conversion of indents on
paste, an XCode keyboard personality, support for Flask, Django 1.7 to
1.9, Python 3.5, and recent Google App Engine versions, improved
auto-completion for PyQt, recursive snippet invocation, and many other
minor features and improvements.
Free trial: http://wingware.com/wingide/trial
Feature list: http://wingware.com/wingide/features
Questions? Don't hesitate to email us at support(a)wingware.com.
Wingware | Python IDE
The Intelligent Development Environment for Python Programmers
(sorry for the double posting, if any)
Dear pythraners and pythonists,
The Pythran team (still 2 active developers) is delighted to
announce the release of Pythran 0.7.5, available on the traditional
- pypi: https://pypi.python.org/pypi/pythran
- conda: https://anaconda.org/serge-sans-paille/pythran
- github: https://github.com/serge-sans-paille/pythran
What is it?
Pythran is a static compiler for numerical kernels written in Python + Numpy.
It basically turns Python-compatible modules into native ones,
eventually vectorized and parallelized.
Following the tradition, each release comes with a code sample. This one
comes from http://jakevdp.github.io/blog/2012/08/24/numba-vs-cython/
#pythran export pythran_pairwise(float64 )
import numpy as np
return np.sqrt(((X[:, None, :] - X) ** 2).sum(-1))
This kernel relies a lot on Numpy's broadcasting, but Pythran can now
compile it efficiently, which is a really nice improvement! It can rip
(without vectorization and parallelization turned on) more than a x5
speedup over the Numpy version \o/
We have published some technical details about Pythran internal on the
It is open to third-party contribution!
* Better Jupyter Note book integration
* Numpy Broadcasting support
* Improved value binding analysis
* Simple inlining optimization
* Type engine improvement
* Less fat in the generated modules
* More and better support for various Numpy functions
* Various performance improvement
* Global variable handling, as constants only though
Thanks a lot to Pierrick Brunet for his dedicated work, and to all the
bug reporters and patch providers that helped a lot for this release:
nils-werner, ronbarak, fred oble, geekou, hainm, nbecker and xantares.
iPOPO v0.6.4 has been released !
What is iPOPO
iPOPO is a Service-Oriented Component Model (SOCM) based on Pelix,
a dynamic service platform. Both are inspired on two popular Java
technologies for the development of long-lived applications: the iPOJO
component model and the OSGi Service Platform.
iPOPO enables to conceive long-running and modular IT services.
It is based on the concepts specified by OSGi:
- Bundle: a Python module imported using Pelix and associated to a
context. A bundle has a life-cycle (install, start, updated, stop,
- Service: a Python object registered in a service registry, associated
to a specification and to properties.
- Component: the instance of a class described/manipulated by iPOPO
Components are bound together by the specification(s) of the service(s)
they provide. The required services are injected into components by iPOPO.
For more information, see
iPOPO provides many services out-of-the-box, like an HTTP server,
local and remote shell, remote services...
iPOPO is released under the terms of Apache Software License 2.0
What's new in 0.6.4
This version adds a log service, allowing access to the traces logged with
either this service or the logging module.
It also two handlers:
- @HiddenProperty, which allows a component to hide some of its information
from the decription API
- @RequiresVariableFilter, which allows to use component properties in the
Basic support for a HTTPS server has been added. It shouldn't be used for
What's coming in 0.6.5
Version 0.6.4 took a year to be released, but the next release should come
Version 0.6.5 will try to tune the HTTP service to ease the development of the
Pelix Web Console, a side project which could become handy.
The HTTPS support will be enhanced as well during this step.
You can take a look at the documentation at https://ipopo.coderxpress.net/
iPOPO is available on PyPI: https://pypi.python.org/pypi/iPOPO
Source is available on GitHub: https://github.com/tcalmant/ipopo
Feel free to send feedback on your experience of Pelix/iPOPO, via the
User list : http://groups.google.com/group/ipopo-users
Development list : http://groups.google.com/group/ipopo-dev
Have fun !