On 19 October 2017 at 12:16, Daniel Holth wrote:
> We said "you won't have to install setuptools" but actually "you don't
> have to use it" is good enough. If you had 2 pkg-resources implementations
> running you might wind up scanning sys.path extra times...
>
True, but that's where Thomas's sug
We said "you won't have to install setuptools" but actually "you don't have
to use it" is good enough. If you had 2 pkg-resources implementations
running you might wind up scanning sys.path extra times...
On Wed, Oct 18, 2017, 20:53 Nick Coghlan wrote:
> On 19 October 2017 at 04:18, Alex Grönhol
On 19 October 2017 at 04:18, Alex Grönholm wrote:
> Daniel Holth kirjoitti 18.10.2017 klo 21:06:
>
> http://setuptools.readthedocs.io/en/latest/formats.html?
> highlight=entry_points.txt#entry-points-txt-entry-point-plugin-metadata
>
> http://setuptools.readthedocs.io/en/latest/pkg_resources.
> h
On Wed, Oct 18, 2017 at 2:57 PM Paul Moore wrote:
> On 18 October 2017 at 19:42, Thomas Kluyver wrote:
> > On Wed, Oct 18, 2017, at 05:59 PM, Paul Moore wrote:
> >> > I've always used the setuptools documentation as a reference. Are you
> >> > suggesting moving that information to a different lo
On Wed, Oct 18, 2017 at 2:18 PM Alex Grönholm
wrote:
> Daniel Holth kirjoitti 18.10.2017 klo 21:06:
>
>
> http://setuptools.readthedocs.io/en/latest/formats.html?highlight=entry_points.txt#entry-points-txt-entry-point-plugin-metadata
>
>
> http://setuptools.readthedocs.io/en/latest/pkg_resources.
On 18 October 2017 at 19:42, Thomas Kluyver wrote:
> On Wed, Oct 18, 2017, at 05:59 PM, Paul Moore wrote:
>> > I've always used the setuptools documentation as a reference. Are you
>> > suggesting moving that information to a different location to
>> > allow/encourage other tools to implement it a
On Wed, Oct 18, 2017, at 05:59 PM, Paul Moore wrote:
> > I've always used the setuptools documentation as a reference. Are you
> > suggesting moving that information to a different location to
> > allow/encourage other tools to implement it as a standard?
>
> I've never used entry points myself (o
Daniel Holth kirjoitti 18.10.2017 klo 21:06:
http://setuptools.readthedocs.io/en/latest/formats.html?highlight=entry_points.txt#entry-points-txt-entry-point-plugin-metadata
http://setuptools.readthedocs.io/en/latest/pkg_resources.html?highlight=pkg_resources#creating-and-parsing
It is not ver
http://setuptools.readthedocs.io/en/latest/formats.html?highlight=entry_points.txt#entry-points-txt-entry-point-plugin-metadata
http://setuptools.readthedocs.io/en/latest/pkg_resources.html?highlight=pkg_resources#creating-and-parsing
It is not very complicated. It looks like the characters are m
On 18 October 2017 at 17:48, Doug Hellmann wrote:
> Excerpts from Thomas Kluyver's message of 2017-10-18 15:52:00 +0100:
>> We're increasingly using entry points in Jupyter to help integrate
>> third-party components. This brings up a couple of things that I'd like
>> to do:
>>
>> 1. Specification
Excerpts from Thomas Kluyver's message of 2017-10-18 15:52:00 +0100:
> We're increasingly using entry points in Jupyter to help integrate
> third-party components. This brings up a couple of things that I'd like
> to do:
>
> 1. Specification
>
> As far as I know, there's no document describing th
We're increasingly using entry points in Jupyter to help integrate
third-party components. This brings up a couple of things that I'd like
to do:
1. Specification
As far as I know, there's no document describing the details of entry
points; it's a de-facto standard established by setuptools. It s
12 matches
Mail list logo
