Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split up properties.py #5626

Closed
bryevdv opened this issue Dec 28, 2016 · 0 comments
Closed

Split up properties.py #5626

bryevdv opened this issue Dec 28, 2016 · 0 comments

Comments

@bryevdv
Copy link
Member

@bryevdv bryevdv commented Dec 28, 2016

With more users writing extensions, it is now important to have better documentation about writing models, using properties, etc. The properties.py currently has a lot of very low level base classes, etc. that users should not really be concerned with. Propose to split off all the low level machinery into property_bases.py or similar, and leave properties.py only containing things that users might care about. Then to structure the documentation appropriately (e.g. splitting into spearete sections for basic properties and dataspecs)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant