-
Notifications
You must be signed in to change notification settings - Fork 1
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
Python 3 #8
Comments
Ok, I just attempted to naively convert cheesecake to python 3, first using 2to3. Cheesecake in ast_pp.py, model.py, codeparser.py has a dependency on the compiler module. That module re-implemented the cpython compiler in python and it was completely removed from python 3. Furthermore, the code references the private module _subprocess, which appears to also be gone in python3. This looks like it can just be replaced with modern popen patterns. setuptools has changed... and now my attention is wandering. We might be better off just re-writing the 2000 lines of cheesecake_index.py by hand to support py3 |
Agreed with rewriting. Although I have a feeling not a lot of people are even using this package. Are you using it on a regular basis @matthewdeanmartin ? |
@griggheo I was, out of frustration with the large number of trash packages on pypi, writing a "package quality checker" of my own, cheese_grader. Along the way I stumbled on this library. I'm the build master where I work, so I check code we write within an inch of its life. But as soon as I import a 3rd party library, other than the "safety" check, it is like I'm assuming other people's code is perfect. All the code I support is py3 only, so I won't be able to use cheeseshop even though I'd want to. |
Got it. It looks like your cheese grader package is the way to go then. |
Currently, cheesecake is not Python 3 ready:
The text was updated successfully, but these errors were encountered: