Message10184
| Author |
stefan.richthofer |
| Recipients |
stefan.richthofer |
| Date |
2015年08月30日.15:01:03 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1440946864.51.0.793342732757.issue2386@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Okay, while this solution solves the project_base-problem, importing distutils.sysconfig fails in an other place:
distutils/command/build.py, line 118 also needs sys.executable.
So, solution 1) is needed I suppose. But how to init sys.executable?
1a) let it point to java(.exe)
1b) just pretend it was launched via jython, i.e. create project_base like described before, then set sys.executable=project_base+"/jython"
Any opinion? While 1b) is not accurate, I suppose it would work better, as this stuff is usually used to find the jython-directory rather than the java-directory. I guess the best idea would be to apply 1b), but only in build.py. Also, I would suggest to put a utility-function somewhere that creates and returns project_base as described above for every potential use-case. Suggestions, where this should go? Maybe into Py.java? Or into some lib-python code? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年08月30日 15:01:04 | stefan.richthofer | set | messageid: <1440946864.51.0.793342732757.issue2386@psf.upfronthosting.co.za> |
| 2015年08月30日 15:01:04 | stefan.richthofer | set | recipients:
+ stefan.richthofer |
| 2015年08月30日 15:01:04 | stefan.richthofer | link | issue2386 messages |
| 2015年08月30日 15:01:03 | stefan.richthofer | create |
|