Hi Stéfan, about backporting, what kind of backporting mechanism do you have in mind? Merging commits by hand, or something more elaborate?
It may be a silly idea, but can't we do it the other way around, that is have an experimental branch where developers who wish to write Python3-only code can work, and in which commits to master are merged if they are Python 3 compatible? It could give us some time to evaluate whether most developers want to write code that is not compatible with Python 2. Best, Emma On Tue, Aug 09, 2016 at 02:23:34PM -0700, Stéfan van der Walt wrote: > Hi everyone, > The previous migration thread stalled, and I would like to revisit the issue. > Here is my proposal: > 1. All code written for the 0.13 release of scikit-image should still be > Python > 2.7 and 3.x compatible. > 2. 0.13.x will be declared a "Long Term Support" release, with all point > releases supporting Python 2.7 until 2020 > 3. Non-API-breaking features from 0.14 and later *may be backported* to 0.13.x > as needed / requested. > 4. Any new code written after 0.13 will be Python 3.x only (but see #3 above). > My motivations are to: > - Remove developer overhead associated with keeping both Python 2 and 3-isms > in > mind > - Reduce testing and maintenance overhead associated with multiple Python > versions > - Utilize new language features such as the @-operator and required keyword > arguments > Please let me know if you have any strong feelings to the contrary. > Best regards > Stéfan -- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscr...@googlegroups.com. To post to this group, send an email to scikit-image@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/20160809214429.GB1817277%40phare.normalesup.org. For more options, visit https://groups.google.com/d/optout.
