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

Investigate installing our own Python on Windows, or at least creating our own venv #176

Open
jackjansen opened this issue Jan 17, 2025 · 1 comment
Assignees
Milestone

Comments

@jackjansen
Copy link
Contributor

The dependency on the System Python is too cumbersome and error-prone.

But the problem is that that will forestall using cwipc for things like point cloud analysis, or at least make it a lot more difficult.

@jackjansen
Copy link
Contributor Author

Turns out it was easy: we create a venv in libexec/cwipc in which we install the cwipc modules, and then we copy the executables from there over into our bin directory.

And if people want to install the cwipc package into another venv (or another Python, or whatever) they can simply run cwipc_pymodules_install with whatever Python they want and also have everything available there.

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

No branches or pull requests

1 participant