[
https://issues.apache.org/jira/browse/AVRO-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678866#comment-16678866
]
ASF subversion and git services commented on AVRO-2240:
-------------------------------------------------------
Commit 6527d6d1d5081d38168b9ea14bd7d715c5e2af8d in avro's branch
refs/heads/master from [~kojiro]
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=6527d6d ]
AVRO-2240 Fix py3 Setup (#347)
* AVRO-2240 Make setup.py python2 compatible
Indicate that avro-python3 is only python3 compatible without making the
setup script itself incompatible with python 2.
Fix a bug with chmod in setup.py
Add trove classifiers to setup.py
* Specify Python 3.4 and Up
Lazy Consensus per the utter silence of
https://mail-archives.apache.org/mod_mbox/avro-dev/201810.mbox/%3CCA%2BB44%2BC0MLQreV2tozd8GFv74qnyBT0%2B3rd44Ey29Gv4T_9%2B3Q%40mail.gmail.com%3E.
* AVRO-2240 Remove Junk
> 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)
