I would like to announce that Authomatic now supports Python 3.
Authomatic is a framework agnostic authorization/authentication client library for Python web applications with out-of-the-box support OpenID, 11 OAuth 1.0a and 18 OAuth 2.0 providers.
Big thanks goes to Emmanuel Leblond for his huge contribution
On behalf of the Python development community and the Python 3.5 release
team, I'm thrilled to announce the availability of Python 3.5.0a3.
Python 3.5.0a3 is the third alpha release of Python 3.5, which will be
the next major release of Python. Python 3.5 is still under heavy
development, and is far from complete.
This is a preview release, and its use is not recommended for production
Two important notes for Windows users about Python 3.5.0a3:
* If you have previously installed Python 3.5.0a1, you may need to
manually uninstall it before installing Python 3.5.0a3 (issue23612).
* If installing Python 3.5.0a3 as a non-privileged user, you may need
to escalate to administrator privileges to install an update to your
C runtime libraries.
You can find Python 3.5.0a3 here:
I'm pleased to announce the second release for hunter:
What is Hunter?
Hunter is a tracer tool, designed to be used for debugging or just to
understand how an application works. It's designed to be flexible and
extensible with custom actions or filters.
It prints the executed code from locations of your choosing and can
optionally print variables from the frames. It also colors the output if
you're in a terminal.
To show all the executed code from `posixpath`:
import hunter hunter.trace(module='posixpath')
To show all the executed code from `posixpath` and a variable:
For convenience, you can also activate it via a `PYTHONHUNTER` environment
PYTHONHUNTER="module='posixpath'" python yourapp.py
For more examples see:
Changes in 0.2
* Added color support (and colorama as dependency).
* Added support for expressions in VarsPrinter.
* Improved error reporting for env variable activation (PYTHONHUNTER).
* Fixed env var activator (the .pth file) installation with setup.py
install (the “egg installs”) and setup.py develop/pip install -e (the “egg
* Breaking changes:
* Renamed F to Q. And Q is now just a convenience wrapper for Query.
* Renamed the PYTHON_HUNTER env variable to PYTHONHUNTER.
* Changed When to take positional arguments.
* Changed output to show 2 path components (still not configurable).
* Changed VarsPrinter to take positional arguments for the names.
Project page and issue tracker
-- Ionel Cristian Mărieș, http://blog.ionelmc.ro
On behalf of the Jython development team, I'm pleased to announce that
the fourth beta of Jython 2.7 is available.
Details are here:
Thanks to Amobee for sponsoring my work on Jython, and thanks to the
many contributors to Jython!
(sorry for the first one with the wrong subject).
A Python3 and PyQT4 Multiplatform Desktop Ping Application
PingPung is intended to fill the niche of a truly multiplatform graphical ping application. Unlike other desktop ping utilities, it does NOT use your operating system's builtin 'ping' program at all. Instead, it uses a pure Python 3 library which creates its own socket. *** Because of this, it will require root privileges on many/all platforms.*** If you're uncomfortable with that, there are many other platform-specific graphical ping apps out there which do not require root (because they're just wrappers around the OS's existing ping util).
A note about dependencies
This application uses PyQt4 as the graphical library, which is not installable via PyPI and will need to be done separately. On Debian/Ubuntu, for example, it's as simple as
sudo apt-get install python3-pyqt4
If you intend to build for Windows, you'll also need to install cx_freeze by any method you choose, and build with
python winsetup.py build_exe
The ping library in use was derived from a standalone application found here http://www.falatic.com/index.php/39/pinging-with-python
PingPung is a Python 3 application, and for any system with Python 3, it's just
pip3 install pingpung
Windows users can download the Windows ZIP file linked on our website https://raindogsoftware.github.io/pingpung/
pytest-2.7.0: fixes, features, speed improvements
pytest is a mature Python testing tool with more than a 1100 tests
against itself, passing on many different interpreters and platforms.
This release is supposed to be drop-in compatible to 2.6.X.
See below for the changes and see docs at:
As usual, you can upgrade from pypi via::
pip install -U pytest
Thanks to all who contributed, among them:
2.7.0 (compared to 2.6.4)
- fix issue435: make reload() work when assert rewriting is active.
Thanks Daniel Hahler.
- fix issue616: conftest.py files and their contained fixutres are now
properly considered for visibility, independently from the exact
current working directory and test arguments that are used.
Many thanks to Eric Siegerman and his PR235 which contains
systematic tests for conftest visibility and now passes.
This change also introduces the concept of a ``rootdir`` which
is printed as a new pytest header and documented in the pytest
customize web page.
- change reporting of "diverted" tests, i.e. tests that are collected
in one file but actually come from another (e.g. when tests in a test class
come from a base class in a different file). We now show the nodeid
and indicate via a postfix the other file.
- add ability to set command line options by environment variable PYTEST_ADDOPTS.
- added documentation on the new pytest-dev teams on bitbucket and
github. See https://pytest.org/latest/contributing.html .
Thanks to Anatoly for pushing and initial work on this.
- fix issue650: new option ``--docttest-ignore-import-errors`` which
will turn import errors in doctests into skips. Thanks Charles Cloud
for the complete PR.
- fix issue655: work around different ways that cause python2/3
to leak sys.exc_info into fixtures/tests causing failures in 3rd party code
- fix issue615: assertion re-writing did not correctly escape % signs
when formatting boolean operations, which tripped over mixing
booleans with modulo operators. Thanks to Tom Viner for the report,
triaging and fix.
- implement issue351: add ability to specify parametrize ids as a callable
to generate custom test ids. Thanks Brianna Laugher for the idea and
- introduce and document new hookwrapper mechanism useful for plugins
which want to wrap the execution of certain hooks for their purposes.
This supersedes the undocumented ``__multicall__`` protocol which
pytest itself and some external plugins use. Note that pytest-2.8
is scheduled to drop supporting the old ``__multicall__``
and only support the hookwrapper protocol.
- majorly speed up invocation of plugin hooks
- use hookwrapper mechanism in builtin pytest plugins.
- add a doctest ini option for doctest flags, thanks Holger Peters.
- add note to docs that if you want to mark a parameter and the
parameter is a callable, you also need to pass in a reason to disambiguate
it from the "decorator" case. Thanks Tom Viner.
- "python_classes" and "python_functions" options now support glob-patterns
for test discovery, as discussed in issue600. Thanks Ldiary Translations.
- allow to override parametrized fixtures with non-parametrized ones and vice versa (bubenkoff).
- fix issue463: raise specific error for 'parameterize' misspelling (pfctdayelise).
- On failure, the ``sys.last_value``, ``sys.last_type`` and
``sys.last_traceback`` are set, so that a user can inspect the error
via postmortem debugging (almarklein).
about me: http://holgerkrekel.net/about-me/