Add new tag for astroconda incorporation #135
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
I'm going to try to do this (https://github.com/keflavich/specutils/tree/v0.2.1) |
|
@keflavich Can you make a tag for this so the astroconda channel can build against it? |
|
@nmearl done. I had forgotten that the merge didn't include the tag. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The astroconda maintainers usually use tags when incorporating packages into the anaconda channel. Obviously, the v0.2 tag is outdated with our current changes (not to mention, the fix for
setup.pyis not in the tagged version, meaning it suffers from the python 3.5.2ConfigParser()regression).A new tag should be created for the current version of specutils (v0.2.1?) encompassing the new Spectrum1DRef object and the
setup.pyfixes.