-
Notifications
You must be signed in to change notification settings - Fork 61
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
PyCVXQuad 10/21 #869
base: master
Are you sure you want to change the base?
PyCVXQuad 10/21 #869
Conversation
@simsaidan just FYI, I fixed the one merge conflict that was preventing the subsequent pipelines from running. We should now expect to see some linting failures, but these should be easy enough to resolve. Of course, don't hesitate to reach out if you'd like to ask any questions or if you want to triage some of these together. Let me know what makes sense for you! |
Hi @simsaidan, the docstring template in toqito's contributing guide is not up to date. I noticed it during your mid-point check-in presentation. My apologies! I am linking an example function for what it is supposed to look like: toqito/toqito/channel_props/is_unital.py Lines 58 to 62 in 3b91eb6
You have to use If you want to take a look at how the docstrings are formatted in the docs build, make sure you add your Edit: The docstring template should be corrected now. |
Hi @simsaidan, Can you please make title and summary of the PR more descriptive? It helps potential reviewers that are not familiar with your project. Also my advice would be to first make a smaller PR with a single quantity (+test and auxiliary functions, if needed) where we can agree on things like styles, module organization, test approach, dependencies. |
Description
Provide a brief description of the PR's purpose here. If your PR is supposed to fix an existing issue, use
a keyword to link your PR to the issue.
Changes
Notable changes that this PR has either accomplished or will accomplish. Feel free to add more lines to the itemized list
below.
Checklist
Before marking your PR ready for review, make sure you checked the following locally. If this is your first PR, you might be notified of some workflow failures after a maintainer has approved the workflow jobs to be run on your PR.
Additional information is available in the documentation.
ruff
for errors related to code style and formatting.pytest
.Sphinx
build can be checked locally for any failures related to your PRlinkcheck
to check for broken links in the documentationdoctest
to verify the examples in the function docstrings work as expected.