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:
> https://bitbucket.org/cffi/cffi/commits/8f867f5a869f
>
> (although cffi itself is not, the extensions it generates
I've created a GitHub issue for this feature request:
"pip install/upgrade --save"
https://github.com/pypa/pip/issues/3884
On Sun, Jul 31, 2016 at 2:29 PM, Wes Turner wrote:
> On Jul 31, 2016 12:25 PM, "Jeremy Stanley" wrote:
> >
> > On 2016-07-30
On Jul 31, 2016 12:25 PM, "Jeremy Stanley" wrote:
>
> On 2016-07-30 20:23:14 -0500 (-0500), Wes Turner wrote:
> > pbr also supports "environment markers"
> > which we would want to preserve when round-tripping (reading in,
modifying,
> > and writing out) requirements.txt files;
The next version of cffi will contain small changes to generate code
compliant with Python's Py_LIMITED_API:
https://bitbucket.org/cffi/cffi/commits/8f867f5a869f
(although cffi itself is not, the extensions it generates will be).
If we also add an appropriate supported tag to pip ~=
On 2016-07-30 20:23:14 -0500 (-0500), Wes Turner wrote:
> pbr also supports "environment markers"
> which we would want to preserve when round-tripping (reading in, modifying,
> and writing out) requirements.txt files;
> though IDK if environment markers are part of any Python Packaging Spec?
>
>