hi, think so, here is what I get if I try to install the versions already
there with their egg-info files:
$ pip install argparse==1.2.1
Requirement already satisfied (use --upgrade to upgrade): argparse==1.2.1
in /usr/lib/python2.7
Cleaning up...
$ pip install wsgiref==0.1.2
Requirement already s
and also:
$ pip install wsgiref
Requirement already satisfied (use --upgrade to upgrade): wsgiref in
/usr/lib/python2.7
Cleaning up...
On Fri, Mar 8, 2013 at 10:45 PM, Samuele Pedroni
wrote:
> hi, think so, here is what I get if I try to install the versions already
> there with their egg-info
Hi Samuele,
On Tue, Mar 5, 2013 at 9:05 PM, Samuele Pedroni
wrote:
> part of what cpython does (did?) in this sort of cases is to ship a
> *.egg-info for the package that has an external existence as well, like in
> CPython2.7 you can see there are .egg-info files for wsgiref and argparse in
> th
part of what cpython does (did?) in this sort of cases is to ship a
*.egg-info for the package that has an external existence as well, like in
CPython2.7 you can see there are .egg-info files for wsgiref and argparse
in the stdlib dir.
On Fri, Mar 1, 2013 at 11:54 AM, Armin Rigo wrote:
> Hi all
On Fri, 01 Mar 2013 17:44:27 +0100, Armin Rigo wrote:
Le 01 Mar 2013 17:44:27 +0100, Armin Rigo a écrit:
> Hi Gabriel,
>
> On Fri, Mar 1, 2013 at 4:22 PM, Gabriel de Perthuis
> wrote:
>> Packages using CFFI should be able to install-require CFFI whatever the
>> interpreter is, including requirin
Hi Gabriel,
On Fri, Mar 1, 2013 at 4:22 PM, Gabriel de Perthuis wrote:
> Packages using CFFI should be able to install-require CFFI whatever the
> interpreter is, including requiring newer versions than the one the
> interpreter
> ships.
The problem is that the pure Python CFFI is rather tied t
> Hi all, hi Jeremy,
>
> I'm thinking about merging the curses_cffi branch, and I see efforts
> going on in sqlite-cffi. Great :-)
>
> We need to think about how we want to support cffi-based modules in
> PyPy. So far the idea is to include the official release of CFFI
> together with regular P
Hi Armin (2013.03.01_12:54:09_+0200)
> We need to think about how we want to support cffi-based modules in
> PyPy. So far the idea is to include the official release of CFFI
> together with regular PyPy installations.
The related question is: How do we ship CFFI modules in PyPy? Import all
the cf
Hi!
Maybe a possible way is that you have "major" releases of cffi without
backward incompatible changes that correspond to PyPy releases - so
that any cffi 1.x works on PyPy 2.0, and any cffi 2.x works on PyPy
2.1, etc. And than you can complain if there is major version mismatch
of cffi.
So there
Hi all, hi Jeremy,
I'm thinking about merging the curses_cffi branch, and I see efforts
going on in sqlite-cffi. Great :-)
We need to think about how we want to support cffi-based modules in
PyPy. So far the idea is to include the official release of CFFI
together with regular PyPy installation
10 matches
Mail list logo
