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

No way to generate optimized bytecode? #207

Closed
alxpettit opened this issue Nov 18, 2018 · 2 comments
Closed

No way to generate optimized bytecode? #207

alxpettit opened this issue Nov 18, 2018 · 2 comments

Comments

@alxpettit
Copy link
Contributor

@alxpettit alxpettit commented Nov 18, 2018

I'm now a co-maintainer of the syncplay AUR package. Ideally, we'd have the installation have .pyc files generated and packaged so that they're tracked by pacman -- but currently we do not. I'd like to know what the equivalent is of --optimize=1 for your install toolchain, since you're not using setup.py.

@Et0h
Copy link
Contributor

@Et0h Et0h commented Nov 25, 2018

I do not have any experience with setup.py, so you will probably need to find someone with relevant toolchain experience to make an appropriate PR or comment on how to do it without setup.py.

@albertosottile
Copy link
Member

@albertosottile albertosottile commented Feb 1, 2019

In the last few days, I investigated the possibility of using setuptools with Syncplay (hence writing a setup.py script). Unfortunately, our current project structure does not match the one typically used for python modules or packages, and these differences really stood out in my attempts to adapt setuptools to Syncplay, creating a lot of issues.

At this moment, we would like to keep our current folder structure, so we decided to abandon the idea of using also setuptools for distributing Syncplay. @alxpettit, going back to your question, a way to generate optimized bytecode for all the python files in Syncplay could be to run
python -m compileall . while being in the repository main folder. Please let us know if this command can be included in the workflow used to pack AUR packages. In the meantime, I am closing this issue.

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

Successfully merging a pull request may close this issue.

None yet
3 participants