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.

Sign up for GitHub

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

Jump to bottom

Improve test coverage of C++ parts of Python API #12705

Closed
martyngigg opened this issue May 29, 2015 · 3 comments
Closed

Improve test coverage of C++ parts of Python API #12705

martyngigg opened this issue May 29, 2015 · 3 comments
Labels
Maintenance Unassigned issues to be addressed in the next maintenance period. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@martyngigg
Copy link
Member

This issue was originally TRAC 11867

Parts of the PythonInterface have introduced additional C++ classes and functions to over and above the standard boost functionality. The test coverage is patchy as in the past it was difficult to get the required Python environment running so that the Python objects would be in a valid state.

We should re-examine this again and try to do better.

Keywords: Maintenance
@martyngigg martyngigg added Python Maintenance Unassigned issues to be addressed in the next maintenance period. labels Jun 3, 2015
@martyngigg martyngigg self-assigned this Jun 3, 2015
@martyngigg martyngigg added this to the Release 3.6 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper NickDraper modified the milestones: Release 3.7, Release 3.8 May 20, 2016
@NickDraper NickDraper modified the milestones: Release 3.8, Release 3.9 Oct 3, 2016
@NickDraper NickDraper modified the milestones: Release 3.9, Temporary Holding Oct 14, 2016
@NickDraper NickDraper removed this from the Temporary Holding milestone Oct 3, 2017
@martyngigg martyngigg removed their assignment Jul 15, 2019
@martyngigg
Copy link
Member Author

Dropping this into the general maintenance pool. It also requires #26334 to be done first.

@gemmaguest gemmaguest removed the Python label Jul 29, 2020
@stale
Copy link

stale bot commented Feb 22, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 22, 2021
@stale
Copy link

stale bot commented Mar 1, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Maintenance Unassigned issues to be addressed in the next maintenance period. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martyngigg @NickDraper @gemmaguest