Cluster-lensing

Latest version: v0.1.2

Safety actively analyzes 688867 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

0.1.2

* clusters.ClusterEnsemble() accepts input cosmology as any astropy.cosmology object

0.1.1

* fixed miss-spelling of "richness" in function names:
- mass\_to\_richess() => mass\_to\_richness()
- richess\_to\_mass() => richness\_to\_mass()
* confirmed compatibility with Python 3.4, 3.5

v0.1.0 (14 Feb 2016) -- Initial release.


How to Release

Here's my step-by-step guide for cutting a new release of
**cluster-lensing**. Thanks to Jake VanderPlas for showing the way!

Pre-release

1. update version in ``setup.py``

2. update version in ``clusterlensing/__init__.py``

3. update version in ``docs/conf.py`` (two places!)

4. update change log in ``CHANGES.md``

5. update ``README.md`` and `` demo.ipynb`` if necessary

6. confirm all tests pass & flake8 gives no errors

$ cd clusterlensing/
$ nosetests
$ flake8 --ignore N802,N806 `find . -name \*.py | grep -v setup.py | grep -v /doc/`


7. create a release tag; e.g.

$ git tag -a v0.1.1 -m 'version 0.1.1 release'


8. push the commits and tag to github; e.g.


$ git push origin v0.1.1
$ git push origin master


9. confirm that CI tests pass on github

10. under "tags" on github, update the release notes

11. push the new release to PyPI:

$ python setup.py sdist upload


12. change directories to ``docs`` and build the documentation:

$ cd docs/
$ make html build documentation
$ make publish publish to github pages
$ make publish and again to really publish


Post-release

1. update version in ``setup.py`` to next version; e.g. '0.3-git'

2. update version in ``clusterlensing/__init__.py`` to the same

3. update version in ``docs/conf.py`` to the same (in two places)

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.