Kotti 1.3.1 was released yesterday.
The list of changes is negligible .
But here's the real news: the release of Kotti 2.0.0 is imminent. There will be nothing new in 2.0.0, except Python >= 3.5 compatibility. All tests pass on Python 3.5 as well as 3.6 on all supported databases on the
py3 branch .
I'll update the docs and cleanup the git history in the next couple of days, then I'll create a
maintenance/1.3 brach from master and merge the
py3 branch into master. At that point the only blocker for a 2.0.0 release will be a pending pull request / new release for deform .
The API will remain almost completely unchanged, so that existing applications should continue to work on the new version with little to no changes at all – if their code is Python 3 compatible, because 2.0.0 will be Python 3 only.
If your application depends on Python 2 compatibility you'll have 3 options:
stay on 1.3.x. It's rock solid and will just continue to work.
re-add Python 2 compatibility yourself, or
pay someone to re-add Python 2 compatibility.
The 2.x line of Kotti will see some reimplementations of internals, probably also some API changes, but of course always with proper deprecation. Some existing features might be outfactored into add-ons to make Kotti itself more suitable for other types of applications use cases where some of its more heavyweight feature are not needed.
You received this message because you are subscribed to the Google Groups "Kotti" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to ko...@googlegroups.com.
Visit this group at https://groups.google.com/group/kotti.
To view this discussion on the web visit https://groups.google.com/d/msgid/kotti/901F863E-5D07-4906-91C7-886C0CA45CD4%40binary-punks.com.
For more options, visit https://groups.google.com/d/optout.