-
Notifications
You must be signed in to change notification settings - Fork 666
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
migration guide for 0.10 to 0.11 transition #381
Comments
This was referenced Aug 5, 2015
MDAnalysis 0.11 user guide sections that require developer verification (please edit and fill in as below if you are comfortable verifying an example covering a particular API change):
|
Note on deprecations: anything that was deprecated should be changed. A user who has applied all changes in the guide should not see any deprecation warnings any more. |
orbeckst
added a commit
that referenced
this issue
Sep 5, 2015
Feature merged ten2eleven: migration from 0.10 to 0.11 with MDAnalysis.ten2eleven() Closes #377. We still need docs #381 (specifically [Migrating MDAnalysis code with ten2eleven.py](/MDAnalysis/mdanalysis/wiki/Migrating-MDAnalysis-code-with-ten2eleven.py)) but we can tackle this better with `ten2eleven` in place. I will consider this merge to close #377 even though we have not full resolved `.frames` handling. If anything major comes up, we will re-open #377.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the big API changes in the 0.11.0 release, we need documentation to support the users in transitioning their existing code. @tylerjereddy already started the wiki page MDAnalysis 0.11 unifying release user guide.
This page (and possibly others, as needed, such as the Releases Notes for 0.11.0) have to be up-to-date and complete before the release so that we can send users to those pages.
The text was updated successfully, but these errors were encountered: