Discussion:
[Fab-user] windows install -- 'fab' is not recognized ...
Willem Hoek
2009-10-23 05:22:47 UTC
Permalink
Just re-loaded Win XP and installed my dev tools -- including Fabric.
When trying to run 'fab' from the MS-DOS command prompt, I get
'fab' is not recognized as an internal or external command.

from python I can see Fabric, because' import fabric' is working OK (?)

I believe it might be related to sys path but even after google searching /
tweaking of path, I am still unable to solve.
Any pointers will be usefull.

Many Thanks
Will
Jeff Forcier
2009-10-23 14:28:08 UTC
Permalink
Hi Willem,
Post by Willem Hoek
When trying to run 'fab' from the MS-DOS command prompt, I get
'fab' is not recognized as an internal or external command.
from python I can see Fabric, because' import fabric' is working OK (?)
I believe it might be related to sys path but even after google searching /
tweaking of path, I am still unable to solve.
I'm afraid I don't use Python on Windows myself so I can't be of too
much help there. I *assume* that, like on Unix platforms, the setup.py
install process drops a copy of the "fab" script onto some globally
shared binary path -- but I have no idea where that would be.

There are other Fabric users on Windows, too, so hopefully one of them
will see this thread and be able to at least tell you what path their
own "fab" appears to be sitting on, which should give us a clue.

I'd do some Googling of my own but I'm kind of pressed for time at the
moment :( I'm hoping to push out Fab 0.9 final this weekend and part
of that process may be trying to set up Python on a Windows VM to test
installation -- if I get to that point I'll let you know what I find.

Best,
Jeff
Akira Li
2009-10-23 17:26:41 UTC
Permalink
Post by Jeff Forcier
Post by Willem Hoek
When trying to run 'fab' from the MS-DOS command prompt, I get
'fab' is not recognized as an internal or external command.
from python I can see Fabric, because' import fabric' is working OK (?)
I believe it might be related to sys path but even after google searching /
tweaking of path, I am still unable to solve.
I'm afraid I don't use Python on Windows myself so I can't be of too
much help there. I *assume* that, like on Unix platforms, the setup.py
install process drops a copy of the "fab" script onto some globally
shared binary path -- but I have no idea where that would be.
Hi,

This might help:

1. Add Python's "Scripts" directory to %PATH% environment variable (look
for \PythonXY\Scripts directory).

2. Find out what extension has the fab script (it is most probably .py
or .bat) and add this extension to %PATHEXT%. It will allow you to call
fab without specifying the extension.

I don't use python on Windows either so there might be some other issues.


--
Akira.
James Pearson
2009-10-27 22:34:21 UTC
Permalink
Post by Willem Hoek
Just re-loaded Win XP and installed my dev tools -- including Fabric.
When trying to run 'fab' from the MS-DOS command prompt, I get
'fab' is not recognized as an internal or external command.
from python I can see Fabric, because' import fabric' is working OK (?)
I believe it might be related to sys path but even after google searching /
tweaking of path, I am still unable to solve.
Any pointers will be usefull.
The default path for the executables created by setup.py to go in is
C:\Python25\Scripts , for Python 2.5 on Windows. You should be able to
navigate into there and see (and run) the script, and if that works, add it
to your PATH.
--
James Pearson
--
The best way to predict the future is to invent it.
- Alan Kay
Willem Hoek
2009-10-28 09:12:23 UTC
Permalink
Many thanks
That did solve the problem


Sent from my iPhone
Post by Willem Hoek
Just re-loaded Win XP and installed my dev tools -- including Fabric.
When trying to run 'fab' from the MS-DOS command prompt, I get
'fab' is not recognized as an internal or external command.
from python I can see Fabric, because' import fabric' is working OK (?)
I believe it might be related to sys path but even after google
searching / tweaking of path, I am still unable to solve.
Any pointers will be usefull.
The default path for the executables created by setup.py to go in is
C:\Python25\Scripts , for Python 2.5 on Windows. You should be able
to navigate into there and see (and run) the script, and if that
works, add it to your PATH.
--
James Pearson
--
The best way to predict the future is to invent it.
- Alan Kay
Continue reading on narkive:
Loading...