*** NOTE: Python 3.3 only! This module is in the stdlib in Python 3.4. ***
On the heels of Python 3.4.0rc2, I've put a new version of the asyncio
package for Python 3.3 on PyPI: https://pypi.python.org/pypi/asyncio/0.4.1
There's a source distro and a 32-bit Windows wheel. (For 64-bit Windows I
could use some help.)
About asyncio: it's a new stdlib module for asynchronous I/O based on the
"yield from" statement that was added to Python 3.3. It was inspired by
Twisted and the async support in Tornado (amongst other influences). The
original code name for the project is Tulip and this is where the latest
developments happen: http://code.google.com/p/tulip/. Also check out PEP
3156: http://python.org/dev/peps/pep-3156/.
For Python 2 and 3.2, Victor Stinner has created a backport named Trollius:
https://pypi.python.org/pypi/trollius/0.1.5
--
--Guido van Rossum (python.org/~guido)
[Please help spread the word by forwarding to other relevant mailing lists,
user groups, etc. world-wide; thanks :-)]
Dear Python Community,
for many years, the Python Job board (http://legacy.python.org/community/jobs/)
was run by volunteers - most of the time by just one volunteer at a
time until they moved on to spend their time on other things.
We've now reached such a point again.
In these years, the volume on the job board has significantly
increased, as it got more and more popular. It is now at around
2-5 postings per day and most of those positions get filled quickly
- which is an indication of how useful this service is to the
Python community.
To scale up and revive the job board, the PSF would now like to setup
a *team of volunteers* to run the job board and this is our call for
help.
How does the job board work ?
-----------------------------
At the moment, the job board is maintained on the legacy site
(http://legacy.python.org/community/jobs/), but since we've
launched our brand new website (http://www.python.org/), we'd like
to move the job board over to that site.
Instead of the repository based approach used on the old site,
the new site has database support to aid in more easily processing
and filing job listings.
There's a job board mailing list which helps coordinate the
task of reviewing and filing job offers. Currently, all job
submissions get sent to this mailing list, but with the job board
app, the submission process can be moved over to the website's
database.
What does it take to run the job board ?
----------------------------------------
You have to review the job postings, request changes if they are too
long, don't clearly state the need for Python skills, or have quality
issues.
After review, the job board app will then allow posting the jobs
on the website by simply setting the status to published.
Communication with the submitters is usually done by email
and via the mailing list, so all team members can see the
communication and help out if necessary.
Please note: This is just a high level overview. The details
need to be hashed out by the new team.
Does the job board app work already ?
-------------------------------------
It does, but is disabled at the moment due to lack of volunteers.
Since the site just launched there may also well be some issues
with the job board app.
On the positive side there's a lot happening around the site at the
moment, so if you have change requests, these will usually be
implemented quickly - or you can jump in, hack on the
job board app and submit a pull request yourself:
https://github.com/python/pythondotorg/tree/master/jobs
These are exciting times and this is your chance to make a
difference !
Ok, I like new challenges - where do I sign up ?
------------------------------------------------
Great :-) Please write to jobs(a)python.org
I have a question...
--------------------
If you have questions, you can write me or the PSF board
at psf(a)python.org.
Many thanks,
--
Marc-Andre Lemburg
Director
Python Software Foundation
http://www.python.org/psf/
I am pleased to announce release 2014.1 of SfePy.
Description
-----------
SfePy (simple finite elements in Python) is a software for solving
systems of coupled partial differential equations by the finite element
method. The code is based on NumPy and SciPy packages. It is distributed
under the new BSD license.
Home page: http://sfepy.org
Mailing list: http://groups.google.com/group/sfepy-devel
Git (source) repository, issue tracker, wiki: http://github.com/sfepy
Highlights of this release
--------------------------
- sfepy.fem was split to separate FEM-specific and general modules
- lower memory usage by creating active DOF connectivities directly from field
connectivities
- new handling of field and variable shapes
- clean up: many obsolete modules were removed, all module names follow naming
conventions
For full release notes see http://docs.sfepy.org/doc/release_notes.html#id1
(rather long and technical).
Best regards,
Robert Cimrman and Contributors (*)
(*) Contributors to this release (alphabetical order):
Vladimír Lukeš, Matyáš Novák, Jaroslav Vondřejc
On behalf of the Python development team, I'm delighted to announce
the second and final release candidate of Python 3.4.
This is a preview release, and its use is not recommended for
production settings.
Python 3.4 includes a range of improvements of the 3.x series, including
hundreds of small improvements and bug fixes. Major new features and
changes in the 3.4 release series include:
* PEP 428, a "pathlib" module providing object-oriented filesystem paths
* PEP 435, a standardized "enum" module
* PEP 436, a build enhancement that will help generate introspection
information for builtins
* PEP 442, improved semantics for object finalization
* PEP 443, adding single-dispatch generic functions to the standard library
* PEP 445, a new C API for implementing custom memory allocators
* PEP 446, changing file descriptors to not be inherited by default
in subprocesses
* PEP 450, a new "statistics" module
* PEP 451, standardizing module metadata for Python's module import system
* PEP 453, a bundled installer for the *pip* package manager
* PEP 454, a new "tracemalloc" module for tracing Python memory allocations
* PEP 456, a new hash algorithm for Python strings and binary data
* PEP 3154, a new and improved protocol for pickled objects
* PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O
Python 3.4 is now in "feature freeze", meaning that no new features will be
added. The final release is projected for mid-March 2014.
The python.org web site has recently been updated to something
completely new, and I'm having some difficulty updating it. For now
I've made Python 3.4.0rc2 available on the legacy web site:
http://legacy.python.org/download/releases/3.4.0/
Once I can update the new web site, Python 3.4.0rc2 will be available here:
http://python.org/download/releases/
(I'm not sure what the final URL will be, but you'll see it listed on
that page.)
Please consider trying Python 3.4.0rc2 with your code and reporting any
new issues you notice to:
http://bugs.python.org/
Enjoy!
--
Larry Hastings, Release Manager
larry at hastings.org
(on behalf of the entire python-dev team and 3.4's contributors)
Hello World,
I'm pleased to announce version 1.0.4 of rCSSmin.
About rCSSmin
=============
rCSSmin is a CSS minifier written in python based on the semantics of
the YUI compressor, which itself is based on the rule list by Isaac
Schlueter.
This module is a re-implementation aiming for speed instead of maximum
compression, so it can be used at runtime (rather than during a
preprocessing step). RCSSmin does syntactical compression only (removing
spaces, comments and possibly semicolons). It does not provide semantic
compression (like removing empty blocks, collapsing redundant properties
etc). It does, however, support various CSS hacks (by keeping them
working as intended):
- IE7 hack (``>/**/``)
- Mac-IE5 hack (``/*\*/.../**/``)
- The boxmodelhack is supported naturally because it relies on valid
CSS2 strings
- Between ``:first-line`` and the following comma or curly brace a
space is inserted. (apparently it's needed for IE6)
- Same for ``:first-letter``
Comments starting with an exclamation mark (``!``) can be kept optionally.
About Release 1.0.4
===================
This is a cosmetic release fixing documentation issues and adding
benchmarks.
Supported Python Versions
=========================
* Python 2.4 - 2.7
* Python 3.1 - 3.4
* PyPy 1.9, 2.0
* Jython 2.5, 2.7 (Python only)
License
=======
rCSSmin is available under the terms and conditions of the "Apache License,
Version 2.0."
Links
=====
* Homepage + Documentation: http://opensource.perlig.de/rcssmin/
* PyPI: https://pypi.python.org/pypi/rcssmin
* Github: https://github.com/ndparker/rcssmin
* License: http://www.apache.org/licenses/LICENSE-2.0
André "nd" Malo
Hello World,
I'm pleased to announce version 1.0.9 of rJSmin.
About rJSmin
============
rJSmin is a javascript minifier written in python. The minifier is based
on the semantics of jsmin.c by Douglas Crockford.
The module is a re-implementation aiming for speed, so it can be used at
runtime (rather than during a preprocessing step). Usually it produces
the same results as the original jsmin.c. It differs in the following
ways:
- there is no error detection: unterminated string, regex and comment
literals are treated as regular javascript code and minified as such.
- Control characters inside string and regex literals are left
untouched; they are not converted to spaces (nor to \n)
- Newline characters are not allowed inside string and regex literals,
except for line continuations in string literals (ECMA-5).
- "return /regex/" is recognized correctly.
- "+ +" and "- -" sequences are not collapsed to "++" or "--"
- Newlines before ! operators are removed more sensibly
- Comments starting with an exclamation mark ('!') can be kept optionally
- rJSmin does not handle streams, but only complete strings. (However,
the module provides a "streamy" interface).
About Release 1.0.9
===================
This is a cosmetic release fixing documentation issues and updating
benchmarks.
Supported Python Versions
=========================
* Python 2.4 - 2.7
* Python 3.1 - 3.4
* PyPy 1.9, 2.0
* Jython 2.5, 2.7 (Python only)
License
=======
rJSmin is available under the terms and conditions of the "Apache License,
Version 2.0."
Links
=====
* Homepage + Documentation: http://opensource.perlig.de/rjsmin/
* PyPI: https://pypi.python.org/pypi/rjsmin
* Github: https://github.com/ndparker/rjsmin
* License: http://www.apache.org/licenses/LICENSE-2.0
André "nd" Malo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On behalf of the Python development team, I'm happy to announce
the release of Python 3.3.5, release candidate 1.
Python 3.3.5 includes a fix for a regression in zipimport in 3.3.4
(see http://bugs.python.org/issue20621) and a few other bugs.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x. In total, almost 500 API items
are new or improved in Python 3.3. For a more extensive list of
changes in the 3.3 series, see
http://docs.python.org/3.3/whatsnew/3.3.html
To download Python 3.3.5 visit:
http://www.python.org/download/releases/3.3.5/
This is a preview release, please report any bugs to
http://bugs.python.org/
The final release is scheduled one week from now.
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.3's contributors)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlMKIPEACgkQN9GcIYhpnLCjXACfQwbC/eD/lhKAZ+XCwTwYPVWj
GMwAnjWkbdk7hqsKoh12EiagpGApEPSA
=2BCx
-----END PGP SIGNATURE-----
Greetings fellow Pythoneers,
I'm happy to announce that pyOpenSSL 0.14 is now available.
pyOpenSSL is a set of Python bindings for OpenSSL. It includes some
low-level cryptography APIs but is primarily focused on providing an API
for using the TLS protocol from Python.
Check out the PyPI page (<https://pypi.python.org/pypi/pyOpenSSL>) for
downloads.
This release of pyOpenSSL adds:
* Support for TLSv1.1 and TLSv1.2
* First-class support for PyPy
* New flags, such as MODE_RELEASE_BUFFERS and OP_NO_COMPRESSION
* Some APIs to access to the SSL session cache
* A variety of bug fixes for error handling cases
Additionally, there are three major changes to the project:
First, the documentation has been converted from LaTeX (CPython's
previous documentation system) to Sphinx (CPython's "new" documentation
system ;). You can find the new documentation on the PyPI documentation
site (<https://pythonhosted.org/pyOpenSSL/>) or
<https://pyopenssl.readthedocs.org/>).
Second, pyOpenSSL is no longer implemented in C as a collection of
extension modules using the Python/C API. Instead, pyOpenSSL is now a
pure-Python project with a dependency on a new project, cryptography
(<https://github.com/pyca/cryptography>), which provides (among other
things) a cffi-based interface to OpenSSL.
This change means that pyOpenSSL development is now more accessible to
Python programmers with little or no experience with C. This is also how
pyOpenSSL is now able to support PyPy.
Finally, the project's code hosting has moved from Launchpad to Github.
Many branches remain only on Launchpad along with their associated bug
reports. Over the coming releases I hope that the fixes and features in
these branches will be ported to Python and incorporated into the
pyOpenSSL master development branch. Bug tracking has been disabled on
Launchpad so that the amount of useful information hosted there can
gradually dwindle to nothing. Please use Github
(<https://github.com/pyca/pyopenssl>) for further development and bug
reporting.
Thanks and enjoy,
Jean-Paul
I'm very proud to present Yet Another SWF Parser: "yaswfp", you can
pronounce whatever you like :)
https://github.com/facundobatista/yaswfp
You can use it as command line program or as a module, for example
(slightly truncated for readability):
>>> swf = swfparser.parsefile(<yourSWFfile>)
>>> swf.header
Header(name=Header, FileLength=4228, ...)
>>> len(swf.tags)
365
>>> swf.tags[3]
PlaceObject2(name=PlaceObject2, CharacterId=1, ...)
Any doubt, question, suggestion, or whatever, feel free to open an
issue in github, mail me, or find me in IRC (I'm facundobatista in
Freenode).
Regards,
--
. Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista
After more than 4 years of development, we are proud to announce the
release of DEAP 1.0.0. You can download a copy of this release at the
following web page.
https://pypi.python.org/pypi/deap
DEAP (Distributed Evolutionary Algorithms in Python) is a novel evolutionary
computation framework for rapid prototyping and testing of ideas. Its design
departs from most other existing frameworks in that it seeks to make algorithms
explicit and data structures transparent, as opposed to the more common black
box type of frameworks.
To get to know more about DEAP and the current release, we invite you
to read the most recent article on DEAP published in SIGEvolution volume 6,
issue 2, pp. 17-26.
http://sigevolution.org/
An IPython notebook version of the article is also available.
https://github.com/DEAP/notebooks
This release includes:
- Major overhaul of statistics computing and logging;
- Ability to do Object Oriented Genetic Programming (OOGP);
- Symbolic regression benchmarks for GP;
- New tutorials and better documentation;
- Several new examples from diverse fields;
- and several other changes.
Every changes of this release are detailed in the documentation.
http://deap.gel.ulaval.ca/doc/default/releases.html
To help users translate code from 0.9.x to 1.0.0, we have also written
a new porting guide that details every change required to use DEAP 1.0.
http://deap.gel.ulaval.ca/doc/default/porting.html
Your feedback and comments are welcome at http://goo.gl/LZkdi4 or
deap-users at googlegroups dot com. You can also follow us on Twitter @deapdev,
and on our blog http://deapdev.wordpress.com/.
Best,
François-Michel De Rainville
Félix-Antoine Fortin
Marc-André Gardner
Christian Gagné
Marc Parizeau
Laboratoire de vision et systèmes numériques
Département de génie électrique et génie informatique
Université Laval
Quebec City (Quebec), Canada