You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Fokko Driesprong (JIRA)" <ji...@apache.org> on 2018/11/07 22:16:00 UTC
[jira] [Assigned] (AVRO-2240) egg_info fails for avro-python3 using
python2
[ https://issues.apache.org/jira/browse/AVRO-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fokko Driesprong reassigned AVRO-2240:
--------------------------------------
Assignee: Michael A. Smith
> 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)