[
https://issues.apache.org/jira/browse/AVRO-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679485#comment-16679485
]
Piotr Gołąb commented on AVRO-2240:
-----------------------------------
Oh, I guess It's too late to say something - I found this PR just this morning.
Isn't the decision to use Python 3.4 too conservative? 3.4 was released on 2014
and I strongly believe that we should be as up-to-date as possible. 3.4 is used
by around 13% of users as shown by Scott Belden and indeed this will shrink. At
the same time we cannot use some of the features that seem obvious in Python 3
(f string formatting, etc.).
I think we should drop 3.4 (builds are passing for 3.5) support and focus on
newer versions. We'll have to do it eventually anyway.
> egg_info fails for avro-python3 using python2
> ---------------------------------------------
>
> Key: AVRO-2240
> URL: https://issues.apache.org/jira/browse/AVRO-2240
> Project: Apache Avro
> Issue Type: Bug
> Components: python
> Affects Versions: 1.8.2
> Reporter: Luke Zulauf
> Assignee: Michael A. Smith
> Priority: Major
> Fix For: 1.9.0
>
>
> When managing dependencies, the ability to call egg_info on any package is
> especially useful (even if the package is not valid for installation with a
> specific python version).
> For example, pipenv can't build a lockfile in python2 if avro-python3 is
> listed as a dependency (for any python version)
>
> The opposite works (using python3 to check the egg_info of avro (the python2
> version).
>
> {code:java}
> $ python3 avro/setup.py egg_info
> (succeeds)
> $ python2 avro/setup.py egg_info
> (succeeds)
> $ python3 avro-python3/setup.py egg_info
> (succeeds)
> $ python2 avro-python3/setup.py egg_info
> (fails){code}
> It would be great if you didn't raise an assertion error for all usages of
> running setup.py, especially when running egg_info.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
