BUG: SPEC filewriter scan numbering and newfile() when file exists #138
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
prjemian
changed the title
|
coveralls reports a big drop in number of lines tested in filewriters.py. This reduction is a false observation since the number of tests has increased from 1 to 8. What it means is that there is more code to be tested. The coveralls web page highlights in red what has not been tested. tl;dr: acceptable as-is |
prjemian
modified the milestones:
milestone-2019-09,
release 1.1.5 for 2019-05 shutdown
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.
resolve problems with
newfile()when file exists