-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Gh actions for python #1721
Gh actions for python #1721
Conversation
Many thanks for the PR. Just a first test, I got a
It reminds me something similar for UTK, I'd need to investigate a bit. |
Ok something I should debug:
|
(ok problem solved.. just a conda issue) |
@@ -1,6 +1,7 @@ | |||
import pytest | |||
import dgtal | |||
|
|||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why such string statement ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This the pythonic way of doing multiline comments. As mentionned in the PR, those test do not run -- and this is not because of GH actions.
Very nice PR, thx @BDoignies . We should discuss a bit about this pypi thing.. |
In the |
You can follow the ".github/workflows/pythonBindings-PR.yml" from line 92 and onwards if you have any more questions about the test process. Here are the lines answering your question : In the build directory, run
You can also test that the module can be properly imported with the line :
|
You know where to find / contact me to setup a meeting for this ! |
I will ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging to test the deploy and GH
Just to make sure information is somewhere in case it is needed. Reasons for Pypi deployment to break:
|
PR Description
This PR proposes a redesign of the CI pipeline for Python binding. Mainly, this PR changes the CI backend from Azure to Github Actions.
I am not so sure about the review of this PR though, because it was tested on my repository and that some of the changes are repository-dependent (see below for a full list).
Quick overview of changes
ssize_t
variable is only POSIX and not standard. Hence Windows does not have it (technically#include <BaseTsd.h>
is possible, but I find it to be too heavy for a simple define).wrap/__init__.py
->wrap/deploy/__init__.py
. Previous location caused issues with CTest. As stated in pytest good practice, import are done differently when running tests.Some 'pending changes'
Repository-dependent changes
File
pythonBindings-PR.yml
is repository-independent and should run on any other fork. However the Pypi deployment is much more different.Some documentation about the process :
Currently the file is setup to:
What I did not test :
What's missing:
Documentation: I did not rewrite the documentation yet. I am waiting for any comments reviewers might have.
Github releases: It is possible to publish directly the .wheel and make them available as part of the tags.
Comments and reviews: I'm am neither an expert of Dgtal nor an expert of CI and python build. Any comments is welcome to make sure everything is fine and for the best 😺 !
Checklist
Most of the following are not applicable to this PR.