Migration to Python 3.x

Ralf Gommers ralf.gommers at gmail.com
Tue Aug 9 18:09:06 EDT 2016


On Wed, Aug 10, 2016 at 9:58 AM, Stéfan van der Walt <stefanv at berkeley.edu>
wrote:

> Hi Emmanuelle
>
>
> On 9 August 2016 at 14:44, Emmanuelle Gouillart <
> emmanuelle.gouillart at nsup.org> wrote:
>
>
>> 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.
>>
>
> I don't think that's a silly idea, but I also don't think that addresses
> two of the points I raised:
>
> - Remove developer overhead associated with keeping both Python 2 and
> 3-isms in mind
>
> I'd like developers to start thinking in Python 3, not the other way
> around.  Barriers for Python 3 implementations should be removed, not
> raised, given that that's the direction we'll have to move eventually.
>
> - Utilize new language features such as the @-operator and required
> keyword arguments
>
> These are not available unless we make Python 3 the default.
>

Hi Stefan, do you propose then to drop Python 3.4 at the same time (@ is >=
3.5)?

Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-image/attachments/20160810/bb0be5d1/attachment.html>


More information about the scikit-image mailing list