On Mon, Oct 1, 2018 at 8:46 PM Nick Coghlan wrote:
> On Wed., 26 Sep. 2018, 2:40 pm Chris Jerdonek,
> wrote:
>
>> My advice to you (and which I've been following myself) would be for
>> you to break changes into small, tightly-focused PR's, and to have
>> only one outstanding at a time (or perha
On Wed., 26 Sep. 2018, 2:40 pm Chris Jerdonek,
wrote:
> My advice to you (and which I've been following myself) would be for
> you to break changes into small, tightly-focused PR's, and to have
> only one outstanding at a time (or perhaps two if non-overlapping).
> The main reason is that there a
Hi,
On Mon, Oct 1, 2018 at 3:51 PM Robin Becker wrote:
>
> Thanks Dustin & Matthew,
>
> Appveyor pinning was relatively easy. I tried to pin in multibuild using the
> approach of pillow, but now I am getting
>
> > macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10
Thanks Dustin & Matthew,
Appveyor pinning was relatively easy. I tried to pin in multibuild using the
approach of pillow, but now I am getting
macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
Traceback (most recent call last):
File "multibuild
Here is the relevant issue: https://github.com/pypa/auditwheel/issues/102
On Mon, Oct 1, 2018 at 7:54 AM Robin Becker wrote:
> I am using Matthew Brett's manylinux builder setup (
> https://github.com/matthew-brett/multibuild) for reportlab and just
> started to
> see this
>
> > File
> "/opt/_in
Sorry for causing you additional frustration. I was also frustrated and
underscoring a sense that seems to come through in most of our interactions for
a number of reasons. It isn’t my intention to cause you additional grief, so I
apologize for fanning the flames.
Dan Ryan // pipenv maintainer
I am using Matthew Brett's manylinux builder setup (https://github.com/matthew-brett/multibuild) for reportlab and just started to
see this
File
"/opt/_internal/cpython-3.6.6/lib/python3.6/site-packages/auditwheel/wheeltools.py",
line 14, in
from wheel.util import urlsafe_b64encode, open
Hi,
I'm sorry, but I'm not going to respond to this message. For some time
now I've been considering taking a break from open source mailing
lists, as I'm finding that the frustration involved in dealing with
some of the more confrontational threads (until now, mostly on other
lists than this one)
