It'd be more accurate to say that it doesn't support automatic generation
of wheels - how would it know what to generate?
The wheels must be created by a build system. The devpi client has support
for building and uploading wheels, and devpi is designed to support having
locally-built wheels supplement existing packages. I'd be happy to
elaborate.
Richard
On 10 July 2014 10:43, Donald Stufft <don...@stufft.io> wrote:
>
> On Jul 9, 2014, at 7:07 PM, Richard Jones <r1chardj0...@gmail.com> wrote:
>
> On 10 July 2014 02:19, Ben Nemec <openst...@nemebean.com> wrote:
>
>> On 07/08/2014 11:05 PM, Joe Gordon wrote:
>> > On Tue, Jul 8, 2014 at 8:54 PM, James Polley <j...@jamezpolley.com>
>> wrote:
>> >
>> >> It may not have been clear from the below email, but clarkb clarifies
>> on
>> >> https://bugs.launchpad.net/openstack-ci/+bug/1294381 that the infra
>> team
>> >> is no longer maintaining pypi-mirror
>> >>
>> >> This has been a very useful tool for tripleo. It's much simpler for new
>> >> developers to set up and use than a full bandersnatch mirror (and
>> requires
>> >> less disk space), and it can create a local cache of wheels which saves
>> >> build time.
>> >>
>> >> But it's now unsupported.
>> >>
>> >> To me it seems like we have two options:
>> >>
>> >> A) Deprecate usage of pypi-mirror; update docs to instruct new devs in
>> >> setting up a local bandersnatch mirror instead
>> >> or
>> >> B) Take on care-and-feeding of the tool.
>> >> or, I guess,
>> >> C) Continue to recommend people use an unsupported unmaintained
>> >> known-buggy tool (it works reasonably well for us today, but it's
>> going to
>> >> work less and less well as time goes by)
>> >>
>> >> Are there other options I haven't thought of?
>> >>
>> >
>> > I don't know if this fits your requirements but I use
>> > http://doc.devpi.net/latest/quickstart-pypimirror.html for my
>> development
>> > needs.
>>
>> Will that also cache wheels? In my experience, wheels are one of the
>> big time savers in tripleo so I would consider it an important feature
>> to maintain, however we decide to proceed.
>>
>
> Yes, devpi caches wheels.
>
> I would suggest that if the pip cache approach isn't appropriate then
> devpi probably a good solution (though I don't know your full requirements).
>
> The big difference between using devpi and pip caching would be that devpi
> will allow you to install packages when you're offline.
>
>
> Richard
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> It doesn’t generate Wheels though, it’ll only cache them if they exist on
> PyPI already.
>
> -----------------
> Donald Stufft
> PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372
> DCFA
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
