[Bob Ippolito wrote]
> Well, there is the license:
>
> "You may make and give away verbatim copies of this Package for
> personal use, or for use within your organization, provided that you
> duplicate all of the original copyright notices and associated
> disclaimers. You may not distribut
>> What do you think if Apple's (somewhat schizo, mind you) usage of
>> /Library/Python/X.Y/[site-packages/] ? This would solve that issue.
> and probably cause others.. I'd rather leave that location to Apple.
> If it turns out that it's really a good idea to put something there,
> then we can c
> >>One tool that would be nice is something that will migrate site-
> >>packages from one to the other when you're switching.
> >>
> >
> >What do you think if Apple's (somewhat schizo, mind you) usage of
> >/Library/Python/X.Y/[site-packages/]
> >? This would solve that issue.
>
> and probabl
On Jun 8, 2005, at 12:30 AM, Trent Mick wrote:
> [Bob Ippolito wrote]
>
>> One tool that would be nice is something that will migrate site-
>> packages from one to the other when you're switching.
>>
>
> What do you think if Apple's (somewhat schizo, mind you) usage of
> /Library/Python/X.Y/[s
[Bob Ippolito wrote]
> One tool that would be nice is something that will migrate site-
> packages from one to the other when you're switching.
What do you think if Apple's (somewhat schizo, mind you) usage of
/Library/Python/X.Y/[site-packages/]
? This would solve that issue.
Trent
--
Tre
On Jun 7, 2005, at 5:25 PM, Trent Mick wrote:
> [Larry Meyn wrote]
>
>> Sorry for the wording, a failed attempt at humor.
>>
>
> No worries. Just making sure that ActivePython wasn't doing anything
> stupid. My successful attempt at paranoia. :)
Well, there is the license:
"You may make and giv
On Jun 7, 2005, at 5:23 PM, Trent Mick wrote:
> [Bob Ippolito wrote]
>
>> It'd probably be better off just moving it to /Library/Frameworks/
>> Backup/Python.framework or something, for at least these reasons:
>>
>> If a developer is going to naively embed ActivePython in their
>> application, th
[Larry Meyn wrote]
> Sorry for the wording, a failed attempt at humor.
No worries. Just making sure that ActivePython wasn't doing anything
stupid. My successful attempt at paranoia. :)
Cheers,
Trent
--
Trent Mick
[EMAIL PROTECTED]
___
Pythonmac-SIG m
[Bob Ippolito wrote]
> It'd probably be better off just moving it to /Library/Frameworks/
> Backup/Python.framework or something, for at least these reasons:
>
> If a developer is going to naively embed ActivePython in their
> application, they'll probably just add a copy files phase to their
[andrea valle wrote]
> Let's suppose I install ActivePython.
> How do I install other modules? for example NumPy or PIL.
> Is there a particular mechanism doing the dirty job (a job in which I
> tipically don't succeed without package manager...)?
The standard way for 3rd-party modules to do this
On Jun 7, 2005, at 1:30 PM, Trent Mick wrote:
>> On Jun 7, 2005, at 8:29 AM, Larry Meyn wrote:
>>
>>> There's a new kid in town and he doesn't play nice with MacPython
>>> (but
>>> he does ask first before kicking MacPython aside:)
>>>
>>> Any thoughts on how this affects the Python development
Hi and thanks for the porting.
I'm sorry if I'm asking obvious things but I'm just a sort of
programmer.
Let's suppose I install ActivePython.
How do I install other modules? for example NumPy or PIL.
Is there a particular mechanism doing the dirty job (a job in which I
tipically don't succeed wi
Trent,
Sorry for the wording, a failed attempt at humor. I just glanced at
the announcement and noticed that your installer will move macpython
aside, but failed to notice that it adds some symlinks to still access
macpython and there is a mechanism to put it back. It's just that
having two
> On Jun 7, 2005, at 8:29 AM, Larry Meyn wrote:
> > There's a new kid in town and he doesn't play nice with MacPython (but
> > he does ask first before kicking MacPython aside:)
> >
> > Any thoughts on how this affects the Python development ecosystem for
> > OS X? (.. and right on the heels of the
On Jun 7, 2005, at 8:29 AM, Larry Meyn wrote:
> There's a new kid in town and he doesn't play nice with MacPython (but
> he does ask first before kicking MacPython aside:)
>
> Any thoughts on how this affects the Python development ecosystem for
> OS X? (.. and right on the heels of the Intel ann
There's a new kid in town and he doesn't play nice with MacPython (but
he does ask first before kicking MacPython aside:)
Any thoughts on how this affects the Python development ecosystem for
OS X? (.. and right on the heels of the Intel announcements.)
http://aspn.activestate.com/ASPN/docs/A
16 matches
Mail list logo
