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

Splitting The World: Python packaging and supporting multiple backends #663

Open
pathunstrom opened this issue Feb 3, 2022 · 0 comments
Labels
discussion Issues that more just discussing than specific flaws or features The Future Tickets revolving around the future direction of ppb.

Comments

@pathunstrom
Copy link
Collaborator

Constraints:

pip install ppb needs to produce the default desktop implementation as it exists now.

When installing for a web context, we don't want SDL included, so need some method to get "core" "features" and "ppb-web-backend" (We can shave the naming yak later).

We should start having a conversation on what this looks like and how to handle it overall.

Current options are deep magics to create a web distributable or ppb package explosion with explicit dependencies. (Or the worst of both worlds: package explosion with deep magics!)

@pathunstrom pathunstrom added discussion Issues that more just discussing than specific flaws or features The Future Tickets revolving around the future direction of ppb. labels Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Issues that more just discussing than specific flaws or features The Future Tickets revolving around the future direction of ppb.
Projects
None yet
Development

No branches or pull requests

1 participant