visualpython-users

[Visualpython-users] Make Mac Installer More Flexible?

[Seth M. <sm...@ps...>]

Hello, 

I am trying to install VPython through Mac installer, and it is telling me that I need to install the 32 bit Python from Python.org.  The problem is, I already have a 32-bit Python installed (using homebrew), but it's not installed where the Python.org binary installer would install to.  As a result,  VPython is not detecting it.  I have also noticed this issue on systems using the Enthought Python Distribution (which has separate 64 and 32 bit Pythons as well), and I would imagine that Python from MacPorts and Fink would have the same issue, but I've never tried these.

Would it be possible to add a button to the installer that says "I know what I'm doing" to bypass the need for the Python.org installation?  Or,  better yet, if VPython does not detect the 32-bit Python from Python.org, ask the user to give the path of their 32-bit installation to verify that VPython will work.

Thanks!

Seth Morton

Re: [Visualpython-users] Make Mac Installer More Flexible?

[Kevin K. <ka...@so...>]

Seth Morton wrote:
 > I am trying to install VPython through Mac installer, and it is
 > telling me that I need to install the 32 bit Python from
 > Python.org.  The problem is, I already have a 32-bit Python
 > installed (using homebrew), but it's not installed where the
 > Python.org binary installer would install to.  As a result, VPython
 > is not detecting it.  I have also noticed this issue on systems
 > using the Enthought Python Distribution (which has separate 64 and
 > 32 bit Pythons as well), and I would imagine that Python from
 > MacPorts and Fink would have the same issue, but I've never tried
 > these.
 > 
 > Would it be possible to add a button to the installer that says "I
 > know what I'm doing" to bypass the need for the Python.org
 > installation?  Or, better yet, if VPython does not detect the
 > 32-bit Python from Python.org, ask the user to give the path of
 > their 32-bit installation to verify that VPython will work.

I found it sufficient to run vpython programs with

	arch -i386 python foo.py
or 	arch -32bit python foo.py

(depending which version of OS X I had).  It seems that the recent
Python installations do both 32bit and 64bit installations, so can be
specified on the command line.

Of course, long term, Vpython will have to move away from the
32-bit-only implementation on Macs, or it will become unusable.

Re: [Visualpython-users] Make Mac Installer More Flexible?

[Bruce S. <Bru...@nc...>]

It's not simply a question of recognizing that some Python or other is
available. The core of VPython is written in C++ and is compiled
against a particular Python, with particular entry points.

In principle it ought to be possible to create a distutils or similar
type of installer for Linux and Mac that you would run by executing
your particular Python, and it would invoke as necessary the C++
compiler. I hope someone will create such a mechanism. I myself am
unlikely to be able to try this in the near future.

This is not a viable option on Windows because most users don't have a
C++ compiler on their Windows machine. However, it could be a useful
way to build binary installers to distribute to Windows users.

Bruce Sherwood

Re: [Visualpython-users] Make Mac Installer More Flexible?

[Bruce S. <Bru...@nc...>]

Another option would be for someone to take responsibility for
creating the VPython installer for the Mac Python of their choice.
Only someone who uses that particular non-python.org version is in a
position to create and test such an installer. As I've explained, it
wouldn't help for the existing installer to recognize a non-python.org
Python being available, because it and VPython won't match.

I'm trying to enunciate a general principle. I'm able to make VPython
installers that match the "official" Pythons distributed at
python.org. VPython installers for any other flavor of Python must
necessarily be the responsibility of users of those other flavors,
unless and until someone creates a distutil-like VPython installer
that is executed by the Python of your choice.

I would of course be happy to host other-flavor VPython installers at
vpython.org.

Bruce Sherwood

On Fri, Jun 8, 2012 at 11:55 AM, Bruce Sherwood <Bru...@nc...> wrote:
> It's not simply a question of recognizing that some Python or other is
> available. The core of VPython is written in C++ and is compiled
> against a particular Python, with particular entry points.
>
> In principle it ought to be possible to create a distutils or similar
> type of installer for Linux and Mac that you would run by executing
> your particular Python, and it would invoke as necessary the C++
> compiler. I hope someone will create such a mechanism. I myself am
> unlikely to be able to try this in the near future.
>
> This is not a viable option on Windows because most users don't have a
> C++ compiler on their Windows machine. However, it could be a useful
> way to build binary installers to distribute to Windows users.
>
> Bruce Sherwood