On Tue, Mar 27, 2018 at 10:08 PM, Sandro Tosi <mo...@debian.org> wrote:
> Hello Piotr,
>
> On Sun, 5 Jun 2016 20:47:46 +0200 Piotr =?utf-8?Q?O=C5=BCarowski?=
> <pi...@debian.org> wrote:
>> FTR: I didn't apply this patch because exceptions are allowed only in
>> private dirs intentionally - I don't want to deal with all the
>> exceptions while f.e. upgrading Python 3 to new 3.X version.
>> It makes perfect sense in 2.X, but we should not package new stuff for
>> 2.X anyway...
>>
>> I do not close this bug or mark it as wontfix, because even for 3.X we
>> will most probably have to figure something out sooner or later (but I
>> still hope that it will be fixed upstream, in the interpreter)
>
> now i have a valid reason for this feature: it was requested to
> install the test files for pylint. pylint has, on purpose, invalid
> files among these tests, but forcing pycompile/py3compile on them of
> course it will fail, making the package uninstallable as-is;
>
> i'll try shipping customized postinst scripts, but that sucks. is
> there any other solution than having this bug fixed?
and now this:
Usage: pycompile [-V [X.Y][-][A.B]] DIR_OR_FILE [-X REGEXPR]
pycompile -p PACKAGE
pycompile: error: --exclude option works with private directories
only, please use /usr/share/python/bcep to specify public modules to
skip
it would be really helpful if all these options and restrictions were
documented somewhere, f.e. pycompile manpage and/or --help. like what
is bcep? (what does it that name mean?) is it a file (as it looks from
that message)? reading pycompile code appears as if it's a directory
where files are read from; what's their format?
Regards,
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
