> > if sampledir is always trunk/jallib/sample, do not make this an environment > variable. >
This is not always the same, mostly because it can point to "unvalidated" or "validated". > Can't you figure out from the .svn files where you are in the trunk? > Yes I could. What if you want to specifically set the dir your want ? > I don't mind setting this variable once > I start to put some variables in my .bashrc. I usually do this. > , but it is always in the same position from the tools dir. There must be a > way in python to get the dir of the script itself. > I don't like hard-code things at this level. For instance, the python script itself is configurable, and I use Makefile to use it with correct args. > > Why include the template file if this is always the same? Why point to it > if you know where it is? > This is what I said: it's not necessarily the same. > > I'd prefer if stuff like wikify.py could be in the same directory as the > script. Then you can distribute it with svn. > As I previously said, I don't want to deal with 3rd party licenses. It'd need a dedicated 3rd_party directory with a README special notice, etc... I don't have time right now for this :) Maybe later... > > Searching the samplefiles for usage of the lib is nice, but in my case > generates quite a mess since I've tens of files in various stages of decay. > Checking these files against the repository is great. > > I'd like to run the script without any superfluous stuff, like: > > xxxx/external/lcd $ python ~/jalv2/jallib/tools/jalapi.py lcd_hd44780_4.py > > Oh, and could you *not* use the script basename (jalapi) for anything else? > This makes filename guessing with tab so much easier. > I don't name my files according to tab guessing convenience, I name them so they have sens (at least, I try) ! > Also, there is a "jallib" python script without the .py extension. Why? > Why not... Mainly because we don't have to know if this is a python script or not. It should be run withon invoking python, but this is WIP. Also note I work on building a standalone script, which would embed *all* dependencies, so no more problems like these. This is quite hard to get, though... Seb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
