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

Create a ppb console command. #178

Open
pathunstrom opened this issue Nov 16, 2018 · 6 comments
Open

Create a ppb console command. #178

pathunstrom opened this issue Nov 16, 2018 · 6 comments
Labels
discussion Issues that more just discussing than specific flaws or features wishlist

Comments

@pathunstrom
Copy link
Collaborator

I imagine a console script with helpful ppb commands. Clearly on the list is the shell being worked on in #177. Also want to add a ppb run sub command that can take a module or package with certain rules and do the engine instantiation for you.

@AstraLuma AstraLuma added the discussion Issues that more just discussing than specific flaws or features label Jul 20, 2019
@AstraLuma
Copy link
Member

This has to do with #177 and some of the ideas of moving in a LOVE-like direction.

@AstraLuma
Copy link
Member

Ok, some thoughts from discord:

  • ppb run looks for __main__.py in the current directory and runs that
  • ppb run spam does python -m spam
  • ppb shell opens a repl
  • ppb fix-assets adds __init__.py in places it thinks it's needed

There was some discussion around how magical ppb run should be (like, it executes the target file, pulls out its global namespace, and looks for starting_scene or setup), but you'd then also need an engine config. Having worked with framework configs plenty in the web space, you often just need python-as-config and at that point you might as well have the user call ppb.run() themselves.

@AstraLuma
Copy link
Member

Maybe ppb get-font to help users finding and pulling fonts from google fonts?

@pathunstrom
Copy link
Collaborator Author

The simplest way to add some of these things will be via console_scripts. Which would mean the code needs to live with ppb proper.

I dunno if bundling that closely is the best plan.

@AstraLuma
Copy link
Member

I'm not against sticking it in ppb proper, based on dependencies vs value. (eg, font integration without requests would be... Fun.)

It would also be pretty easy to do a ppb-cli package that does the same thing.

@AstraLuma
Copy link
Member

  • ppb versions--some kind of output of library versions, including SDL

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 wishlist
Projects
None yet
Development

No branches or pull requests

2 participants