Message11362
| Author |
zyasoft |
| Recipients |
darjus, stefan.richthofer, zyasoft |
| Date |
2017年05月07日.16:34:31 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1494174872.67.0.48541491414.issue2570@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Agreed that using something like LiJy would make this problem go away, because we would have a real executable as a launcher, much as we see with the Windows launcher. Better yet, it would be direct. But there are both build (need to do this for every platform, although creative use of CPython could help) and licensing problems as pointed out.
If we could "seamlessly" monkeypatch setuptools CommandSpec as necessary, that would give us control for this thorny issue, without having to maintain a Jython-specific patch of setuptools (thereby limiting upgrades of pypa upstream work like pip), while preserving the ability to revise the installer for a specific version of Jython. Maybe we could manage through some suitable cleverness in site.py? Again, this only works because CommandSpec is relatively stable... And it is monkeypatching! |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2017年05月07日 16:34:32 | zyasoft | set | messageid: <1494174872.67.0.48541491414.issue2570@psf.upfronthosting.co.za> |
| 2017年05月07日 16:34:32 | zyasoft | set | recipients:
+ zyasoft, darjus, stefan.richthofer |
| 2017年05月07日 16:34:32 | zyasoft | link | issue2570 messages |
| 2017年05月07日 16:34:32 | zyasoft | create |
|