For some possibly useful documentation feedback: I got confused.
Normally I would install a tool, check out its `--help` content, then maybe try it out. I think based on my attempts to do this and read the docs, is that this is not currently possible for PyApp. Instead you must have a Python app you'd like to setup for compilation before you can install PyApp at all (at least when using the cargo installation method). Is that right? And then when installing the tool it will also go ahead and compile the currently configured Python package?
Sorry about that! What you said is basically correct: this is for distributing Python applications. You configure via environment variables at build-time and the binary you ship to users who then run it. It could be a single name/version pair or more complex options like embedding a wheel or being defined by a requirements file.
Comments
Thanks, I look forward to this!
For some possibly useful documentation feedback: I got confused.
Normally I would install a tool, check out its `--help` content, then maybe try it out. I think based on my attempts to do this and read the docs, is that this is not currently possible for PyApp. Instead you must have a Python app you'd like to setup for compilation before you can install PyApp at all (at least when using the cargo installation method). Is that right? And then when installing the tool it will also go ahead and compile the currently configured Python package?
Sorry about that! What you said is basically correct: this is for distributing Python applications. You configure via environment variables at build-time and the binary you ship to users who then run it. It could be a single name/version pair or more complex options like embedding a wheel or being defined by a requirements file.