-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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 pymc3-3.0rc5.tar.gz has no package directory 'docs' #1633
Comments
Cc @fonnesbeck
…On 1 Jan 2017 9:13 PM, "Yves-Alexandre de Montjoye" < ***@***.***> wrote:
I just tried installing pymc3 using pip on a clean Ubuntu 16.04 and it
seems that a directory docs" is missing
best, Yves-Alexandre
pip install -U pymc3
Collecting pymc3
Downloading pymc3-3.0rc5.tar.gz (992kB)
100% |████████████████████████████████| 993kB 959kB/s
Complete output from command python setup.py egg_info:
WARNING: '.' not a valid package name; please use only .-separated package
names in setup.py
/usr/lib/python2.7/dist-packages/setuptools/dist.py:285: UserWarning:
Normalizing '3.0.rc5' to '3.0rc5'
normalized_version,
running egg_info
creating pip-egg-info/pymc3.egg-info
writing requirements to pip-egg-info/pymc3.egg-info/requires.txt
writing pip-egg-info/pymc3.egg-info/PKG-INFO
writing top-level names to pip-egg-info/pymc3.egg-info/top_level.txt
writing dependency_links to pip-egg-info/pymc3.egg-info/
dependency_links.txt
writing manifest file 'pip-egg-info/pymc3.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
error: package directory 'docs' does not exist
----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in
/tmp/pip-build-u3oT51/pymc3/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1633>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA8DiOO0FxYtXNOZ0vPy8lUoiIbzUqZhks5rOBb4gaJpZM4LYxpy>
.
|
Incidentally this causes a break in https://ci.appveyor.com/project/conda-forge/pymc3-feedstock/build/1.0.13/job/8cnj2qv15njfkvxy too |
Works great, thanks! |
With rc6?
…On 2 Jan 2017 10:22 AM, "Yves-Alexandre de Montjoye" < ***@***.***> wrote:
Works great, thanks!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1633 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA8DiNf_8ysCaYxm-oeT3_JOfyJDG1uaks5rOM_vgaJpZM4LYxpy>
.
|
Nope, I guess you rolled back to 3.0.rc4 on pip?
In [2]: pymc3.__version__
Out[2]: '3.0.rc4'
…On 02/01/17 12:30, Peadar Coyle wrote:
With rc6?
On 2 Jan 2017 10:22 AM, "Yves-Alexandre de Montjoye" <
***@***.***> wrote:
> Works great, thanks!
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#1633 (comment)>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AA8DiNf_8ysCaYxm-oeT3_JOfyJDG1uaks5rOM_vgaJpZM4LYxpy>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1633 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgtA3oF9o4wIVLCugYKYLwuSVjc3i6wks5rON_RgaJpZM4LYxpy>.
|
https://pypi.python.org/pypi/pymc3 shows rc6 being available. How did you upgrade? |
Just upgraded and it works great.
best, Yves-Alexandre
In [1]: import pymc3
In [2]: pymc3.__version__
Out[2]: '3.0.rc6'
…On 02/01/17 14:19, Thomas Wiecki wrote:
https://pypi.python.org/pypi/pymc3 shows rc6 being available. How did
you upgrade?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1633 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgtA5Nf5rWE9kQdXBMSTtzAqTW8tSpsks5rOPlRgaJpZM4LYxpy>.
|
Great, thanks for testing. |
Of course, thanks for the great work!
…On Mon, Jan 2, 2017 at 2:58 PM, Thomas Wiecki ***@***.***> wrote:
Great, thanks for testing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1633 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgtA8T95gINjkNkV13umNi2tcDnxXRIks5rOQKegaJpZM4LYxpy>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just tried installing pymc3 using pip on a clean Ubuntu 16.04 and it seems that a directory docs" is missing
best, Yves-Alexandre
pip install -U pymc3
Collecting pymc3
Downloading pymc3-3.0rc5.tar.gz (992kB)
100% |████████████████████████████████| 993kB 959kB/s
Complete output from command python setup.py egg_info:
WARNING: '.' not a valid package name; please use only .-separated package names in setup.py
/usr/lib/python2.7/dist-packages/setuptools/dist.py:285: UserWarning: Normalizing '3.0.rc5' to '3.0rc5'
normalized_version,
running egg_info
creating pip-egg-info/pymc3.egg-info
writing requirements to pip-egg-info/pymc3.egg-info/requires.txt
writing pip-egg-info/pymc3.egg-info/PKG-INFO
writing top-level names to pip-egg-info/pymc3.egg-info/top_level.txt
writing dependency_links to pip-egg-info/pymc3.egg-info/dependency_links.txt
writing manifest file 'pip-egg-info/pymc3.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-u3oT51/pymc3/
The text was updated successfully, but these errors were encountered: