On 09/28/2017 09:40 AM, Paul Moore wrote:
> Are you aware of pipsi? If you do `pipsi install somepackage` it
> creates a new virtualenv in ~/.local/.venvs, populates it with
> somepackage and its dependencies, and then puts the entry point
> scripts for somepackage into ~/.local/bin. It may be a
Are you aware of pipsi? If you do `pipsi install somepackage` it
creates a new virtualenv in ~/.local/.venvs, populates it with
somepackage and its dependencies, and then puts the entry point
scripts for somepackage into ~/.local/bin. It may be a useful way of
delivering your program, rather than
On 09/27/2017 09:50 AM, Paul Moore wrote:
>>> What you could do is pip install your binary dependencies into a
>>> directory in $TEMP using --target, then add that directory to
>>> sys.path. Probably easier than building a full virtualenv. Bundle pip
>>> with your app if you can't assume your
On 26 September 2017 at 23:48, Irmen de Jong wrote:
> On 09/26/2017 10:49 PM, Paul Moore wrote:
>> On 26 September 2017 at 19:47, Irmen de Jong wrote:
>>> Any thoughts on this? Is it a good idea or something horrible? Has
>>> someone attempted
On 09/26/2017 10:49 PM, Paul Moore wrote:
> On 26 September 2017 at 19:47, Irmen de Jong wrote:
>> Any thoughts on this? Is it a good idea or something horrible? Has
>> someone attempted something like this before perhaps?
>
> When I've done this, I've bundled my
On 26 September 2017 at 19:47, Irmen de Jong wrote:
> Any thoughts on this? Is it a good idea or something horrible? Has
> someone attempted something like this before perhaps?
When I've done this, I've bundled my dependencies in with my zipapp.
Of course that's trickier
On 09/26/2017 09:19 PM, Thomas Jollans wrote:
>> - use venv.EnvBuilder() to create a new virtualenv somewhere in the
>> user's home directory (~./virtualenvs/mygreatgame ?)
>
> The appropriate place for this kind of thing, on Linux, would be
> $XDG_DATA_HOME, default "~/.local/share/", i.e.:
>
>
On 26/09/17 20:47, Irmen de Jong wrote:
> Hi,
> I've been using Python's executable zip application feature to neatly
> package my little game into a single "executable" file.
> Here "executable" means the user can simply start it by doubleclicking
> it, or launching it from a shell prompt. Of
Hi,
I've been using Python's executable zip application feature to neatly
package my little game into a single "executable" file.
Here "executable" means the user can simply start it by doubleclicking
it, or launching it from a shell prompt. Of course the user already has
to have a proper Python