On Jan 18, 2:19 pm, Rikishi 42 <[EMAIL PROTECTED]> wrote:
> On Thursday 18 January 2007 10:13, robert wrote:
>
> > stay with py23 for "a script" (and more) and make <700kB
> > independent distros - UPX and 7zip involved:
>
> >http://groups.google.com/group/comp.lang.python/msg/edf469a1b3dc3802Tha
On Thursday 18 January 2007 10:13, robert wrote:
> stay with py23 for "a script" (and more) and make <700kB
> independent distros - UPX and 7zip involved:
>
> http://groups.google.com/group/comp.lang.python/msg/edf469a1b3dc3802
Thanks, that might be an option. But I might just convince the person
Gabriel Genellina wrote:
> At Wednesday 17/1/2007 16:05, Rikishi 42 wrote:
>
>> >>What I want to do is to compile/bundle/prepare/whatever_term a simple
>> >>Python script for deployment on a Windows machine. Installing Python
>> >>itself on that machine, is not an option. Ideally I would like to
At Wednesday 17/1/2007 16:05, Rikishi 42 wrote:
>>What I want to do is to compile/bundle/prepare/whatever_term a simple
>>Python script for deployment on a Windows machine. Installing Python
>>itself on that machine, is not an option. Ideally I would like to obtain
>>a single executable file, bu
Hi,
I'm new to this group. I've tried finding my answer in existing messages,
but no such luck.
What I want to do is to compile/bundle/prepare/whatever_term a simple
Python script for deployment on a Windows machine. Installing Python
itself on that machine, is not an option. Ideally I would like
Rikishi 42 wrote:
> Hi,
> I'm new to this group. I've tried finding my answer in existing messages,
> but no such luck.
>
> What I want to do is to compile/bundle/prepare/whatever_term a simple
> Python script for deployment on a Windows machine. Installing Python
> itself on that machine, is not
On Wednesday 17 January 2007 00:48, Larry Bates wrote:
>> There is nothing graphical, nothing fancy about the script.
>> The only imports are: os, stat, string and time.
>>
>> Any suggestions on an - easy and clear - path to follow ?
> I use py2exe and inno installer. Works great.
Thanks, I wil
On Wednesday 17 January 2007 00:22, James Stroud wrote:
>> There is nothing graphical, nothing fancy about the script.
>> The only imports are: os, stat, string and time.
>>
>> Any suggestions on an - easy and clear - path to follow ?
>
>
> pyinstaller + innosetup.
I will look into it, thanks!
On Wednesday 17 January 2007 03:33, Gabriel Genellina wrote:
> At Tuesday 16/1/2007 19:49, Rikishi 42 wrote:
>
>>What I want to do is to compile/bundle/prepare/whatever_term a simple
>>Python script for deployment on a Windows machine. Installing Python
>>itself on that machine, is not an option.
At Tuesday 16/1/2007 19:49, Rikishi 42 wrote:
What I want to do is to compile/bundle/prepare/whatever_term a simple
Python script for deployment on a Windows machine. Installing Python
itself on that machine, is not an option. Ideally I would like to obtain
a single executable file, but a script
Rikishi 42 wrote:
> Hi,
> I'm new to this group. I've tried finding my answer in existing messages,
> but no such luck.
>
> What I want to do is to compile/bundle/prepare/whatever_term a simple
> Python script for deployment on a Windows machine. Installing Python
> itself on that machine, is not
Rikishi 42 wrote:
> Hi,
> I'm new to this group. I've tried finding my answer in existing messages,
> but no such luck.
>
> What I want to do is to compile/bundle/prepare/whatever_term a simple
> Python script for deployment on a Windows machine. Installing Python
> itself on that machine, is not
Hi,
I'm new to this group. I've tried finding my answer in existing messages,
but no such luck.
What I want to do is to compile/bundle/prepare/whatever_term a simple
Python script for deployment on a Windows machine. Installing Python
itself on that machine, is not an option. Ideally I would like
13 matches
Mail list logo