Pymc3: Pushing to PyPI for RC2

[springcoil]

Hi, who is pushing it to PyPI for RC2? Is it you Chris?

[fonnesbeck]

I will tag the release and post to PyPI

[springcoil]

Cool :)

[twiecki]

@fonnesbeck I think we can move ahead with this now.

[ericmjl]

Is #1339 resolved in RC2? I'm happy to start making a conda-forge recipe for this if it's not already being done.

[springcoil]

I think it's ok to move forward with a conda-forge recipe. Any objections @twiecki @fonnesbeck

[twiecki]

@ericmjl should be resolved, but we still need the release on pypi.

[ericmjl]

@twiecki: no problem with waiting for the release on PyPI. I'll get the recipe prepped nonetheless.

[fonnesbeck]

completed

[twiecki]

@ericmjl Do you think getting rc2 on conda forge is going to be quick? If so, we might as well wait with the announcement until that's ready.

[ericmjl]

@twiecki: I'll have to see how long the builds take, as well as when the conda-forge team approves the PR. What's your personal cut-off time? This evening, or next 1-2 days, or the end of the week?

[fonnesbeck]

@ericmjl There is no cutoff _per se_. As much as everyone wants to see the release, there is no reason to rush it.

[twiecki]

For reference: https://github.com/conda-forge/staged-recipes/pull/1704

[ericmjl]

@fonnesbeck thanks! :smile:

P.S. ever since attending your tutorial @ SciPy 2014 + listening to @twiecki's talk @ Boston Bayesians, I've started to have a ton of fun w/pymc3. Lovin' it!

[ericmjl]

It's looking like there's a bunch of dependencies that need to be built via conda-forge first. I'm slowly running into them:

• nbsphinx
• commonmark
• recommonmark

And then dependencies of the dependencies:

• configparser

I'll keep you guys posted.

[twiecki]

Hm, those are just required to build the docs, perhaps we can make them optional in pymc3?

[ericmjl]

Perhaps so, I guess? I think I can modify the pymc3 build script so that they aren't included or required.

[twiecki]

great

[ericmjl]

It's in building right now: https://github.com/conda-forge/staged-recipes/pull/1705

[ericmjl]

Not quite sure why this error is happening on the CI-build:

https://circleci.com/gh/conda-forge/staged-recipes/9809?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

Any ideas, @twiecki?

[twiecki]

creating /opt/conda/envs/_build_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.5/site-packages/pymc3

Is that weird directory name at fault perhaps?

[ericmjl]

Maybe, though on my local build that weird dir also shows up. I'll see what the conda-forge folks say about it as well.

[ericmjl]

The PR has been merged! :smile: https://github.com/conda-forge/staged-recipes/pull/1705

Just waiting for the feedstock to be created, and it'll be up on conda-forge. There is one minor issue with the Windows build - had to do with matplotlib. The matplotlib folks will have to take care of it.

I also submitted PRs for the dependencies that are needed in building the docs, just to make things complete.

[fonnesbeck]

Fantastic, thanks!