visualpython-users

[Visualpython-users] distutils

[Bruce S. <bas...@un...>]

Prompted by Arthur Siegel's suggestions, Jonathan Brandmeyer and I have been
doing some experimenting with distutils as a mechanism for building VPython
installers. The situation is not as simple as one would like. Dynamically
supporting all of our platforms and different compilers with a single script
will be difficult at best. We'll keep at this.

Bruce Sherwood

Re: [Visualpython-users] distutils

[Arthur <ajs...@op...>]

I am running into some isues as well.

I am not sure it even solves the most substantial issues, but thinking about
it, is there any reason the Windows and non-Windows setup.py's cannot be
separate scripts?

Would also be interested in what you are running into.  Are the issues
intra-Linux, Linux/Mac?

Since I have only one Linux and no Mac to test, I suspect issues, but cannot
actually see them.

Art

Art
----- Original Message -----
From: "Bruce Sherwood" <bas...@un...>
To: "vpusers" <vis...@li...>
Sent: Tuesday, February 25, 2003 8:51 AM
Subject: [Visualpython-users] distutils


> Prompted by Arthur Siegel's suggestions, Jonathan Brandmeyer and I have
been
> doing some experimenting with distutils as a mechanism for building
VPython
> installers. The situation is not as simple as one would like. Dynamically
> supporting all of our platforms and different compilers with a single
script
> will be difficult at best. We'll keep at this.
>
> Bruce Sherwood
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users

Re: [Visualpython-users] distutils

[Bruce S. <bas...@un...>]

There's quite a large number of detailed issues. To give a simple example, a
machine (my Mac OSX 10.2 is an example) may not have gtk-config to be driven
to identify the gtk library environment. And gtk-config only applies to GTK
1, not GTK 2. Etc. As Jonathan Brandmeyer has pointed out to me, distutils
doesn't address a large number of the configuration/environment issues that
are handled by the autoconfig machinery used for example in the compilation
of Python itself from source. Sometime last year I complimented Guido on the
fact that the source compilation of Python worked flawlessly on many
different Unix-like platforms, and he said that there had been a huge amount
of work on the autoconfig aspects over a couple of years to reach this point
of universality.

So while distutils may have some uses with respect to VPython (including as
Arthur has shown a nice way to produce an executable installer on Windows),
it does seem alas that eventually we'll have to bite the bullet of learning
to use autoconfig to address the many nagging problems that people have
experienced on diverse Linux/Unix platforms.

The problems will be eased by Jonathan's intention to try to simplify the
Visual environment using newer schemes such as Boost, which Arthur made us
aware of.

Bruce Sherwood

----- Original Message -----
From: "Arthur" <ajs...@op...>
To: "Bruce Sherwood" <bas...@un...>; "vpusers"
<vis...@li...>
Sent: Tuesday, February 25, 2003 9:03 AM
Subject: Re: [Visualpython-users] distutils


> I am running into some isues as well.
>
> I am not sure it even solves the most substantial issues, but thinking
about
> it, is there any reason the Windows and non-Windows setup.py's cannot be
> separate scripts?
>
> Would also be interested in what you are running into.  Are the issues
> intra-Linux, Linux/Mac?
>
> Since I have only one Linux and no Mac to test, I suspect issues, but
cannot
> actually see them.
>
> Art
>
> Art
> ----- Original Message -----
> From: "Bruce Sherwood" <bas...@un...>
> To: "vpusers" <vis...@li...>
> Sent: Tuesday, February 25, 2003 8:51 AM
> Subject: [Visualpython-users] distutils
>
>
> > Prompted by Arthur Siegel's suggestions, Jonathan Brandmeyer and I have
> been
> > doing some experimenting with distutils as a mechanism for building
> VPython
> > installers. The situation is not as simple as one would like.
Dynamically
> > supporting all of our platforms and different compilers with a single
> script
> > will be difficult at best. We'll keep at this.
> >
> > Bruce Sherwood
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Visualpython-users mailing list
> > Vis...@li...
> > https://lists.sourceforge.net/lists/listinfo/visualpython-users
>
>
>

Re: [Visualpython-users] distutils

[Arthur <aj...@ix...>]

As  per Arnd's suggestion, we are probably not facing anything that others
haven't faced and othercome.  And its probably a good idea to see how others
are handling these issues.

On that score:

It might be worthwhile to download the pygame source distro -
http://pygame.org/ -  to see how a complex - I think more than VPython
faces - situation with a host of dependencies is handled.  There is a
generic config.py script that calls platform specific config scripts, which
then finally configures the workable setup.py.

More bads news:

On the start menu, icon issue for Windows - I see that while pygame
accomplishes it with a pure Python script, the script working is dependent
on having win32all installed.

Art
----- Original Message -----
From: "Bruce Sherwood" <bas...@un...>
To: "Arthur" <ajs...@op...>; "vpusers"
<vis...@li...>
Sent: Tuesday, February 25, 2003 11:57 AM
Subject: Re: [Visualpython-users] distutils


