Repository navigation
remove clean_parse_tables.py (to be moved to astropy-tools) - #4300
Conversation
|
👍 |
|
Perhaps this should be accompanied with a few comments in the relevant source files as to where to get this script, and that it should be run when updating the parser/lexers. |
|
@embray - good point - how about the README I just added? |
|
@astrofrog - this seems really weird... Not important for the PR itself, but possibly signifying a coveralls issue? |
|
The readme isn't too helpful because who would know to go looking for it? It's not in a place where anyone would look when making updates to the parsers. Instead it would be good to just have a short comment directly in the code such as in this file: https://github.com/astropy/astropy/blob/master/astropy/units/format/cds.py#L27 |
|
Additionally, mixing our own files with vendored code is confusing. |
|
@embray - so you're thinking everywhere that there's a lextab/parsetab? I confess I don't really understand when/how those files are generated, so I could be confused. If you (or @mdboom) have a specific idea of where this is most likely to be recognized, a PR to my branch might be fastest. Or maybe the best solution is for someone (probably shouldn't be me given the above...) to add a developer doc along the lines of "Upkeep of PLY-generated files in astropy"? |
|
It's only used in a handful of files: Just a copy/pasted comment near the top of all of those files should suffice. |
|
@eteq - Re If this right, rebasing this should make the fail go away (given that no change happens in master in the meantime). |
87ec54f to
1332648
Compare
|
OK, is this what you mean, @embray (the commit I just pushed up)? Again, I really don't understand what PLY/lex/yacc are doing and when the tables are getting generated, so I just sort of made this up... |
|
This is fine. |
|
Alright, I'll go ahead and merge. |
remove clean_parse_tables.py (to be moved to astropy-tools)
remove clean_parse_tables.py (to be moved to astropy-tools)
|
backported to v1.1.x in c8f65a0 |
This PR removes the
dev/clean_parse_tables.pyfile, as a companion to astropy/astropy-tools#8, which adds it to astropy-tools.Does this seem reasonable, @mdboom ? It looks to be like this dev directory was added in #4003 for just this file, and it looks to me like this script fits better with the other tools in astropy-tools as a "script which is useful for developing astropy, but not necessary for the package itself". Does that sound right, or is there a reason why
clean_parse_tables.pyshould stay in the core vs astropy-tools?(Note that I'm milestoning this v1.1 because I think we don't want
devto appear in the repo and then disappear again later)