Skip to content

Update Contributing Environment section #18052

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

Merged
merged 8 commits into from
Nov 2, 2017

Conversation

TomAugspurger
Copy link
Contributor

Closes #18041
Closes #17544
Closes #17747

Still need to

  1. Maybe add a section on getting compilers
  2. Update the windows environment section
  3. More rewording on the docs

But I wanted to get this out there to check if people are OK with the general approach of

  1. first conda environment.yaml file with all the build deps
  2. second conda requirements file with all the optional deps
  3. Instruct contributors to just install everything
  4. A script to create requirements.txt files from the conda files for people using virtualenv / pip
  5. Just focusing on python3

And if people are able to test this on their machine I'd be grateful. I've tested both conda and pip/venv on my mac.

@jreback jreback added the Docs label Oct 31, 2017
@jreback
Copy link
Contributor

jreback commented Oct 31, 2017

general approach looks nice.

of the docs, greatly reducing the turn-around time for checking your changes.
You will be prompted to delete ``.rst`` files that aren't required. This is okay because
the prior versions of these files can be checked out from git. However, you must make sure
You can tell ``make.py`` to compile only a single section of the docs, greatly
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add a pointer that says the very first thing you have to do is create the dev env (refer to the section above)

@codecov
Copy link

codecov bot commented Oct 31, 2017

Codecov Report

Merging #18052 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #18052      +/-   ##
==========================================
- Coverage   91.24%   91.23%   -0.02%     
==========================================
  Files         163      163              
  Lines       50114    50114              
==========================================
- Hits        45729    45720       -9     
- Misses       4385     4394       +9
Flag Coverage Δ
#multiple 89.04% <ø> (ø) ⬆️
#single 40.24% <ø> (-0.06%) ⬇️
Impacted Files Coverage Δ
pandas/io/gbq.py 25% <0%> (-58.34%) ⬇️
pandas/core/frame.py 97.75% <0%> (-0.1%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4578a03...eecb9fc. Read the comment docs.

@TomAugspurger TomAugspurger changed the title [WIP] Update Contributing Environment section Update Contributing Environment section Oct 31, 2017
Copy link
Member

@jorisvandenbossche jorisvandenbossche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this!

@@ -0,0 +1,27 @@
# This file was autogenerated by scripts/convert_deps.py
# Do not modify directlybeautifulsoup4
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing a new line in the convert script

to updating. This will effectively store your changes and they can be reapplied
after updating.
Let us know if you have any difficulties by `opening an issue
<https://github.com/pandas-dev/pandas/issues/new>`_.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe rather point to asking on gitter compared to directly opening an issue? (or both)

- Install either :ref:`Anaconda <install.anaconda>` or :ref:`miniconda <install.miniconda>`
- Install either `Anaconda <https://www.anaconda.com/download/>`_ or `miniconda
<https://conda.io/miniconda.html>`_
- Make sure your conda is up to date (`conda update conda`)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

double backticks


To work in this environment, Windows users should ``activate`` it as follows::
# Install the rest of the optional dependencies
conda install -c defaults -c conda-forge --file=ci/requirements-optional-conda.txt
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this exactly do by specifying both? First look at defaults and otherwise look at conda-forge?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct. IIRC we have deps that are conda-forge only. I suppose we maybe just to -c conda-forge and no defaults.


Creating a development environment
----------------------------------
Creating a Python Environment
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add "(conda)" between brackets? (as is done for pip)


or use the `Microsoft Visual Studio VC++ compiler for Python <https://www.microsoft.com/en-us/download/details.aspx?id=44266>`__. Note that you have to check the ``x64`` box to install the ``x64`` extension building capability as this is not installed by default.
Creating a Python Environment (pip)
-----------------------------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this have the same header level as the conda one?

ipython
ipykernel
jinja2
lxml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you added this already (lxml), thanks!

git rebase upstream/master
- https://blogs.msdn.microsoft.com/pythonengineering/2016/04/11/unable-to-find-vcvarsall-bat/
- https://github.com/conda/conda-recipes/wiki/Building-from-Source-on-Windows-32-bit-and-64-bit
- https://cowboyprogrammer.org/building-python-wheels-for-windows/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should prob update these and eliminate the older ones

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I'll go through these later today and remove the old / outdated ones.

@jreback jreback added this to the 0.21.1 milestone Nov 1, 2017
@jreback jreback merged commit 0fd3bd7 into pandas-dev:master Nov 2, 2017
@jreback
Copy link
Contributor

jreback commented Nov 2, 2017

thanks @TomAugspurger awesome!

@jreback
Copy link
Contributor

jreback commented Nov 2, 2017

in future PR can add a note in the documentation section of whatsnew

ghost pushed a commit to reef-technologies/pandas that referenced this pull request Nov 3, 2017
1kastner pushed a commit to 1kastner/pandas that referenced this pull request Nov 5, 2017
No-Stream pushed a commit to No-Stream/pandas that referenced this pull request Nov 28, 2017
@TomAugspurger TomAugspurger deleted the contributing-environment branch December 8, 2017 18:28
TomAugspurger added a commit to TomAugspurger/pandas that referenced this pull request Dec 8, 2017
TomAugspurger added a commit that referenced this pull request Dec 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants