In file/spec.py, accommodate files containing multiple adjacent heade… #6
Conversation
This file contains hidden or 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
Contributor
Author
|
Also, is it possible to make a new release of pyspec that contains these fixes available on pypi? |
kpwelsh
added a commit
to Verdant-Evolution/chess-pyspec
that referenced
this pull request
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…r sections
When there is more than one adjacent header section beginning with "#E" or "#F", parse them as separate header sections. When multiple adjacent sections all contain "#O" lines with motor names, the
FileBlockto which they all belong has duplicate copies of the motor names, so all following scans have a mismatching # of motor positions and motor names, so those scans havescan.motor_positions == None.