Michael Toomim wrote:
> I just installed the latest appscript from the installer. However,
> it puts the appscript python libs into
>
> /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/
> site-packages/aeosa
The appscript installer should install the following items into site-
On 11/13/06 8:37 PM, "Michael Toomim" <[EMAIL PROTECTED]> wrote:
> I just installed the latest appscript from the installer. However, it
> puts the appscript python libs into
>
> /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/
> aeosa
>
> instead of
>
> /Library/
On 11/14/06, Paul Berkowitz <[EMAIL PROTECTED]> wrote:
> On 11/13/06 8:37 PM, "Michael Toomim" <[EMAIL PROTECTED]> wrote:
>
> > I just installed the latest appscript from the installer. However, it
> > puts the appscript python libs into
> >
> > /Library/Frameworks/Python.framework/Versions/2.4/li
Russell E. Owen wrote:
> Sorry to follow up my own posting, but I found one way to do it:
>
> modify matplotlib's setup.py file to always install dateutil and pytz.
> It turns out normally only installs them if a version doesn't already
> exist.
I think it's a better idea to build mpkgs of date
Russell E Owen wrote:
>> I've never tried to create a binary egg
> (though I know how in principal). I'm wondering if there are any
> gotchas? I'm guessing I'll at least have to modify or create my own
> setup.py file in many cases -- depending on how many changes are
> required, that could be
At 11:20 AM -0800 2006-11-14, Christopher Barker wrote:
>Russell E. Owen wrote:
>>Sorry to follow up my own posting, but I found one way to do it:
>>
>>modify matplotlib's setup.py file to always install dateutil and
>>pytz. It turns out normally only installs them if a version doesn't
>>already
Paul Berkowitz wrote:
> On 11/13/06 8:37 PM, "Michael Toomim" <[EMAIL PROTECTED]> wrote:
>
>> I just installed the latest appscript from the installer. However, it
>> puts the appscript python libs into
>>
>> /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/
>> aeosa
has wrote:
> The appscript installer should install the following items into site-
> packages:
>
> aeosa/
> aeosa.pth
>
> The .pth file should contain the relative path to the aeosa directory
> (aeosa), and Python's import mechanism should follow that path when
> looking for modules to impor
Michael Toomim wrote:
> Hm, well I guess the .pth file didn't work on my machine for some reason.
After some more debugging, I think the problem might have been that my
python2.4 is installed from fink, which has its own site-packages
directory in /sw.
Thanks for the help!
