On 7 September 2015 at 14:11, Marcus Smith wrote:
>
>
>> > That way, the URL works as people expect, *and* the resulting
>> > destination gives a URL that (when inevitably copy-and-pasted) will
>> > retain its meaning over time.
>>
>> Yes, ReadTheDocs does let us do that.
>
>
> well, it lets you d
> That way, the URL works as people expect, *and* the resulting
> > destination gives a URL that (when inevitably copy-and-pasted) will
> > retain its meaning over time.
>
> Yes, ReadTheDocs does let us do that.
well, it lets you do it for a whole project.
we'd have to have a project per spec for
On 7 September 2015 at 09:42, Ben Finney wrote:
> Nick Coghlan writes:
>
>> On 7 September 2015 at 02:09, Marcus Smith wrote:
>> > For example, down the road when there's Wheel 2.0, what's the "Current
>> > Specs" for wheel?
>>
>> Yes, but I think that's easy enough to handle by having a default
Nick Coghlan writes:
> On 7 September 2015 at 02:09, Marcus Smith wrote:
> > For example, down the road when there's Wheel 2.0, what's the "Current
> > Specs" for wheel?
>
> Yes, but I think that's easy enough to handle by having a default URL
> that always goes to the latest version of the spec
On 7 September 2015 at 01:43, Marcus Smith wrote:
> ok, so this is PEP 474
> where's the activity for the forge idea happening? python-dev list?
While the final discussions will need to move to python-dev, the
preliminary discussions are taking place on the core-workflow mailing
list: https
On 7 September 2015 at 02:09, Marcus Smith wrote:
> One thought that comes to mind is how to present specs that deal with
> formats and artifacts that persist for years.
>
> For example, down the road when there's Wheel 2.0, what's the "Current
> Specs" for wheel?
>
> I would describe 2.0 is the "
On 7 September 2015 at 01:37, Marcus Smith wrote:
>>
>> then bundles the system
>> version back up with rewheel for installation into Python virtual
>> environments.
>
>
> this "bundles the system version back up" step happens when?
When ensurepip.bootstrap() runs - Fedora's system Python is patc
One thought that comes to mind is how to present specs that deal with
formats and artifacts that persist for years.
For example, down the road when there's Wheel 2.0, what's the "Current
Specs" for wheel?
I would describe 2.0 is the "Latest" spec, but "Current Specs" includes all
versions we're a
ok, so this is PEP 474
where's the activity for the forge idea happening? python-dev list?
On Sat, Sep 5, 2015 at 10:47 PM, Nick Coghlan wrote:
>
> On 6 Sep 2015 10:39, "Marcus Smith" wrote:
> >
> > yea, I like the idea of our own authoritative Pypa project for
> proposals, and maybe have
>
>
> then bundles the system
> version back up with rewheel for installation into Python virtual
> environments.
this "bundles the system version back up" step happens when?
which fedora version did this start?
___
Distutils-SIG maillist - Distutils-
10 matches
Mail list logo