> There's quite a large number of detailed issues. To give a simple example,
a
> machine (my Mac OSX 10.2 is an example) may not have gtk-config to be
driven
> to identify the gtk library environment. And gtk-config only applies to
GTK
> 1, not GTK 2. Etc. As Jonathan Brandmeyer has pointed out to me, distutils
> doesn't address a large number of the configuration/environment issues
that
> are handled by the autoconfig machinery used for example in the
compilation
> of Python itself from source. Sometime last year I complimented Guido on
the
> fact that the source compilation of Python worked flawlessly on many
> different Unix-like platforms, and he said that there had been a huge
amount
> of work on the autoconfig aspects over a couple of years to reach this
point
> of universality.
>
> So while distutils may have some uses with respect to VPython (including
as
> Arthur has shown a nice way to produce an executable installer on
Windows),
> it does seem alas that eventually we'll have to bite the bullet of
learning
> to use autoconfig to address the many nagging problems that people have
> experienced on diverse Linux/Unix platforms.
>
> The problems will be eased by Jonathan's intention to try to simplify the
> Visual environment using newer schemes such as Boost, which Arthur made us
> aware of.
>
> Bruce Sherwood
>
> ----- Original Message -----
> From: "Arthur" <ajs...@op...>
> To: "Bruce Sherwood" <bas...@un...>; "vpusers"
> <vis...@li...>
> Sent: Tuesday, February 25, 2003 9:03 AM
> Subject: Re: [Visualpython-users] distutils
>
>
> > I am running into some isues as well.
> >
> > I am not sure it even solves the most substantial issues, but thinking
> about
> > it, is there any reason the Windows and non-Windows setup.py's cannot be
> > separate scripts?
> >
> > Would also be interested in what you are running into.  Are the issues
> > intra-Linux, Linux/Mac?
> >
> > Since I have only one Linux and no Mac to test, I suspect issues, but
> cannot
> > actually see them.
> >
> > Art
> >
> > Art
> > ----- Original Message -----
> > From: "Bruce Sherwood" <bas...@un...>
> > To: "vpusers" <vis...@li...>
> > Sent: Tuesday, February 25, 2003 8:51 AM
> > Subject: [Visualpython-users] distutils
> >
> >
> > > Prompted by Arthur Siegel's suggestions, Jonathan Brandmeyer and I
have
> > been
> > > doing some experimenting with distutils as a mechanism for building
> > VPython
> > > installers. The situation is not as simple as one would like.
> Dynamically
> > > supporting all of our platforms and different compilers with a single
> > script
> > > will be difficult at best. We'll keep at this.
> > >
> > > Bruce Sherwood
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Visualpython-users mailing list
> > > Vis...@li...
> > > https://lists.sourceforge.net/lists/listinfo/visualpython-users
> >
> >
> >
>

[Visualpython-users] "WinPyVisual" complete

[Arthur <ajs...@op...>]

As a step towards an "all_in_one" Windows distribution of PyGeo, I have a
draft of a working all_in_one version of VPython available.

As it currently exists, it is a zip file of < 1.2 meg that can be unzipped
anywhere in the directory tree. It includes a scaled down ScITE.  Fire up
ScITE, go to the "demos" sub-directory, open up any of the usual  VPython
demos - see proviso as to Tkinter below -  hit F5 and the demo will run.  No
other python, Numeric, or other files (other than normally present Windows
dlls) are assumed to be present on the machine.

If a distribution along these lines is to be developed, it would be simple
to do it using a simple Windows installer to add icons, start files,
licenses, etc.

Also, for demonstration purposes, I have available another zip file with a
bounce2.exe file and the minimal support files it needs to run.  Doubleclick
and the bounce2 demo runs. It was built using py2exe in conjunction with
distutils. Bounce2.exe is about 200k and includes all the Python files
(including a version of the interpreter itself) needed to run VPython files,
except for the following rquired dlls:

python22.dll
umath.pyd
multiarray.pyd
_numpy.pyd
_sre.pyd
cvisual.pyd

What I think is potentially interesting about this facility, as a one trick
in the toolchest, is the ability to demonstrate one's work to others without
asking them to do anything major in terms of an installation on their
machine.  Assuming they at least have access to a Windows machine, if they
are given the above listed dlls in a directory, any VPython constructions
then built as .exe will run as an executable from that directory.  I include
in the zip the simple required setup.py and a .bat file to run which -
assuming one downloads py2exe (there is a Windows installer for it) - will
create, with minimal editing,  an executable out of any VPython script.

With Bruce's permission (and some instructions on how to do so) , I will
make these files available.

Art

FWI, the PyGeo situation is a little more complicated in that it requires
TkInter.  But its quite doable, just adds a little more bulk to the
distribution.

Do any of the VPython demos rely on Tk?  If so, those will not run
successfully with the "distribution" in its present form.

[Visualpython-users] Re: "WinPyVisual" complete

[Bruce S. <bas...@un...>]

This sounds pretty interesting, Arthur. Thanks for the research! I myself am
recovering from being sick for several days, so it will be a while before I
can play with your ideas.

Bruce Sherwood

