DM-4953: Don't print lsstcppimport err message if we're inside Scons. #17
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
timj
approved these changes
Aug 2, 2017
python/lsstimport.py
Outdated
| try: | ||
| import SCons.Script | ||
| # If we're not, then we will get an ImportError trying to import SCons.Script | ||
| # If we're not, then that first ImportError is a problem and we should |
There was a problem hiding this comment.
doubled "If we're not" looks wrong.
timj
changed the title
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.
I added a check that tries to
import SCons.Scriptto check to see if we're in Scons. If we are, then no worries. If we're not, then still print out the warning to STDERR.@timj Does this look right?