visualpython-users

[Visualpython-users] Building 32-bit/64-bit vpython on MacOS?

[Daniel F. <boy...@gm...>]

Dear list,

I have recently discovered the Homebrew project, which is a fantastic
community driven package manager for MacOS,
http://github.com/mxcl/homebrew . Using this and pip
(http://pypi.python.org/pypi/pip) I have build a really stable python
environment, both 32-bit and 64-bit on MacOS including numpy, scipy
etc.. I would now like to add vpython to the stack. Currently, I'm
using the pre-compiled 32-bit version from the installer and it works
really well with my python environment. However, this fails when
imported from the 64-bit python. So my questions:

* How easy would it be to provide a 'brew' for vpython specific to MacOS?

* Could a more general installer for vpython be added to the pip
package manager?

* Is there a fundamentally reason for sticking to 32-bit (e.g.
dependency difficulties?)

Best,

Dan

Re: [Visualpython-users] Building 32-bit/64-bit vpython on MacOS?

[Martin C. <cos...@wa...>]

On 24/01/11 11:17 , Daniel Farrell wrote:
[]
> * Is there a fundamentally reason for sticking to 32-bit (e.g.
> dependency difficulties?)

I can't answer your other questions, but this one I can: There is no 
such reason. Fink (an older "community driven package manager for 
MacOS") has vpython version 5.40 (package visual-py27) that builds OK in 
the 64bit tree.

-- 
Martin

Re: [Visualpython-users] Building 32-bit/64-bit vpython on MacOS?

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

Martin, that's very good news, but puzzling. I thought that there was
no support for Carbon within Mac 64-bit programs? The demise of Carbon
has had me very worried, as no one seems to know how to make VPython
work within a Cocoa environment.

Bruce Sherwood

On Mon, Jan 24, 2011 at 5:11 AM, Martin Costabel <cos...@wa...> wrote:
> On 24/01/11 11:17 , Daniel Farrell wrote:
> []
>> * Is there a fundamentally reason for sticking to 32-bit (e.g.
>> dependency difficulties?)
>
> I can't answer your other questions, but this one I can: There is no
> such reason. Fink (an older "community driven package manager for
> MacOS") has vpython version 5.40 (package visual-py27) that builds OK in
> the 64bit tree.
>
> --
> Martin
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
>

Re: [Visualpython-users] Building 32-bit/64-bit vpython on MacOS?

[Martin C. <cos...@wa...>]

Bruce,

you are right; I keep forgetting that Fink's vpython uses X11 graphics. 
For aqua graphics, the non-existence of some parts of Carbon for 64bit 
is indeed a serious obstacle.

Martin

On 24/01/11 17:21 , Bruce Sherwood wrote:
> Martin, that's very good news, but puzzling. I thought that there was
> no support for Carbon within Mac 64-bit programs? The demise of Carbon
> has had me very worried, as no one seems to know how to make VPython
> work within a Cocoa environment.
>
> Bruce Sherwood
>
> On Mon, Jan 24, 2011 at 5:11 AM, Martin Costabel<cos...@wa...>  wrote:
>> On 24/01/11 11:17 , Daniel Farrell wrote:
>> []
>>> * Is there a fundamentally reason for sticking to 32-bit (e.g.
>>> dependency difficulties?)
>>
>> I can't answer your other questions, but this one I can: There is no
>> such reason. Fink (an older "community driven package manager for
>> MacOS") has vpython version 5.40 (package visual-py27) that builds OK in
>> the 64bit tree.
>>

Re: [Visualpython-users] Building 32-bit/64-bit vpython on MacOS?

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

Ah. Of course. I made the corresponding mistake of forgetting that in
the Fink environment the demise of Carbon isn't a problem. In fact,
Fink may in the future again be the basis for VPython if no one
figures out how to make a Cocoa-based VPython. The problem with that
is that many Mac users very much want the standard Mac look and feel,
as was made clear when the only Mac version was based on X11.

Bruce Sherwood

On Mon, Jan 24, 2011 at 3:41 PM, Martin Costabel <cos...@wa...> wrote:
> Bruce,
>
> you are right; I keep forgetting that Fink's vpython uses X11 graphics. For
> aqua graphics, the non-existence of some parts of Carbon for 64bit is indeed
> a serious obstacle.
>
> Martin
>
> On 24/01/11 17:21 , Bruce Sherwood wrote:
>>
>> Martin, that's very good news, but puzzling. I thought that there was
>> no support for Carbon within Mac 64-bit programs? The demise of Carbon
>> has had me very worried, as no one seems to know how to make VPython
>> work within a Cocoa environment.
>>
>> Bruce Sherwood
>>
>> On Mon, Jan 24, 2011 at 5:11 AM, Martin Costabel<cos...@wa...>
>>  wrote:
>>>
>>> On 24/01/11 11:17 , Daniel Farrell wrote:
>>> []
>>>>
>>>> * Is there a fundamentally reason for sticking to 32-bit (e.g.
>>>> dependency difficulties?)
>>>
>>> I can't answer your other questions, but this one I can: There is no
>>> such reason. Fink (an older "community driven package manager for
>>> MacOS") has vpython version 5.40 (package visual-py27) that builds OK in
>>> the 64bit tree.
>>>
>