Skip to content
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

Add infos how to handle times in Gammapy #285

merged 6 commits into from Jun 12, 2015


Copy link

@cdeil cdeil commented Jun 12, 2015

This PR adds a first description how to use times in Gammapy.

The discussion in this started in #278
This will not be fully addressed here, further discussion / work is needed, see #284

@cdeil cdeil self-assigned this Jun 12, 2015
@cdeil cdeil added this to the 0.3 milestone Jun 12, 2015
cdeil added a commit that referenced this pull request Jun 12, 2015
Add infos how to handle times in Gammapy
@cdeil cdeil merged commit fca3aa5 into gammapy:master Jun 12, 2015
.. code-block:: bash
$ rm -r build docs/_build docs/api htmlcov

This comment has been minimized.


mapazarr Jun 12, 2015

@cdeil Would it be possible to add a clean command to in order to be able to clean all the generated files that are always safe to delete?
I'd like the idea of being able to call
python clean
which internally should do
rm -rf build docs/_build docs/api htmlcov
(and eventually more things in the future, in case other to-come dependecies/developments create generated files other places).
My point is: it's hard to remember where all generated files are located (and as you say, they might cause trouble sometimes) and a simple clean command should easily do the trick.

This comment has been minimized.


cdeil Jun 12, 2015
Author Member

@mapazarr – Completely agree. There is one or several clean commands. I don't know what they do exactly or if they could be modified in Astropy or Gammapy to do exactly what we want. If you want you can look into this, but my guess is that it's hard to understand, especially for someone like you or me that's not a Python setuptools expert.

This comment has been minimized.


mapazarr Jun 13, 2015

@cdeil: please see PR #289.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants