RetroSearch Browse

Sun May 8 22:39:51 EDT 2016 · https://mail.python.org/pipermail/python-dev/2016-May/144488.html

On 05/08/2016 07:15 PM, Nick Coghlan wrote:
> On 9 May 2016 at 08:43, Ethan Furman wrote:

>> It's a 2/3 compatibility issue with enum34 and aenum which support _order_,
>> and Python3.4+ which does not.  The work-around is to use __order__ instead
>> (or use enum34 or aenum instead ;) .
>
> Needing to use a PyPI alternative to a stdlib module for increased
> cross-version consistency is a pretty common experience these days, so
> I think that's OK - end users can choose for themselves between the
> stability of the stdlib version and the reduced update latency of the
> PyPI version.

Are you saying I shouldn't bother updating the 3.6 Enum to ignore _order_?

--
~Ethan~

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-May/144488.html below:

[Python-Dev] Minor change to Enum -- should it go into 3.5.2?