Hash bang syntax not portable about fuct

[MrOnion]

Forgot to answer this but the env has been used already and I think it's the distutils that strips it out from the final package when doing the build. This might need some tweaking to get it right if it's actually causing trouble.

[fredcooke]

Doh. Should have known that you'd be doing it properly and it was a gotcha. Yes, I think it does/did cause issues. Haven't tried it on Ubunut Bionic, but might do shortly just because. I have my "fuct-dev" package installed so it should just work, aside from possibly this.

[fredcooke]

BUILD FAILED - Missing plugin dependency 'pypandoc~=1.3.0': Installing collected packages: pypandoc

sudo pip install --upgrade pypandoc

pycollada 0.4 has requirement python-dateutil==1.5, but you'll have python-dateutil 2.6.1 which is incompatible.

[INFO] Installing plugin dependency pypandoc
[ERROR] Failed to install 'pypandoc':
Uninstalling pypandoc-1.4:

fred@karma:~/fuct/target/dist/fuct-0.9.1$ fuctloader
bash: /usr/local/bin/fuctloader: python: bad interpreter: No such file or directory

Yeah, still an issue.

[MrOnion]

Ok, i'll look into this. The build script might also need some work to finish the python3 changes.

[fredcooke]

Yeah, and I'll need to fork my fuct-dev into fuct-py27-dev and fuct-py3-dev :-) Any thoughts on those errors/issues? Seems to work without it, minus the script. Does readme need updating to add that package maybe at a specific version? Not sure, super tired right now.

…

On 24 June 2018 at 00:00, Ari Karhu ***@***.***> wrote: Ok, i'll look into this. The build script might also need some work to finish the python3 changes. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACQd9lu3nkOhzAoa_tmhqzUIwiBMrxdks5t_i3bgaJpZM4LdV3r> .

[MrOnion]

The pybuilder distutils plugin creates the broken shebang scripts and when you run 'python setup.py install' they are copied as-is. Although it's not mandatory to have them ready as the setup.py can produce them as well. For example if you clean the current build dir before installing by running 'python setup.py clean install', then the correct (your env) interpreter path is used. That could be added to the readme...

One way to generate working script files from the start could be to force the pybuilder distutils plugin to use overridden interpreter path that is the env one. Not clean, but you will end up with scripts with either the env path or the current system path which should both work.

[MrOnion]

There is a workaround now in dev branch. Feel free to test it out.