11Introduction
22============
33
4- This docmentation provides a guide for pymatgen administrators. The following
4+ This documentation provides a guide for pymatgen administrators. The following
55assumes you are using miniconda or Anaconda.
66
77Releases
@@ -23,18 +23,18 @@ Install some conda tools first::
2323 conda install --yes conda-build anaconda-client
2424 conda config --add channels matsci
2525
26- Pymatgen uses `invoke <http://www.pyinvoke.org/ >`_ to automate releases. You will
26+ Pymatgen uses `invoke <http://www.pyinvoke.org/ >`_ to automate releases. You will
2727also need sphinx and doc2dash. Install these using::
2828
2929 pip install --upgrade invoke sphinx doc2dash
3030
31- For 2018, we will release both py27 and py37 versions of pymatgen. Create
31+ For 2018, we will release both py27 and py37 versions of pymatgen. Create
3232environments for py27 and py37 using conda::
3333
3434 conda create --yes -n py37 python=3.7
3535 conda create --yes -n py27 python=2.7
3636
37- For each env, install some packages using conda followed by dev install for
37+ For each env, install some packages using conda followed by dev install for
3838pymatgen::
3939
4040 conda activate py37
@@ -50,43 +50,43 @@ pymatgen::
5050 pip install invoke sphinx doc2dash
5151 python setup.py develop
5252
53- Add your PyPI username and password and GITHUB_RELEASE_TOKEN into your
53+ Add your PyPI username and password and GITHUB_RELEASE_TOKEN into your
5454environment::
5555
5656 export TWINE_USERNAME=PYPIUSERNAME
5757 export TWINE_PASSWORD=PYPIPASSWORD
5858 export GITHUB_RELEASES_TOKEN=TOKEN_YOU_GET_FROM_GITHUB
5959
60- You may want to add these to your .bash_profile to avoid having to type these
60+ You may want to add these to your .bash_profile to avoid having to type these
6161each time.
6262
6363Machine-specific issues
6464~~~~~~~~~~~~~~~~~~~~~~~
6565
66- The above instructions are general, but there are some known issues that are
66+ The above instructions are general, but there are some known issues that are
6767machine-specific:
6868
69- * Installing lxml via pip required `STATIC_DEPS=true pip install lxml ` on
69+ * Installing lxml via pip required `STATIC_DEPS=true pip install lxml ` on
7070 macOS 10.13.
71- * It can be useful to `pip install --upgrade pip twine setuptools ` (this may
71+ * It can be useful to `pip install --upgrade pip twine setuptools ` (this may
7272 be necessary if there are authentication errors when connecting to PyPI).
7373* You may have to `brew install hdf5 netcdf ` or similar to be able to pip
7474 install the optional requirement `netCDF4 `.
7575
7676Doing the release
7777-----------------
7878
79- Ensure appropriate environment variabels are set including `DISCOURSE_API_USERNAME `,
79+ Ensure appropriate environment variables are set including `DISCOURSE_API_USERNAME `,
8080`DISCOURSE_API_KEY ` and `GITHUB_RELEASES_TOKEN `.
8181
82- First update the change log. The autogenerated change log is simply a list of
82+ First update the change log. The autogenerated change log is simply a list of
8383commit messages since the last version. Make sure to edit the log for brevity
8484and to attribute significant features to appropriate developers::
8585
8686 conda activate py37
8787 invoke update-changelog
8888
89- Then, do the release with the following sequence of commands (you can put them
89+ Then, do the release with the following sequence of commands (you can put them
9090in a bash script in your PATH somewhere)::
9191
9292 conda activate py37
@@ -97,7 +97,7 @@ in a bash script in your PATH somewhere)::
9797 python setup.py develop
9898
9999Double check that the releases are properly done on Pypi. If you are releasing
100- on a Mac, you should see a pymatgen.version.tar.gz and two wheels (Py37 and
100+ on a Mac, you should see a pymatgen.version.tar.gz and two wheels (Py37 and
101101P). There will be a py37 wheel for Windows that is generated by Appveyor.
102102
103103Materials.sh
0 commit comments