Skip to content

Match __repr__ to attribute - #4147

Merged
mhvk merged 3 commits into
astropy:masterfrom
DanielLenz:master
Sep 12, 2015
Merged

mhvk merged 3 commits into
astropy:masterfrom
DanielLenz:master

Conversation

@DanielLenz

Copy link
Copy Markdown

Rename Error -> Uncertainty and Units -> Unit in __repr__ to match the attributes.
Requested in #4145
Had to re-do the pull request because I messed up the branches.

Daniel added 2 commits September 11, 2015 17:42
In constant.py, rename units -> unit and error -> uncertainty to match __repr__ to attributes.
@pllim

pllim commented Sep 11, 2015

Copy link
Copy Markdown
Member

Note: Old PR was #4146.

👍 It seems uncontraversial. I would lean towards a change log, because why not?

@mhvk mhvk added the constants label Sep 11, 2015
@mhvk mhvk added this to the v1.1.0 milestone Sep 11, 2015
@mhvk

mhvk commented Sep 11, 2015

Copy link
Copy Markdown
Contributor

I think indeed it is best to err in the direction of too much information: @dienz-bonn: could you add an entry to the file CHANGES.rst? I think it would go under the header of Bug fixes (for 1.1), since really a repr is meant to be something that one can reproduce an instance with, and it would seema bug for it not to have the right names.

In the commit message for that change, you can add "[skip ci]", so that travis does not run again, and then this can be merged. Thanks!

@mhvk

mhvk commented Sep 11, 2015

Copy link
Copy Markdown
Contributor

Sorry for the misspelled id, @dlenz-bonn

Document renaming of units and error in __repr__ in the changes.
@DanielLenz

Copy link
Copy Markdown
Author

Thanks for the help, I added the changes to the change log. Note that I changed my username as well, but the commits should appear with the old id.

@mhvk

mhvk commented Sep 12, 2015

Copy link
Copy Markdown
Contributor

Great, thanks! Merging...

mhvk added a commit that referenced this pull request Sep 12, 2015
Match __repr__ to attribute
@mhvk
mhvk merged commit 7dce3a0 into astropy:master Sep 12, 2015
@embray

embray commented Sep 14, 2015

Copy link
Copy Markdown
Member

Why should this be limited to v1.1.0? This change can be backported to the v1.0.x branch.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should have been "uncertainty" in lowercase.

@embray

embray commented Sep 14, 2015

Copy link
Copy Markdown
Member

I'm putting this in 1.0.5.

@embray embray modified the milestones: v1.0.5, v1.1.0 Sep 14, 2015
@embray embray added the Bug label Sep 14, 2015
mhvk added a commit that referenced this pull request Sep 14, 2015
@embray embray mentioned this pull request Sep 16, 2015
dhomeier pushed a commit to dhomeier/astropy that referenced this pull request Dec 17, 2015
dhomeier pushed a commit to dhomeier/astropy that referenced this pull request Jun 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants