Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pip Install Fails with Python 3 #75

Open
vabaimova opened this issue Sep 12, 2018 · 2 comments
Open

Pip Install Fails with Python 3 #75

vabaimova opened this issue Sep 12, 2018 · 2 comments

Comments

@vabaimova
Copy link

vabaimova commented Sep 12, 2018

I've tried both of the commands listed in the documentation to install pyoracc using pip, but both fail since the setup script uses Python 2 syntax for a print statement.

I was able to successfully do it by following the more explicit step by step instructions (clone the repo, cd into the repo, then pip install), but as Python 2 will no longer be supported very soon, I figure that this is a minor bug that should be addressed.

@raquelalegre
Copy link
Contributor

raquelalegre commented Sep 12, 2018

Thanks for reporting this, @vabaimova. I think the README in this repository needs changing.

This repository contains a version of pyoracc that works in both Python 2 and Python 3 and is tested using Travis for both versions overnight. It has also been released on PyPI and you can install it as:

pip install pyoracc

@jayanthjaiswal has worked on a new version of this repository in a fork in https://github.com/cdli-gh/pyoracc.git. That repository (which is referred to from the installation instructions in the README) is the one that is failing for Python 3, and it hasn't been released with PyPI yet.

So, the README in this repo is a bit confusing and we need to change it. We also should probably clarify the issue about the two different versions of PyOracc and consolidate in a single version soon. What do you think, @jayanthjaiswal?

@raquelalegre
Copy link
Contributor

I have updated the comment above because there were some inaccuracies in it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants