From: Waylan L. <wa...@gm...> - 2009-03-13 19:52:53
|
So I finally got around to testing the exe installable for 2.0-rc1 today. It worked fine, but the command line script does not work properly. It seems that on Windows, when a command line script tries to import a lib of the same name it fails. Apparently, it tries to import itself instead and returns an import error. AFAICT, this is *not* a problem in Linux systems. Looking at a few other libs I have installed on my system, it appears that they get around this by spelling the command line script differently - usually with capitalization. In most cases the lib is CamelCased and the script is all lower case. Obviously, to retain backwards compatibility that's not an option for us. Anyone have any suggestions or know of any solutions? -- ---- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg |