Ronald Oussoren wrote:
> > Yes, that's part of the problem. The other part is that .pth handling
> > seems to have changed from 2.5 to 2.6.
>
> That's news to me. I've been using zipped eggs with 2.6 without any
> problems.
Don't know that it had anything to do with eggs. What I was seeing wa
Ronald Oussoren wrote:
>
> On 17 Sep, 2009, at 23:50, Bill Janssen wrote:
>
> > Ronald Oussoren wrote:
> >
> >> Bill,
> >>
> >> Appscript probably gets installed as a zipped egg, the .python-eggs
> >> directory gets created when a real filesystem path is needed for an
> >> item in such an egg.
On 17 Sep, 2009, at 23:50, Bill Janssen wrote:
Ronald Oussoren wrote:
Bill,
Appscript probably gets installed as a zipped egg, the .python-eggs
directory gets created when a real filesystem path is needed for an
item in such an egg.
Yes, that's part of the problem. The other part is that
On 17 Sep, 2009, at 23:50, Bill Janssen wrote:
Ronald Oussoren wrote:
Bill,
Appscript probably gets installed as a zipped egg, the .python-eggs
directory gets created when a real filesystem path is needed for an
item in such an egg.
Yes, that's part of the problem. The other part is that
In article <20090917234722.gb26...@panix.com>,
Aahz wrote:
> On Thu, Sep 17, 2009, Bill Janssen wrote:
> > Ronald Oussoren wrote:
> >> If you install appscript as an unzipped egg the problem should go away.
> > How does one do that?>
> You can unzip manually as with any other .ZIP file, or you
On Thu, Sep 17, 2009, Bill Janssen wrote:
> Ronald Oussoren wrote:
>>
>> If you install appscript as an unzipped egg the problem should go away.
>
> How does one do that?
You can unzip manually as with any other .ZIP file, or you can do
easy_install with -Z.
--
Aahz (a...@pythoncraft.com)
Ronald Oussoren wrote:
> Bill,
>
> Appscript probably gets installed as a zipped egg, the .python-eggs
> directory gets created when a real filesystem path is needed for an
> item in such an egg.
Yes, that's part of the problem. The other part is that .pth handling
seems to have changed from 2
On 14 Sep 2009, at 16:28, Bill Janssen wrote:
has wrote:
You can install appscript from source using plain old distutils; the
setup.py script will use setuptools if it's available and distutils
if
not. Though if there are problems with setuptools then I'd suggest
filing bug reports on tha
has wrote:
> On 13 Sep 2009, at 18:52, Bill Janssen wrote:
>
> > Is it possible to disentangle appscript from setuptools? I just
> > downloaded the sources to my Snow Leopard machine, did
> >
> > python setup.py build
> > python setup.py install
> >
> > which went just fine. But then I did
> >
On Sun, Sep 13, 2009, Ronald Oussoren wrote:
>
> Appscript probably gets installed as a zipped egg, the .python-eggs
> directory gets created when a real filesystem path is needed for an item
> in such an egg.
>
> If you install appscript as an unzipped egg the problem should go away.
My auto-i
On 13 Sep 2009, at 18:52, Bill Janssen wrote:
Is it possible to disentangle appscript from setuptools? I just
downloaded the sources to my Snow Leopard machine, did
python setup.py build
python setup.py install
which went just fine. But then I did
% python
import appscript
and got this
Bill,
Appscript probably gets installed as a zipped egg, the .python-eggs
directory gets created when a real filesystem path is needed for an
item in such an egg.
If you install appscript as an unzipped egg the problem should go away.
Ronald
On 13 sep 2009, at 19:52, Bill Janssen wrote
Is it possible to disentangle appscript from setuptools? I just
downloaded the sources to my Snow Leopard machine, did
python setup.py build
python setup.py install
which went just fine. But then I did
% python
>>> import appscript
and got this big stack trace because a ~/.python-eggs subdire
13 matches
Mail list logo
