I’ve just released pip 1.5.2 and virtualenv 1.11.2
1.5.2 (2014-01-26)
--
* Upgraded the vendored ``pkg_resources`` and ``_markerlib`` to setuptools 2.1.
* Fixed an error that prevented accessing PyPI when pyopenssl, ndg-httpsclient,
and pyasn1 are installed
* Fixed an issue
On Jan 25, 2014, at 11:15 PM, Kyle Kelley wrote:
> Where are the states stored?
https://github.com/python/pypi-salt
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMa
I'll get in touch with Martin.
On 26 January 2014 11:40, Nick Coghlan wrote:
>
> On 26 Jan 2014 09:51, "Richard Jones" wrote:
> >
> > Thanks everyone who helped make this happen.
>
> Indeed - fine work! :)
>
> > From my perspective* I believe the ssh upload mechanism was added to
> address sec
On 26 Jan 2014 09:51, "Richard Jones" wrote:
>
> Thanks everyone who helped make this happen.
Indeed - fine work! :)
> From my perspective* I believe the ssh upload mechanism was added to
address security issues around the basic-auth-over-http method used
historically. Now uploads *may* be done
Paul's position exactly mirrors my own - I an perfectly fine with the
recommended advice to scientific users continuing to be "NumPy doesn't
officially support pip and virtualenv because of the way it is built and
installed, so you will have to get one of the curated scientific stacks,
bootstrap co
On Jan 25, 2014, at 7:04 PM, Chris Jerdonek wrote:
> On Sat, Jan 25, 2014 at 3:38 PM, Donald Stufft wrote:
>> Today (Sat Jan 25, 2014) the Infrastructure team has migrated PyPI to new
>> infrastructure.
>>
>> The old infrastructure was:
>>
>> - a single database server managed by OSUOSL
>> -
On Sat, Jan 25, 2014 at 3:38 PM, Donald Stufft wrote:
> Today (Sat Jan 25, 2014) the Infrastructure team has migrated PyPI to new
> infrastructure.
>
> The old infrastructure was:
>
> - a single database server managed by OSUOSL
> - a pair of load balancers shared by all of the python.org services
On 25 January 2014 23:36, Vinay Sajip wrote:
>> Those people currently either use the wininst installers (which I'm
>> *not* advocating that we remove) or they use virtualenvs, and have the
>> view that they have to at a minimum jump through some hoops to get
>> numpy to work.
>
> I don't know if
Thanks everyone who helped make this happen.
>From my perspective* I believe the ssh upload mechanism was added to
address security issues around the basic-auth-over-http method used
historically. Now uploads *may* be done over https, and those using the ssh
method can move over to using twine or
On Sat, 25/1/14, Paul Moore wrote:
> Wheels are an improvement over the wininst status quo because they
> support virtualenvs. So I want to see numpy wheels available, because
> that would be a significant step in making people aware of some of the
>
Today (Sat Jan 25, 2014) the Infrastructure team has migrated PyPI to new
infrastructure.
The old infrastructure was:
- a single database server managed by OSUOSL
- a pair of load balancers shared by all of the python.org services hosted on
OSUOSL
- a single backend VM that served as everything
On 25 January 2014 21:56, Oscar Benjamin wrote:
> I'll try to summarise your take on this: You would like to take the
> time to ensure that Python packaging is done properly. That may mean
> that some functionality isn't available for some time, but you think
> that it's better to "get it right" t
On 24 January 2014 10:18, Nick Coghlan wrote:
>
> On 24 Jan 2014 19:41, "Paul Moore" wrote:
>>
>> On 24 January 2014 00:17, Oscar Benjamin
>> wrote:
>> > You need to bear in mind that people currently have a variety of ways
>> > to install numpy on Windows that do work already without limitation
On 25 January 2014 21:33, Oscar Benjamin wrote:
> Last time I tried with mingw it worked (I've since departed the
> Windows world). I think official numpy binaries for Windows are built
> with mingw (Christoph uses MSVC though).
That may well be the case, but MSVC (Express or full) is the
"standa
On 24 January 2014 22:40, Paul Moore wrote:
> On 24 January 2014 22:21, Chris Barker wrote:
>> well, numpy _should_ build out of the box with nothing special if you are
>> set up to build regular extensions. I understand that a lto f Windows users
>> are not set up to build extensions at all, but
15 matches
Mail list logo
