Great. Just making sure. Updating the chapter now.
On Mon, Aug 1, 2016 at 3:41 PM, Donald Stufft wrote:
> Yea, instead of testpypi.python.org you’d use test.pypi.org. Specifically
> for uploading you’d use something like:
>
>
> [testpypiorg]
>
Yea, instead of testpypi.python.org you’d use test.pypi.org. Specifically for
uploading you’d use something like:
[testpypiorg]
repository:https://test.pypi.org/legacy/
username:
password:
For downloading it’d be something like test.pypi.org/simple/
> On Aug 1, 2016, at 6:39 PM, Anna
To be specific, update .pypirc like this:
[testpypi]
repository=https://test.pypi.org/
On Mon, Aug 1, 2016 at 3:39 PM, Anna Ravenscroft
wrote:
> So for testing, we direct testpypi (in the pypirc) to test.pypi.org,
> right?
>
> On Mon, Aug 1, 2016 at 3:26 PM, Donald Stufft
So for testing, we direct testpypi (in the pypirc) to test.pypi.org, right?
On Mon, Aug 1, 2016 at 3:26 PM, Donald Stufft wrote:
> Just an FYI, test.pypi.org is now active (this is the Warehouse instance
> backed by Test PyPI). Once https://github.com/pypa/warehouse/pull/1416
Just an FYI, test.pypi.org is now active (this is the Warehouse instance backed
by Test PyPI). Once https://github.com/pypa/warehouse/pull/1416 is deployed and
merged test.pypi.io will start to redirect to test.pypi.org.
No changes to pypi.io have occurred yet, we’re still waiting on the EV
Yep, file:
https://github.com/pypa/setuptools/issues/709
Chris
On 01/08/2016 22:40, Chris Jerdonek wrote:
The issue tracker on PyPA's GitHub repo for the proejct seems alive and well:
https://github.com/pypa/setuptools/issues
--Chris
On Mon, Aug 1, 2016 at 2:34 PM, Chris Withers
The issue tracker on PyPA's GitHub repo for the proejct seems alive and well:
https://github.com/pypa/setuptools/issues
--Chris
On Mon, Aug 1, 2016 at 2:34 PM, Chris Withers wrote:
> Hi Guys,
>
> Where's the best place to report setuptools issues now?
>
> I see 25.1.2 was
Hi Guys,
Where's the best place to report setuptools issues now?
I see 25.1.2 was release today, and I've just had nightly builds
of one of my packages fail as follows:
Installing docs.
Getting distribution for 'sphinx'.
Traceback (most recent call
On Mon, Aug 1, 2016 at 12:01 PM Steve Dower wrote:
> On 01Aug2016 0702, Nick Coghlan wrote:
> > On 1 August 2016 at 23:36, Daniel Holth wrote:
> >> build_ext command determines
> >> the DLL extension. It could be patched or modified to read an "I'm
On 01Aug2016 0702, Nick Coghlan wrote:
On 1 August 2016 at 23:36, Daniel Holth wrote:
build_ext command determines
the DLL extension. It could be patched or modified to read an "I'm ABI3"
flag on the Extension() object.
We could pass an ABI3 flag to bdist_wheel in the same
On 1 August 2016 at 23:36, Daniel Holth wrote:
> On Mon, Aug 1, 2016 at 1:42 AM Nick Coghlan wrote:
>> Status quo, on publication side:
>>
>> - require minimum cffi version 1.8
>> - build with setuptools
>> - postprocessing step to rename shared library/DLL
On Mon, Aug 1, 2016 at 1:42 AM Nick Coghlan wrote:
> On 1 August 2016 at 05:27, Daniel Holth wrote:
> > The next version of cffi will contain small changes to generate code
> > compliant with Python's Py_LIMITED_API:
> >
12 matches
Mail list logo