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
Norman Gray wrote:
Did you force the reinstall? It appears so, since it reached the
10.6 appscript install.
How do you do that? My own problem here [1] is that I can't work
out how to make appscript play with python 2.6 (or 10.6).
If the problem is that easy_install is installing appscr
On Sep 11, 2009, at 11:48 AM, Norman Gray wrote:
Did you force the reinstall? It appears so, since it reached the
10.6 appscript install.
How do you do that? My own problem here [1] is that I can't work out
how to make appscript play with python 2.6 (or 10.6).
I thought I had used the -U o
Greetings
On 2009 Sep 11, at 15:02, Brad Howes wrote:
Did you force the reinstall? It appears so, since it reached the
10.6 appscript install.
How do you do that? My own problem here [1] is that I can't work out
how to make appscript play with python 2.6 (or 10.6).
Sorry. No idea what
On Sep 11, 2009, at 12:03 AM, Noel Rappin wrote:
I did reinstall. I'm still having the same problem with Appscript
0.20, Snow Leopard's Python 2.6.1
The issue happens in a different place each time, but the error
looks like this:
File "build/bdist.macosx-10.6-universal/egg/appscript/refere
I did reinstall. I'm still having the same problem with Appscript
0.20, Snow Leopard's Python 2.6.1
The issue happens in a different place each time, but the error looks like this:
File "build/bdist.macosx-10.6-universal/egg/appscript/reference.py",
line 504, in __call__
appscript.reference.Com
On Sep 9, 2009, at 1:53 AM, has wrote:
Noel Rappin wrote:
I have a Python script that I've been using to communicate back and
forth with iTunes via py-appscript -- it's worked fine for a long
time.
Snow Leopard seems to have broken it -- everytime I run the script,
it
stops, and then exits
Noel Rappin wrote:
I have a Python script that I've been using to communicate back and
forth with iTunes via py-appscript -- it's worked fine for a long
time.
Snow Leopard seems to have broken it -- everytime I run the script, it
stops, and then exits, claiming that one of the commands has time
I have a Python script that I've been using to communicate back and
forth with iTunes via py-appscript -- it's worked fine for a long
time.
Snow Leopard seems to have broken it -- everytime I run the script, it
stops, and then exits, claiming that one of the commands has timed
out. It's never the
21 matches
Mail list logo