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

How much work would require to port Python code to 3.X? #206

Open
lpgasparotto opened this issue Apr 23, 2022 · 13 comments
Open

How much work would require to port Python code to 3.X? #206

lpgasparotto opened this issue Apr 23, 2022 · 13 comments

Comments

@lpgasparotto
Copy link
Contributor

Since most Linux distros provide Boost compiled against Python 3.X HeeksCNC will not compile/work properly unless Boost be recompiled against Python 2.7 and override default version. This workaround could affect other applications which use Boost (i.e. FreeCAD). Also, the Boost manual installation is not that straight forward.

I'm willing to help in whatever I could. There's a kind of migration tool, I gues it's called 2to3, which could automate a considerable part of the process. Main differences are related to the way modules are imported and other minimal syntax differences.

@bullestock
Copy link

I have created a fork at https://github.com/bullestock/heekscnc/ which, among other fixes, uses Python 3.

@lpgasparotto
Copy link
Contributor Author

Great!!! Thank you very much for doing it. Will you make a pull request?

@bullestock
Copy link

@lpgasparotto I have done so much code cleanup on my own fork that it's quite complicated to create pull requests.

@lpgasparotto
Copy link
Contributor Author

Keep me in mind if you need help. I't would be a pleasure to help you in whatever you need and I be able to do.

@lpgasparotto
Copy link
Contributor Author

lpgasparotto commented Jan 9, 2023 via email

@bullestock
Copy link

@lpgasparotto I just tried to compile my fork now, and while I was able to fix some of the errors, there is still a single instance of the deprecated Nodes() call that I couldn't quickly figure out how to convert. Anyway, the fixes are pushed.

@lpgasparotto
Copy link
Contributor Author

lpgasparotto commented Jan 10, 2023 via email

@bullestock
Copy link

@lpgasparotto I managed to fix the remaining compile errors.

@lpgasparotto
Copy link
Contributor Author

lpgasparotto commented Jan 11, 2023 via email

@lpgasparotto
Copy link
Contributor Author

lpgasparotto commented Jan 11, 2023 via email

@lpgasparotto
Copy link
Contributor Author

lpgasparotto commented Jan 11, 2023 via email

@lpgasparotto
Copy link
Contributor Author

lpgasparotto commented Jan 12, 2023 via email

@bullestock
Copy link

bullestock commented Jan 13, 2023

It's very possible that my compile fixes have broken something.

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

2 participants