On Thursday, October 19, 2017, Donald Stufft <don...@stufft.io> wrote:
>
> On Oct 19, 2017, at 5:26 PM, Tres Seaver <tsea...@palladion.com
> <javascript:_e(%7B%7D,'cvml','tsea...@palladion.com');>> wrote:
>
> Having the packaging
> system register those services at installation time (even if it doesn't
> care otherwise about them) seems pretty reasonable to me.
>
>
> It does register them at installation time, using an entirely generic
> feature of “you can add any file you want to a dist-info directory and we
> will preserve it”. It doesn’t need to know anything else about them other
> then it’s a file that needs preserved.
>
When I think of 'register at installation time', I think of adding them to
a single { locked JSON || SQLite DB || ...}; because that's the only way
there'd be a performance advantage?
Why would we write a .txt, transform it to {JSON || SQL INSERTS}, and then
write it to a central registrar?
(BTW, pipsi does console script entry points with isolated virtualenvs
linked into from ~/.local/bin (which is generally user-writable)).
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
