We are excited to announce the launch of the EuroPython 2018 website:
* https://ep2018.europython.eu/ *
The EuroPython conference will take place in sunny Edinburgh,
Scotland, this year, from July 23-29 2018.
It’s a great time of year to visit Edinburgh with 16 hours of
daylight, and the festival season in full flow, so come and join
us. This is just one week before the famous Edinburgh Fringe Festival
and the Turing Festival, so you can extend your stay a little longer
in Edinburgh, or head for the Highlands to enjoy the amazing mountains
and lochs.
EuroPython 2018 - The European Python Conference
------------------------------------------------
Here’s an overview of what you can expect in Edinburgh:
- We will start with Workshops and Training Sessions on Monday and
Tuesday.
- The main 3 conference days follow, packed with keynotes, talks,
exhibition, help desks, interactive sessions, panels and poster
sessions.
- The two weekend days after the conference, July 28 and 29, are
reserved for sprints (hackathons).
Overall, we will again have 7 days worth of great Python content,
arranged in over 120 sessions, waiting for you.
The venue is the Edinburgh International Conference Centre, in central
Edinburgh, just on the edge of the historic Old Town.
In short:
- Monday, Tuesday, July 23-24: Workshops and Training
- Wednesday - Friday, July 25-27: Conference talks, keynotes, training
- Saturday, Sunday, July 28-29: Sprints
Our Sponsors
------------
All this would not be possible without the generous help of our launch
sponsors. If your company would be interested in sponsoring the 17th
EuroPython please contact sponsoring(a)europython.eu.
Sponsoring EuroPython guarantees you highly targeted visibility and
the opportunity to present yourself and your company in a professional
and innovative environment. You’ll have an unique opportunity to meet
many Python-enthusiastic developers, users and professionals. As a
sponsor of EuroPython 2018, you will directly help to promote the work
of a great open-source community and help further its development.
EuroPython 2018 is the 17th EuroPython conference. The conference
tours throughout Europe. It so far has had stops in Belgium, Sweden,
Lithuania, United Kingdom, Italy, Germany and Basque Country/Spain,
growing from initially 240 attendees to well over 1200.
In the coming days, we will announce the start of the Call for
Proposals and Early Bird Ticket sales. Please watch our EuroPython
blog for updates.
https://ep2018.europython.eu/
Enjoy,
--
EuroPython 2018 Team
https://ep2018.europython.eu/https://www.europython-society.org/
PS: Please forward or retweet to help us reach all interested parties:
https://twitter.com/europython/status/961616731482488833
Thanks.
Hello! Django-CheetahTemplate version 0.2.
WHAT IS Django-CheetahTemplate
Django-CheetahTemplate is a Django template backend to use
CheetahTemplate3 in Django. It's a brand new project created for the new
custom Django template backends API.
It works with Python 2.7 or Python 3.4+, Django 1.11 and 2+,
CheetahTemplate3.
WHAT'S NEW
Version 0.2.0 (2018-02-05)
The first public release.
WHERE TO GET
Home Page: https://github.com/CheetahTemplate3/django-cheetahtemplate
PyPI: https://pypi.python.org/pypi/django-cheetahtemplate
AUTHOR
Oleg Broytman <phd(a)phdru.name>
COPYRIGHT
Copyright (C) 2018 PhiloSoft Design.
LICENSE
MIT
Oleg.
--
Oleg Broytman http://phdru.name/ phd(a)phdru.name
Programmers don't die, they just GOSUB without RETURN.
We're pleased to announce the release of RISE 5.2.0!
RISE let's you show your Jupyter notebook rendered as an executable
Reveal.js-based slideshow. It is your very same notebook but in a slidy way!
For more information about this release, please visit the following blog
post: http://www.damian.oquanta.info/posts/rise-520-is-out.html
Have a great week!
--
*Damián Avila*
On behalf of the Python development community, I'm happy to announce the
availability of Python 3.4.8 and Python 3.5.5.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both
versions only accept security fixes, not conventional bug fixes, and
both releases are source-only.
You can find Python 3.4.8 here:
https://www.python.org/downloads/release/python-348/
And you can find Python 3.5.5 here:
https://www.python.org/downloads/release/python-355/
Happy Pythoning,
//arry/
Hello all,
I'm glad to announce the release of pyo 0.8.9, available for python
2.7, 3.5 and 3.6.
Pyo is a Python module written in C to help real-time digital signal processing
script creation. It is available for Windows, macOS and linux. It is released
under the LGPL 3 license.
For more info, downloads and other links, see the official web site:
http://ajaxsoundstudio.com/software/pyo/
The documentation:
http://ajaxsoundstudio.com/pyodoc/
For the latest sources and bug tracker:
https://github.com/belangeo/pyo
Bug Fixes:
- Fixed erroneous condition in listscramble function.
- Fixed pa_get_devices_infos() function on Windows.
- Fixed segfault at exit when a Server object is created but never
booted (fixed issue #117).
- Fixed window shape in the Harmonizer object (use an halfsine instead
of an hanning).
- Fixed crash when trying to draw a ControlSlider with width or height of 0.
Enhancements:
- Changed the stereo panning law for cosine/sine within Pan object.
- Speed-up computation for various objects.
- Allow the "mode" argument of Resample object to be changed dynamically.
- Added new object: HRTF, Head-Related Transfert Function 3D spatialization.
Olivier Belanger
belangeo(a)gmail.com
http://olivier.ajaxsoundstudio.com/
----
P><A HREF="http://ajaxsoundstudio.com/software/pyo/">Pyo 0.8.9</A>
Python DSP library. (05-Feb-18)
Announcing wxPython 4.0.1
=========================
PyPI: https://pypi.python.org/pypi/wxPython/4.0.1
Extras: https://extras.wxPython.org/wxPython4/extras/
Pip: ``pip install wxPython==4.0.1``
This release is a quick hot-fix of some issues discovered in 4.0.0
just after the release, plus a bit of low-hanging fruit that was easy
to squeeze in too. Changes in this release include the following:
* A fix for a segfault that happens upon startup on newer linux
releases. (#648)
* Set LD_RUN_PATH for the wxWidgets part of the build so the wx libs
that are loaded by other wx libs can be found successfully. (#723)
* Use wxApp::GetInstance to check if there is an existing wxApp
object. (#720)
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
application.
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 with 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:
https://docs.wxpython.org/MigrationGuide.html
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/
--
Robin Dunn
Software Craftsman
http://wxPython.org
With the release of 3.7b1, I’ve updated the semi-official python-dev big ol’ docker image you can use in various CI and development tasks, such as for GitLab CI runners. This image is based on Ubuntu 16.04 LTS, and comes with the latest Python 2.7, 3.4, 3.5, 3.6, 3.7, and git master (now 3.8a0), along with a bunch of other useful tools like mypy, coverage, tox, wget, zip, and git.
For more information see:
https://gitlab.com/python-devs/ci-images/tree/master
The README.md file includes links to the quay.io repository, instructions on the image’s use, and a sample .gitlab-ci.yml file.
I’ll be tracking the 3.7 releases now as well.
Feedback welcome at:
https://gitlab.com/python-devs/ci-images
Cheers,
-Barry
Announcing wxPython 4.0.0
=========================
PyPI: https://pypi.python.org/pypi/wxPython/4.0.0
Extras: https://extras.wxPython.org/wxPython4/extras/
Pip: ``pip install wxPython==4.0.0``
Changes in this release include the following:
* Fixes in wx.aui to properly transfer ownership of the menubar, and
also some tweaks in the AUI_MDI sample in the demo. (#540)
* Added a wx.BUILD_TYPE value to distinguish between development,
snapshot, and release builds. The value is also appended to
wx.PlatformInfo. (Thanks Mesalu!)
* Fix crash when trying to fetch multiple items from a composite data
object in wx.DropTarget.OnData. (#550) Also fixed the
CustomDragAndDrop sample to not fail on Python 2.7.
* Add ability for wxArray wrappers to return a copy of the item in the
``__getitem__`` method. This solves problems where an array that is
the return value of some method call is indexed immediately and a
reference to the array is not held, which could result in garbage
values for the indexed item. Currently this is turned on for just
GridCellCoordsArray, but others can be switched in the future if
needed. (#297)
* Add missing ``wx.GetLocale`` function. (#572)
* Add methods to wx.TextCtrl for output "file-like"
compatibility. (#578)
* Fix object ownership issue for menus added to toolbar items. (#580)
* Updated SIP to version 4.19.5. One of the new features of this
version is that integer overflows are no longer silently truncated
and ignored. In other words, if a wrapped API has a parameter that
is a C int type, and you pass a value that is larger than what will
fit in that type of integer then an OverflowError exception will be
raised.
* Fixed wx.richtext.RichTextBuffer.GetExtWildcard to return a tuple of
2 values, as was done in Classic. (#594)
* Various fixes in UltimateListCtrl, HyperTreeList and
CheckListCtrlMixin. (#592, #349, #612)
* Fixes in TextEditMixin to ensure that the new value is passed in the
event. (#605)
* Fix comparing DataViewItem and TreeListItem objects with
None. (#595)
* Fix event type name in wx/lib/sheet.py (#613)
* The wx.MessageDialog methods which take ButtonLabel parameters are
now able to accept either strings or stock IDs. (#607, #276)
* Fix wx.EvtHandler.Unbind to work correctly when specifying the
handler and it is a bound method. (#624)
* Fix OGL's ShapeCanvas to draw properly when the window is scrolled,
and to also adjust the mouse coordinates, etc. (#635)
* Set a default background color for the generic buttons. (#651)
* Fixed HtmlWindow's OnFoo virtual methods so calls to them are
propagated to the Python class. (#642)
* Fixed wx.CallLater to explicitly hold a reference instead of
depending on an uncollectable cycle to keep the instance
around. Like before the cycle is broken and the saved reference is
deleted after the timer expires and the callable has been
called. (#457)
* Although it's more or less just an implementation detail, add
wrappers for wx.aui.AuiTabCtrl so references to it will get the
correct type. (#664)
* List-like wrapper classes generated for accessing wxLists and
wxArrays now support reverse indexing. (#669) For example::
child = panel.GetChildren()[-1]
* Ported some of the classes in Classic's gizmos module from C++ to
Python, including LEDNumberCtrl, DynamicSashWindow, and
TreeListCtrl. The classes are now located in the wx.lib.gizmos
package, with a compatibility module at the old wx.gizmos
location. Please note that this TreeListCtrl class is a very
different implementation than wx.dataview.TreeListCtrl, although
there is some overlap in purpose. In addition, the new TreeListCtrl
class is not actually a port from the old gizmos.TreeListCtrl but
rather just a thin layer around AGW's HyperTreeList. This means that
if you are using a non- default style flag you'll need to pass it to
the agwStyle parameter instead of the style parameter.
* Fix crash when deleting all wx.dataview.TreeListCtrl items with
wxGTK3. (#679, #704)
* Fix displaying '&' in the label of wx.RadioBox on GTK. (#39)
* Fix problems of the wrong C++ method being called in
wx.ProgressDialog on MS Windows. (#701)
* Fixed how the scrollbar events are captured in DynamicSashWindow in
order to fix regression in the sample. (#687)
* Allow extra CLI args to be passed to build.py by setting
WXPYTHON_BUILD_ARGS in the environment.
* Added context manager methods to wx.DC that explicitly destroys the
C++ part of the DC upon exit. Using DCs as context managers is not
required, but can be handy in the rare cases where something holds
on to a DC for too long, perhaps unintentionally. (#680)
* Fixed crash due to too aggressive management of wxModules when we
load subordinate extensions that have their own wxModules (wx.html,
wx.adv, etc.) (#688)
* Fixed StyledTextCtrl.MarkerDefineRGBAImage and RegisterRGBAImage
methods to be able to accept any Python buffer compatible object for
the pixel data. (#716)
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
application.
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 with 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:
https://docs.wxpython.org/MigrationGuide.html
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/
--
Robin Dunn
Software Craftsman
http://wxPython.org
On behalf of the Python development community and the Python 3.7 release
team, I'm happy to announce the availability of Python 3.7.0b1. b1 is
the first of four planned beta releases of Python 3.7, the next major
release of Python, and marks the end of the feature development phase
for 3.7. You can find Python 3.7.0b1 here:
https://www.python.org/downloads/release/python-370b1/
Among the new major new features in Python 3.7 are:
* PEP 538, Coercing the legacy C locale to a UTF-8 based locale
* PEP 539, A New C-API for Thread-Local Storage in CPython
* PEP 540, UTF-8 mode
* PEP 552, Deterministic pyc
* PEP 553, Built-in breakpoint()
* PEP 557, Data Classes
* PEP 560, Core support for typing module and generic types
* PEP 562, Module __getattr__ and __dir__
* PEP 563, Postponed Evaluation of Annotations
* PEP 564, Time functions with nanosecond resolution
* PEP 565, Show DeprecationWarning in __main__
* PEP 567, Context Variables
Please see "What’s New In Python 3.7" for more information.
Additional documentation for these features and for other changes
will be provided during the beta phase.
https://docs.python.org/3.7/whatsnew/3.7.html
Beta releases are intended to give you the opportunity to test new
features and bug fixes and to prepare their projects to support the
new feature release. We strongly encourage you to test your projects
with 3.7 during the beta phase and report issues found to
https://bugs.python.org as soon as possible.
While the release is feature complete entering the beta phase, it is
possible that features may be modified or, in rare cases, deleted up
until the start of the release candidate phase (2018-05-21). Our goal
is have no ABI changes after beta 3 and no code changes after rc1.
To achieve that, it will be extremely important to get as much exposure
for 3.7 as possible during the beta phase.
Attention macOS users: with 3.7.0b1, we are providing a choice of
two binary installers. The new variant provides a 64-bit-only
version for macOS 10.9 and later systems; this variant also now
includes its own built-in version of Tcl/Tk 8.6. We welcome your
feedback.
Please keep in mind that this is a preview release and its use is
not recommended for production environments.
The next planned release of Python 3.7 will be 3.7.0b2, currently
scheduled for 2018-02-26. More information about the release schedule
can be found here:
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
nad(a)python.org -- []