RE: [Jython-dev] A proposal for jythonc -J / --compileropts

[Humbel O. <Otm...@bi...>]

>   [Finn Bock]
> > [Humbel Otmar]

=20
> >Please find below a possible solution to a small jythonc problem.
> >I hope it is not platform specific.=20
>=20
> I think it is. I can't test it, but quoting args should work correctly
> on unix. It is the braindead command interpreter on windows that is at
> fault here.
>=20
> >I am not sure if this should become a bug report.
>=20
> It should, please add one. Even if it is just a windows problem, it is
> still a problem.
Done (# 453301).

> >With the following change in jython/Tools/main.py (around line 150):
> >	elif opt in ('-J', '--compileropts'):
> >		options.jopts =3D3D arg.split(',')  # was arg.split()
before
>=20
> While I'm always in favor of a quick hack <wink>, this is isn't the
> right one. It would break working scripts for unix users and I have
> never seen other tools use this convention for passing options down to
> subcommands.
Fully agree. Thanks very much for pointing this out.

> I'm leaning more towards a fix where we can pass in the name of a
> (property?) file that contains further options and arguments.=20
> It isn't a
> good solution but it would be the same bad solution that windows have
> always used.
> That could also function as the workaround to the max 9 args=20
> restriction
> that we also suffer on windows.
Until then, I'll stick to the quick hack, but very locally
on our make server. To be able to - dynamically - target different
output directories just makes it a lot easier to run several different
builds every night.