Skip to content

remove clean_parse_tables.py (to be moved to astropy-tools) - #4300

Merged
eteq merged 2 commits into
astropy:masterfrom
eteq:clean-parse-tables
Nov 17, 2015
Merged

eteq merged 2 commits into
astropy:masterfrom
eteq:clean-parse-tables

Conversation

@eteq

@eteq eteq commented Nov 9, 2015

Copy link
Copy Markdown
Member

This PR removes the dev/clean_parse_tables.py file, 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.py should stay in the core vs astropy-tools?

(Note that I'm milestoning this v1.1 because I think we don't want dev to appear in the repo and then disappear again later)

@eteq eteq added the Affects-dev PRs and issues that do not impact an existing Astropy release label Nov 9, 2015
@eteq eteq added this to the v1.1.0 milestone Nov 9, 2015
@embray

embray commented Nov 12, 2015

Copy link
Copy Markdown
Member

👍

@embray

embray commented Nov 12, 2015

Copy link
Copy Markdown
Member

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.

@eteq

eteq commented Nov 13, 2015

Copy link
Copy Markdown
Member Author

@embray - good point - how about the README I just added?

@eteq

eteq commented Nov 13, 2015

Copy link
Copy Markdown
Member Author

@astrofrog - this seems really weird... coveralls said coverage decreased, but the only change here is removing code that definitely was not being tested. So the denominator should shrink and therefore coverage should have increased, right?

Not important for the PR itself, but possibly signifying a coveralls issue?

@embray

embray commented Nov 13, 2015

Copy link
Copy Markdown
Member

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

@embray

embray commented Nov 13, 2015

Copy link
Copy Markdown
Member

Additionally, mixing our own files with vendored code is confusing.

@eteq

eteq commented Nov 13, 2015

Copy link
Copy Markdown
Member Author

@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"?

@bsipocz

bsipocz commented Nov 13, 2015

Copy link
Copy Markdown
Member

@eteq - Re coveralls: we saw this before with other PRs, too (e.g. #3628). My best guess was that the issue is somewhat related that the coverage changed between the base of this PR and the top of master, and the change this PR introduces is negative compared to that.

If this right, rebasing this should make the fail go away (given that no change happens in master in the meantime).

@eteq
eteq force-pushed the clean-parse-tables branch from 87ec54f to 1332648 Compare November 17, 2015 04:38
@eteq

eteq commented Nov 17, 2015

Copy link
Copy Markdown
Member Author

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...

@embray

embray commented Nov 17, 2015

Copy link
Copy Markdown
Member

This is fine.

@eteq

eteq commented Nov 17, 2015

Copy link
Copy Markdown
Member Author

Alright, I'll go ahead and merge.

eteq added a commit that referenced this pull request Nov 17, 2015
remove clean_parse_tables.py (to be moved to astropy-tools)
@eteq
eteq merged commit 606018b into astropy:master Nov 17, 2015
@eteq
eteq deleted the clean-parse-tables branch November 17, 2015 16:23
eteq added a commit to eteq/astropy that referenced this pull request Nov 17, 2015
remove clean_parse_tables.py (to be moved to astropy-tools)
@eteq

eteq commented Nov 17, 2015

Copy link
Copy Markdown
Member Author

backported to v1.1.x in c8f65a0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Affects-dev PRs and issues that do not impact an existing Astropy release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants