Reputation: 3459
There are some posts on SO and tell me to use fab-script.py as startup script for pycharm. It's exactly what I used before. Now when I upgrade fabric to latest version, fab-script disappeared, and only fab.exe left there. I tried a lot of other ways, but still failed to launch debugger in pycharm.
Upvotes: 2
Views: 1577
Reputation: 3459
The final solution is to add line below at fabfile.py:
import fabric.main
if __name__ == '__main__':
fabric.main.main()
then you can debug the fabfile.py as a normal python script in pycharm.
For Fabric 2 users this should work (tested on Fabric 2.6.0
):
import fabric.main
if __name__ == '__main__':
fabric.main.program.run()
Upvotes: 2
Reputation: 6549
How to run/debug Fabric (Fab) command in Pycharm
which fab
from your virtualenv and take the output pathrun/debug configuration
with type = python
scriptconfigure it
output
from p.1Example
Upvotes: 2
Reputation: 2269
I haven't used this setup on Windows, but on Linux/Mac, it's fairly straightforward:
fab.exe
, like C:\Python27\.....\fab.exe
or whatever it is.-l
, to list the available commands. You'll tweak this later, and fill it in with whatever tasks you'd run from the command line, like "fab etc..."And it's about as easy as that, at least on *nix. Sorry that I don't have a Windows setup, but do let us know if you do have any issues with the setup described above.
Upvotes: 1