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 pyro-ppl failing in Python 3 #1759

Closed
fritzo opened this issue Feb 14, 2019 · 1 comment
Closed

pip install pyro-ppl failing in Python 3 #1759

fritzo opened this issue Feb 14, 2019 · 1 comment
Assignees

Comments

@fritzo
Copy link
Member

fritzo commented Feb 14, 2019

$ conda create -n test3 python=3
...
$ source activate test3
$ pip install pyro-ppl
Collecting pyro-ppl
  Downloading https://files.pythonhosted.org/packages/75/0e/e6013ad748349e447c6da7ba0b3d66950e834a5b45a0ff426c131b00cde5/pyro-ppl-0.3.1.tar.gz (207kB)
    100% |████████████████████████████████| 215kB 4.9MB/s
    Complete output from command python setup.py egg_info:
    fatal: Not a git repository (or any of the parent directories): .git
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/c5/cqn89jt900v5tmm2y7p0tf4r0000gn/T/pip-install-6feboagj/pyro-ppl/setup.py", line 25, in <module>
        cwd=PROJECT_PATH).decode('ascii').strip()
      File "/Users/fritzobermeyer/miniconda2/envs/test3/lib/python3.7/subprocess.py", line 395, in check_output
        **kwargs).stdout
      File "/Users/fritzobermeyer/miniconda2/envs/test3/lib/python3.7/subprocess.py", line 487, in run
        output=stdout, stderr=stderr)
    subprocess.CalledProcessError: Command '['git', 'tag', '--points-at', 'HEAD']' returned non-zero exit status 128.

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/c5/cqn89jt900v5tmm2y7p0tf4r0000gn/T/pip-install-6feboagj/pyro-ppl/
@fritzo fritzo self-assigned this Feb 14, 2019
@fritzo
Copy link
Member Author

fritzo commented Feb 14, 2019

Seems to be fixed by our 0.3.1.post1 release.

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

No branches or pull requests

1 participant