----- Original Message -----
From: "Arthur" <ajs...@op...>
To: "Bruce Sherwood" <bas...@un...>; "vpusers"
<vis...@li...>
Sent: Sunday, March 02, 2003 3:58 PM
Subject: "WinPyVisual" complete


> As a step towards an "all_in_one" Windows distribution of PyGeo, I have a
> draft of a working all_in_one version of VPython available.
>
> As it currently exists, it is a zip file of < 1.2 meg that can be unzipped
> anywhere in the directory tree. It includes a scaled down ScITE.  Fire up
> ScITE, go to the "demos" sub-directory, open up any of the usual  VPython
> demos - see proviso as to Tkinter below -  hit F5 and the demo will run.
No
> other python, Numeric, or other files (other than normally present Windows
> dlls) are assumed to be present on the machine.
>
> If a distribution along these lines is to be developed, it would be simple
> to do it using a simple Windows installer to add icons, start files,
> licenses, etc.
>
> Also, for demonstration purposes, I have available another zip file with a
> bounce2.exe file and the minimal support files it needs to run.
Doubleclick
> and the bounce2 demo runs. It was built using py2exe in conjunction with
> distutils. Bounce2.exe is about 200k and includes all the Python files
> (including a version of the interpreter itself) needed to run VPython
files,
> except for the following rquired dlls:
>
> python22.dll
> umath.pyd
> multiarray.pyd
> _numpy.pyd
> _sre.pyd
> cvisual.pyd
>
> What I think is potentially interesting about this facility, as a one
trick
> in the toolchest, is the ability to demonstrate one's work to others
without
> asking them to do anything major in terms of an installation on their
> machine.  Assuming they at least have access to a Windows machine, if they
> are given the above listed dlls in a directory, any VPython constructions
> then built as .exe will run as an executable from that directory.  I
include
> in the zip the simple required setup.py and a .bat file to run which -
> assuming one downloads py2exe (there is a Windows installer for it) - will
> create, with minimal editing,  an executable out of any VPython script.
>
> With Bruce's permission (and some instructions on how to do so) , I will
> make these files available.
>
> Art
>
> FWI, the PyGeo situation is a little more complicated in that it requires
> TkInter.  But its quite doable, just adds a little more bulk to the
> distribution.
>
> Do any of the VPython demos rely on Tk?  If so, those will not run
> successfully with the "distribution" in its present form.

[Visualpython-users] Re: "WinPyVisual" complete

[Bruce S. <bas...@un...>]

Oh, one other thing. Arthur, please don't wait for my "permission". Do make
your experiments available to all of us to try out. We'll all benefit from a
diversity of approaches being tried.

Bruce Sherwood

----- Original Message -----
From: "Arthur" <ajs...@op...>
To: "Bruce Sherwood" <bas...@un...>; "vpusers"
<vis...@li...>
Sent: Sunday, March 02, 2003 3:58 PM
Subject: "WinPyVisual" complete


> As a step towards an "all_in_one" Windows distribution of PyGeo, I have a
> draft of a working all_in_one version of VPython available.
>
> As it currently exists, it is a zip file of < 1.2 meg that can be unzipped
> anywhere in the directory tree. It includes a scaled down ScITE.  Fire up
> ScITE, go to the "demos" sub-directory, open up any of the usual  VPython
> demos - see proviso as to Tkinter below -  hit F5 and the demo will run.
No
> other python, Numeric, or other files (other than normally present Windows
> dlls) are assumed to be present on the machine.
>
> If a distribution along these lines is to be developed, it would be simple
> to do it using a simple Windows installer to add icons, start files,
> licenses, etc.
>
> Also, for demonstration purposes, I have available another zip file with a
> bounce2.exe file and the minimal support files it needs to run.
Doubleclick
> and the bounce2 demo runs. It was built using py2exe in conjunction with
> distutils. Bounce2.exe is about 200k and includes all the Python files
> (including a version of the interpreter itself) needed to run VPython
files,
> except for the following rquired dlls:
>
> python22.dll
> umath.pyd
> multiarray.pyd
> _numpy.pyd
> _sre.pyd
> cvisual.pyd
>
> What I think is potentially interesting about this facility, as a one
trick
> in the toolchest, is the ability to demonstrate one's work to others
without
> asking them to do anything major in terms of an installation on their
> machine.  Assuming they at least have access to a Windows machine, if they
> are given the above listed dlls in a directory, any VPython constructions
> then built as .exe will run as an executable from that directory.  I
include
> in the zip the simple required setup.py and a .bat file to run which -
> assuming one downloads py2exe (there is a Windows installer for it) - will
> create, with minimal editing,  an executable out of any VPython script.
>
> With Bruce's permission (and some instructions on how to do so) , I will
> make these files available.
>
> Art
>
> FWI, the PyGeo situation is a little more complicated in that it requires
> TkInter.  But its quite doable, just adds a little more bulk to the
> distribution.
>
> Do any of the VPython demos rely on Tk?  If so, those will not run
> successfully with the "distribution" in its present form.
>
>
>
>
>