I'm very happy to announce the release of Sphinx 1.4-final available on the
Python package index at <http://pypi.python.org/pypi/Sphinx/1.4>.
Sphinx-1.4 includes many updates from 1.3.6 version:
* 49 features
* 17 incompatible changes
* 40 fixes of bugs/buglets
For the full changelog, go to <http://www.sphinx-doc.org/en/1.4/changes.html
Thanks to all coraborators and contributers!
What's new in 1.4 (short version)?
* I18N: figure substitutions by language and figure_language_filename
* Config: suppress_warnings to suppress arbitrary warning message
* Directive: glossary term supports grouping key for index entries by using
classifier syntax (experimental)
* Directive: Support Imgmath (pngmath with svg support).
* Builder: XeTeX and LuaTeX for the LaTeX builder.
* Builder: Add the ``dummy`` builder: syntax check without output.
* Builder: Add EPUB 3 builder (experimental)
* Search: Chinese language search index.
* Search: Japanese language search index by using Janome
* Search: splitter customization for Japanese language search index
* Domain: cpp domain improvements
* Ext: Add sphinx.ext.githubpages to publish the docs on GitHub Pages
* Ext: Add ``sphinx.ext.autosectionlabel`` extension to allow reference
sections using its title.
* API: Add Sphinx.add_source_parser() to add source_suffix and
source_parsers from extension
* Image recognition by using ``imagesize`` package w/o PIL/Pillow
* manpage writer: don't make whole of item in definition list bold if it
includes strong node.
* Remove hint message from quick search box for html output.
* sphinx_rtd_theme has become optional. Please install it manually.
* :confval:`html_extra_path` also copies dotfiles in the extra directory,
refers to :confval:`exclude_patterns` to exclude extra files and
* Under glossary directive, each terms are converted into individual
``term`` nodes and ``termsep`` node is removed.
By this change, output layout of every builders are changed a bit.
* The default highlight language is now Python 3. This means that source
is highlighted as Python 3 (which is mostly a superset of Python 2), and
parsing is attempted to distinguish valid code.
* `Locale Date Markup Language
``"MMMM dd, YYYY"`` is default forma for `today_fmt` and
However strftime format like ``"%B %d, %Y"`` is also supported for
compatibility until Sphinx-1.5. Later format will be disabled from
What is it?
Sphinx is a tool that makes it easy to create intelligent and beautiful
documentation for Python projects (or other documents consisting of
multiple reStructuredText source files).
IRC: #sphinx-doc on irc.freenode.net
Just in case you didn’t find enough Easter eggs today, we have a whole
basket of them waiting for you: the first set of accepted sessions for
EuroPython 2016 in Bilbao.
*** EuroPython 2016 Session List ***
The sessions were selected on the basis of your talk voting and the
work of the EuroPython program work group. From the around 300
proposals, 156 sessions were chosen for EuroPython 2016 in the first
* 125 talks
* 20 training sessions
* 11 local track talks
We still have several other session types coming (helpdesks, posters,
panels, interactive sessions). These will announced separately.
Early in June we will have a short second Call for Proposals, limited
to hot topics and most recent developments in software and technology.
We will announce details soon.
Many thanks to everyone who submitted proposals. EuroPython wouldn’t
be possible without our speakers.
The program work group will now work on the schedule. Given the
number of sessions, this may take a while, but we’ll try to get it done
as quickly as possible. The WG is also putting together a submission
waiting list, which will be used to fill slots of speakers who cannot
attend. Speakers on the waiting list will be contacted by the end of
Happy Easter Weekend !
With gravitational regards,
EuroPython 2016 Team
I wanted to announce a workshop I'm organizing at SciPy this year:
What: A two-day workshop bringing together folks working on JIT/AOT
compilation in Python.
When/where: July 11-12, in Austin, Texas.
(This is co-located with SciPy 2016, overlapping with the tutorial
sessions, just before the conference proper.)
Nathaniel J. Smith -- https://vorpus.org
I'm the main developer of qutebrowser, a keyboard-focused vim-like web browser,
built using Python and Qt: http://www.qutebrowser.org/
qutebrowser is currently using QtWebKit, which is based on an outdated version
of the WebKit rendering engine. This comes with various stability, performance
and security issues.
I just launched a crowdfunding campaign with the goal of adding support for
QtWebEngine to qutebrowser. QtWebEngine is based on Chromium and in very active
development - support for it will fix dozens of qutebrowser bugs related to
Since this is a lot of work, I plan to work on it full-time for a month, or
even longer if possible. I'd really appreciate your help!
You can find the campaign here: http://igg.me/at/qutebrowser
http://www.the-compiler.org | me(a)the-compiler.org (Mail/XMPP)
GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
I love long mails! | http://email.is-not-s.ms/
A new Trove Classifier "Framework :: Pytest" has been added to PyPI
following a request I made some time ago.
With this users have another way to search for pytest plugins besides
searching only for projects with "pytest-" prefix, which is great!
Later on today I will update the official docs to mention this and update
plugincompat to also use this classifier to find plugins.
I recommend all plugin authors to include this classifier in your
``setup.py`` and publish the change to PyPI. For those who don't know, you
don't need to publish a new release to update the PyPI project page, you
can just add the classifier to ``setup.py`` and execute ``python setup.py
PyCA/cryptography 1.3.1 was just released to PyPI. This is a minor bugfix release that fixes the following:
* Fixed a bug that caused an AttributeError when using mock to patch some cryptography modules.
-Paul Kehrer (reaperhulk)
This is a gentle reminder about the approaching deadlines for the SciPy 2016
Mar 21: Tutorial Proposals Due
Mar 25: Talk and Poster Proposals Due
Please submit your tutorials and talks at http://scipy2016.scipy.org .
SciPy 2016, the Fifteenth Annual Conference on Python in Science, takes place in
Austin, TX on July, 11th to 17th. The conference features two days of tutorials
by followed by three days of presentations, and concludes with two days of
developer sprints on projects of interest to attendees.
The topics presented at SciPy are very diverse, with a focus on advanced
software engineering and original uses of Python and its scientific libraries,
either in theoretical or experimental research, from both academia and the
industry. This year we are happy to announce two specialized tracks that run in
parallel to the general conference (Data Science , High Performance Computing)
and 8 mini-symposia (Earth and Space Science, Biology and Medicine, Engineering,
Social Sciences, Special Purpose Databases, Case Studies in Industry, Education,
Submissions for talks and posters are welcome on our website
(http://scipy2016.scipy.org). In your abstract, please provide details on what
Python tools are being employed, and how. The talk and poster submission
deadline is March 25th, 2016, while the tutorial submission deadline is March,
Mar 21: Tutorial Proposals Due
Mar 25: Talk and Poster Proposals Due
May 11: Plotting Contest Submissions Due
Apr 22: Tutorials Announced
Apr 22: Financial Aid Submissions Due
May 4: Talk and Posters Announced
May 11: Financial Aid Recipients Notified
May 22: Early Bird Registration Deadline
Jul 11-12: SciPy 2016 Tutorials
Jul 13-15: SciPy 2016 General Conference
Jul 16-17: SciPy 2016 Sprints
We look forward to an exciting conference and hope to see you in Austin in July!
SciPy 2016 Organizers (http://scipy2016.scipy.org/)
Conference Chairs: Aric Hagberg, Prabhu Ramachandran
Tutorial Chairs: Justin Vincent, Ben Root
Program Chair: Serge Rey, Nelle Varoquaux
Proceeding Chairs: Sebastian Benthall, Scott Rostrup
PyGreSQL 5.0 has just been released. This is the first release of
PyGreSQL to run under Python 3.x. See the web site for other changes
and enhancements. The source files are available at:
If you are running NetBSD, look in the packages directory under
databases. There is also a package in the FreeBSD ports collection.
This version has been built and unit tested on:
- Windows 7 with both MinGW and Visual Studio
- PostgreSQL 9.0 to 9.5 32 and 64bit
- Python 2.6, 2.7, 3.3, 3.4 and 3.5 32 and 64bit
D'Arcy J.M. Cain
PyGreSQL Development Group
On behalf of PyCA – the Python Cryptography Authority – I’m anxious to announce that after almost a year since the 0.15.1 release of pyOpenSSL we’ve released the brand new 16.0.0.
A few organizational notes:
1. The pyopenssl-users mailing list and #pyopenssl IRC channel are deprecated. Please use cryptography-dev <https://mail.python.org/pipermail/cryptography-dev/> and #cryptography-dev on Freenode where you’re much more likely to get help.
2. The version scheme switched to CalVer because a 0.x version for a 15 years old project is rather odd and calling it 1.0 although we don’t expect a 2.0 to ever happen didn’t make any sense. pyOpenSSL is a long-running project with strict backward-compatibility requirements and is hence better served with a calendar-based version scheme.
3. Please note that some of us will be doing a TLS/HTTPS workshop at PyCon US 2016 so if you always wanted to learn about these things first hand, make sure to sign up: <https://us.pycon.org/2016/schedule/presentation/1786/>. We've opted to receive no compensation and asked the organizers to send them to PyLadies instead. So you’ll be doing good while learning something!
While the list of changes looks short, a lot internal work happened:
72 files changed, 15511 insertions(+), 15063 deletions(-)
We’ve done our best to not break any existing applications; including by making the urllib3 and Twisted test suites part of our CI.
The full changelog can be found at <https://pyopenssl.readthedocs.org/en/stable/changelog.html>.
This is the first release under full stewardship of PyCA. We have made many changes to make local development more pleasing. The test suite now passes both on Linux and OS X with OpenSSL 0.9.8, 1.0.1, and 1.0.2. It has been moved to py.test, all CI test runs are part of tox and the source code has been made fully flake8 compliant.
We hope to have lowered the barrier for contributions significantly but are open to hear about any remaining frustrations.
• Python 3.2 support has been dropped. It never had significant real world usage and has been dropped by our main dependency cryptography. Affected users should upgrade to Python 3.3 or later.
• The support for EGD has been removed. The only affected function OpenSSL.rand.egd() now uses os.urandom() to seed the internal PRNG instead. Please see pyca/cryptography#1636 for more background information on this decision. In accordance with our backward compatibility policy OpenSSL.rand.egd() will be removed no sooner than a year from the release of 16.0.0.
Please note that you should use urandom for all your secure random number needs.
• Python 2.6 support has been deprecated. Our main dependency cryptography deprecated 2.6 in version 0.9 (2015-05-14) with no time table for actually dropping it. pyOpenSSL will drop Python 2.6 support once cryptography does.
• Fixed OpenSSL.SSL.Context.set_session_id, OpenSSL.SSL.Connection.renegotiate, OpenSSL.SSL.Connection.renegotiate_pending, and OpenSSL.SSL.Context.load_client_ca. They were lacking an implementation since 0.14. #422
• Fixed segmentation fault when using keys larger than 4096-bit to sign data. #428
• Fixed AttributeError when OpenSSL.SSL.Connection.get_app_data() was called before setting any app data. #304
• Added OpenSSL.crypto.dump_publickey() to dump OpenSSL.crypto.PKey objects that represent public keys, and OpenSSL.crypto.load_publickey() to load such objects from serialized representations. #382
• Added OpenSSL.crypto.dump_crl() to dump a certificate revocation list out to a string buffer. #368
• Added OpenSSL.SSL.Connection.get_state_string() using the OpenSSL binding state_string_long. #358
• Added support for the socket.MSG_PEEK flag to OpenSSL.SSL.Connection.recv() and OpenSSL.SSL.Connection.recv_into(). #294
• Added OpenSSL.SSL.Connection.get_protocol_version() and OpenSSL.SSL.Connection.get_protocol_version_name(). #244
• Switched to utf8string mask by default. OpenSSL formerly defaulted to a T61String if there were UTF-8 characters present. This was changed to default to UTF8String in the config around 2005, but the actual code didn't change it until late last year. This will default us to the setting that actually works. To revert this you can call OpenSSL.crypto._lib.ASN1_STRING_set_default_mask_asc(b"default"). #234