I did have issues, however:
- **Command line wrapper?**
Though I'm no *nix ninja, I knew enough to follow INSTALL, which gave me a working jsl.py. I naively tried copying this to my ~/bin directory and quickly found that a no-go. I then tried various invocations of setup.py install with -prefix, -home, -user, etc. I tried **-dry-run** with these and found it to be pretty wet (**defect: lib directories got created anyway**).
I'm only a programmer: Your modern lib/python/2.6/site-packages and .egg-info files frighten and confuse me… But I **do** know the Windows executable hid all that from me and gave me a nice, reassuring "0 errors" ouput when I behaved myself, and surely a project implemented in nice, portable Python and C couldn't have only a Win32 API dependent command line executable?
For now I ended up writing a jsl bash script to invoke my svn workspace's jsl.py with my edited .conf file, but would love the same wrapper I got spoiled with on Windows…
- **New (secret) Warnings**
Actually I'll make a separate post for this…
Yes, I've just been working out the trunk, so I got lazy with proper packaging/installation.
However, try it now. Update from Subversion and reinstall. (You don't need to run the makefile anymore. Just use setup.py.)
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.