Release 1.17.1 of pretix and pre-announcements for pretix 2.0
This month, there is no new feature release of pretix, but we are fixing some minor issues in the current stable release. At the same time, we're announcing some important changes coming up in pretix 2.0 next month.
In particular, pretix 1.17.1 fixes the following bugs:
An exception thrown when cloning an event in some cases.
An exception thrown when editing event meta data in some cases.
Multiple exceptions thrown when submitting API requests with missing optional fields in the body.
Multiple exceptions thrown during form validation.
An exception thrown with custom prices of more than 100 million units of currency.
pretix 1.17.1 is now available for installation via
pip. The new docker images will appear on Docker Hub over the
next few hours. We apologize for any caused inconvenience.
Announcements for pretix 2.0
We plan on releasing pretix 2.0 in early September. pretix 2.0 will be backwards-incompatible in multiple regards, so we'd like to announce a few changes already to allow you to prepare.
Changes for system administrators:
With pretix 2.0, we will drop support for Python 3.4. If you're using Python 3.4 at the moment, we recommend that you already perform an upgrade to Python 3.5 or Python 3.6, so you're ready when pretix 2.0 arrives.
pretix 2.0 will also break things in the plugin API, so please have a look at the plugins you have installed. We will make sure that all plugins officially maintained by us will have a compatible release ready within one day after the release of pretix 2.0, but if you run any third-party or self-built plugins, have a look if you can prepare them for pretix 2.0 already.
Changes for plugin maintainers:
pretix 2.0 will allow partial payments and refunds of orders, and therefore changes the API for payment plugins in a backwards-compatible way. If your plugin contains a payment provider, we suggest that you prepare by reading and following our upgrade guide.
pretix 2.0 will presumably be based on Django 2.1 instead of Django 1.11. Therefore, you should make sure your plugin code is compatible with these Django versions by reading the Django release notes. We're also upgrading to REST framework 3.8 and django-filter 2.0 which both come with some bakwards-incompatible changes.
For customers on our Hosted service, we will roll out the changes of 2.0 in chunks over the next weeks. We'll make sure all installed plugins stay compatible, so you don't need to check anything and get the new features as soon as they are ready.