Thanks for writing that detailed explanation, Paul (and all your other hard
work!)
Richard
On 21 October 2017 at 21:03, Paul Moore wrote:
> On 20 October 2017 at 23:53, Richard Jones wrote:
> > Hiya Paul,
> >
> > There's a bunch of tooling out there using pi
Hiya Paul,
There's a bunch of tooling out there using pip's internals to extending
pip's functionality. Could you please provide a some reasoning as to why
they're all going to be broken at pip 10, and possibly some guidance on how
to get that functionality back?
Cheers,
Richard
On 21 Oc
On 2 June 2017 at 18:05, Nick Coghlan wrote:
> On 2 June 2017 at 09:00, Nick Timkovich wrote:
> > This issue was also brought up in January at
> > https://github.com/pypa/pypi-legacy/issues/585 then just as after the
> > initial "typosquatting PyPI" report (June 2016) it's met with resounding
>
On 2 June 2017 at 09:00, Nick Timkovich wrote:
> This issue was also brought up in January at https://github.com/pypa/pypi-
> legacy/issues/585 then just as after the initial "typosquatting PyPI"
> report (June 2016) it's met with resounding silence. Attacking the
> messenger doesn't seem like a
On 2 June 2017 at 03:40, Thomas Kluyver wrote:
> On Thu, Jun 1, 2017, at 06:32 PM, Matt Joyce wrote:
> There *appear* to be, but I checked several of the names listed there, and
> they're not on PyPI:
>
> https://pypi.python.org/pypi/tkinter
> https://pypi.python.org/pypi/memcached
> https://pypi
Hi all,
I've fallen seriously behind in trying to admin PyPI by myself, and I'm
calling for someone to help. Generally this means helping people reset
their email address for account recovery, or trying to contact owners of
packages to facilitate ownership changes. The *ahem* "tools" available
are
m: Donald Stufft
> Sent: 4/19/2016 21:52
> To: Richard Jones
> Cc: disutils-sig ; Christopher Wilcox
>
> Subject: Re: [Distutils] Parked Names in PyPI under user rodmena
>
> I’m 100% sure Steve is a Microsoft employee and I’m like 95% sure
> Christopher is too :)
>
>
Just to be clear, are you the user "Microsoft"? You're not posting from a @
microsoft.com email domain, is all. Or are you just a "concerned citizen"?
Because in the case of the latter there's really nothing for me to do here
without a request from someone actually wanting to do something with the
The usual process is to request such things through the support tracker so
there's a 'paper trail', but I've been unable to attend to the queue of
requests there recently so I'm going to make a special effort here. Please
do consider making a request in the support tracker though, thanks.
I'll get
On 18 April 2016 at 08:46, Guido van Rossum wrote:
> In a similar vein, the package distributor is listed as "zuroc" -- would
> this be someone else or just an alias for the owner?
>
That's the same person mentioned in your original mail.
Richard
__
Hi Guido,
Because this sort of thing has come up a lot in the past, and because I've
copped trouble for mishandling it in the past, I took the trouble of
writing up a formal description of how I handle these sorts of issues:
https://docs.google.com/document/d/1elum7ENjQb0dLB4ATfYNtnXYVLUzsKacc0VW
On 16 March 2016 at 03:41, Chris Barker wrote:
> Probably not the right list but:
>
> There are a number of folks having issue siwth new PyPi pacakges not being
> found by search:
>
>
> https://bitbucket.org/pypa/pypi/issues/412/my-package-doesnt-show-up-in-search
>
> clearly issues have been pos
ng to think about what we want to put in
> there.
> So this one:
>
> Framework :: Plone :: 5.1
>
> Thanks,
>
> Maurits
>
> Op 02/12/15 om 01:54 schreef Richard Jones:
>
>> At the moment it's a manual poke, but I have done this thing right now.
>>
>
At the moment it's a manual poke, but I have done this thing right now.
On 2 December 2015 at 10:46, James Bennett wrote:
> Reviving this old thread because today is Django 1.9's release date and
> I'm unsure of the process for keeping up with new-released versions in
> trove classifiers. Do we
Hi Mike,
Sorry, but this is a known problem that no-one has time to investigate or
fix.
Richard
On 29 September 2015 at 01:31, Mike O'Driscoll
wrote:
> Hello,
>
> I have been unable to login to the PyPi site for nearly a month now via
> OpenID (launchpad).
>
> I have the following ticket
On 22 July 2015 at 15:07, Brett Cannon wrote:
> When I wrote https://nothingbutsnark.svbtle.com/python-3-support-on-pypi
> I wrote a script to download every project's JSON metadata by scraping the
> simple index and then making the appropriate GET request for the JSON
> metadata. It worked, but
ge, not the 1.1 package.
>
>
> On Tue, Jul 7, 2015 at 4:23 PM, Richard Jones wrote:
>
>> This is very strange - perhaps there's a caching issue or something, but
>> there's a file present on that release when I look now :/
>>
>> On 7 July 2015 at 15:09
This is very strange - perhaps there's a caching issue or something, but
there's a file present on that release when I look now :/
On 7 July 2015 at 15:09, James Bennett wrote:
> Earlier tonight I was trying to upload a new version (1.1) of
> https://pypi.python.org/pypi/django-contact-form
>
>
Hi, PyPI is being kept on life-support, and I do not currently have time to
debug LaunchPad's openid. The only active development at present is
warehouse.
On Mon, 4 May 2015 at 05:49 anatoly techtonik wrote:
> Hi,
>
> Can't login with Google and with LaunchPad.
> Google breakage was predictable,
5 at 10:46 PM, Nick Coghlan wrote:
>
>>
>> On 3 Apr 2015 07:03, "Richard Jones" wrote:
>> >
>> > I can't speak for any plans others active in the PyPA might have, but
>> I'll be using the sprint time to work on Warehouse and hopefully help
&g
Could the BoF be Friday instead please? Saturday is International Tabletop
Day, and there's a bunch of us will be celebrating that :)
On Fri, 3 Apr 2015 at 08:46 Nick Coghlan wrote:
>
> On 3 Apr 2015 07:03, "Richard Jones" wrote:
> >
> > I can't speak f
I can't speak for any plans others active in the PyPA might have, but I'll
be using the sprint time to work on Warehouse and hopefully help others
work on it also.
I'm almost certain that my hallway track time will involve many
packaging-related discussions, as it always does :)
Richard
On
Added!
Framework :: Django :: 1.4
Framework :: Django :: 1.5
Framework :: Django :: 1.6
Framework :: Django :: 1.7
Framework :: Django :: 1.8
On Mon, 30 Mar 2015 at 16:09 James Bennett wrote:
> I would be OK with including 1.5 just for completeness' sake.
>
___
downstream tools like Django Packages will be
> an immense help to the Django ecosystem.
>
> --Danny
>
> On Sun, Mar 29, 2015 at 9:58 PM, Richard Jones wrote:
> > Hi James,
> >
> > I tend to just require that there already exists a number of packages
> that
> >
Hi James,
I tend to just require that there already exists a number of packages that
would use the classifier. Sounds like that's the case?
Richard
On Mon, 30 Mar 2015 at 15:50 James Bennett wrote:
> Following up on some IRC discussion with other folks:
>
> There is precedent (Plone) for
+1, JSONP was an interim hack solution way before CORS was an option.
On Thu, 19 Mar 2015 at 13:58 Donald Stufft wrote:
> For awhile now PyPI has supported JSONP on the /pypi/*/json API to allow
> people
> to access the JSON data in a cross origin request. JSONP is problematic
> psuedo
> standar
Sorry, there's no facility at present for signing a file that's already
uploaded.
On Mon Feb 23 2015 at 10:33:49 AM Ben Finney
wrote:
> Howdy all,
>
> How can I upload an OpenPGP signature (and the signing key) for a
> version, after the upload of the distribution is complete?
>
> I have recentl
Google has discontinued support for OpenID, so we're not going to be
putting any effort into debugging this issue.
Richard
On Sun Feb 08 2015 at 6:09:22 AM anatoly techtonik
wrote:
> Hi,
>
> Attempt to authorize with Google gives "Something wen wrong" page
> shown at https://pypi.python.o
Thanks for pointing that out. There's not lot we can do immediately, as any
significant improvement to search will require architecture changes.
Or, do what I do: use Google :)
[in the Bad Old Days, we used google site search, but people complained
that the results weren't pretty enough]
On Sat
Now that I think about it, I'm almost certain that Donald and I have had
the "hey, what about an upload.pypi.python.org" conversation in the past,
as a way around issues involving the CDN :)
Still a good idea, in my opinion.
Richard
On Wed Dec 31 2014 at 3:01:53 PM Nick Coghlan wrote:
>
Thanks for the clarification, guys.
Donald, I'm not sure what you mean by "a compromise of the CDN for
*uploading*".
On Wed Dec 31 2014 at 1:21:18 PM Donald Stufft wrote:
> On Dec 30, 2014, at 8:24 PM, Nick Coghlan wrote:
>
> On 23 December 2014 at 04:15, Vladimir Diaz
> wrote:
>
>> On Mon,
It has been a while since Pygments was updated in that environment, so I've
updated it. The PyPI code required a language argument, so I fixed that as
well.
Richard
On Mon Dec 29 2014 at 10:54:50 AM John Anderson wrote:
> On Sun, Dec 28, 2014 at 9:02 AM, Marius Gedminas wrote:
>
>> On S
Thanks for that, Fred. I've added all four classifiers.
Richard
On Thu Nov 27 2014 at 9:26:24 AM Fred Drake wrote:
> On Wed, Nov 26, 2014 at 5:15 PM, Richard Jones wrote:
> > Do you have any idea of the number of existing packages that would fit
> under
> > e
On Wed Nov 26 2014 at 9:47:07 PM Takayuki Shimizukawa
wrote:
> Hi Fred,
>
> On Tue Nov 25 2014 at 23:12:14 Fred Drake wrote:
>
>> On Wed, Nov 19, 2014 at 10:16 AM, Takayuki Shimizukawa
>> wrote:
>> > I'd like to request classifiers for the Sphinx like:
>> >
>> > "Topic :: Documentation :: Sphin
On Thu Nov 27 2014 at 9:08:40 AM Donaldo Fastoso
wrote:
> Somewhat OT,
>
> but i was wondering if there is documentation helping to choose
> the right classifiers if the choice is not obvious.
>
> For example i find the "Development Status" classifiers somewhat
> "quirky": 3 classifiers for alpha
+1 thanks for the detail
On 14 November 2014 13:21, Donald Stufft wrote:
> Starting a new thread with more explicit details at Richard’s request.
> Essentially the tl;dr here is that we'll switch to using sha2 (specifically
> sha256).
>
>
> Simple API
> --
>
> Drop the #md5= from the PyP
+1 pending detail
Sent from my mobile - please excuse any brevity.
On 13 Nov 2014 12:08, "Ian Cordasco" wrote:
> +1 from me as well
>
> On Wed, Nov 12, 2014 at 1:41 PM, Donald Stufft wrote:
> >
> >> On Nov 12, 2014, at 2:34 PM, Alex Gaynor wrote:
> >>
> >> Hi everybody!
> >>
> >> Right now, Py
It could get quite messy, without consensus. I figured custom tags would be
a more local thing.
On 30 October 2014 11:17, Donald Stufft wrote:
>
> On Oct 29, 2014, at 7:57 PM, Nick Coghlan wrote:
>
>
> On 30 Oct 2014 07:20, "Marcus Smith" wrote:
> >
> > yes, I'm partial to a solution like this
I am currently trying to decide what to do in the case of this request:
https://sourceforge.net/p/pypi/support-requests/420/
It is remarkably similar to the request which only just recently got me
into trouble, with the slight difference that there may be a trademark
issue which I am definitely no
Yep, I get notified of comments, thanks.
I'll add information on how to start the process - I always require an
issue in the support tracker.
On 14 October 2014 18:54, holger krekel wrote:
> On Tue, Oct 14, 2014 at 13:38 +1100, Richard Jones wrote:
> > Thanks for raising squattin
Thanks for raising squatting as a concern. I have added what I think is a
reasonable method of handling squatting (or otherwise unused name
registrations):
https://docs.google.com/document/d/1elum7ENjQb0dLB4ATfYNtnXYVLUzsKacc0VWnHHJb2A/edit?usp=sharing
Richard
On 14 October 2014 12:40, Ten
Hi folks, sorry for the delay, I was on vacation and then catching up on
stuff. I've composed a draft of the policy and I welcome your comments (in
the doc, please):
https://docs.google.com/document/d/1elum7ENjQb0dLB4ATfYNtnXYVLUzsKacc0VWnHHJb2A/edit?usp=sharing
My apologies if I've missed some n
On 29 September 2014 08:02, Donald Stufft
wrote:
>
> I forgot to mention, there is also testpypi.python.org which can be used
> to test
> builds prior to publishing them to PyPI. There is also devpi which I
> believe has
> the option to push from one of the devpi indexes straight to PyPI as well
>
He means a file with the same file name, but not necessarily the same
content.
On 29 September 2014 07:54, John Yeuk Hon Wong
wrote:
> On 9/28/14 5:23 PM, Donald Stufft wrote:
>
>
> You can delete them and then reupload the same file with different
> contents.
>
> Sorry, but I am confused: wha
29 September 2014 07:54, Richard Jones wrote:
> Just to reiterate: from the beginning uploaded files were immutable, but
> the later addition of deletion gave uploaders the loophole through which
> they could not confuse downloaders of their packages.
>
> On 29 September 2014 07:
Just to reiterate: from the beginning uploaded files were immutable, but
the later addition of deletion gave uploaders the loophole through which
they could not confuse downloaders of their packages.
On 29 September 2014 07:36, M.-A. Lemburg wrote:
> On 28.09.2014 21:31, Donald Stufft wrote:
> >
The intent was always that files were immutable. The deleting loophole is
just something that I never got around to fixing.
+1 to fix that bug :)
On 29 September 2014 07:23, Donald Stufft wrote:
>
> On Sep 28, 2014, at 5:21 PM, Ethan Furman wrote:
>
> On 09/28/2014 12:31 PM, Donald Stufft wrot
Hi all,
Having had some time to think this over, I will attempt to explain what the
current process is, and how I believe I should change it. It's worth noting
that I'm the only person who handles support issues for PyPI (years ago
Martin von Lowis also did this, and Donald Stufft has handled one
On 20 September 2014 04:47, Daniel Greenfeld wrote:
> In order to claim a package as being abandoned it should undergo a
> formal process that includes:
>
> * Placement on a PUBLIC list of packages under review for a grace
> period to be determined by this discussion
>
This is not done at presen
Hi Bence,
Please file a support issue using the link in the pypi sidebar.
Richard
On 2 September 2014 12:08, Bence Nagy wrote:
> Hey there,
>
> I've submitted a pull request on GitHub[0] for the package
> Flask-Redis[1] 6 months ago. It didn't contain anything of real
> importance, but I
Wow, a huge thanks to everyone named (as well as you, Nick ;) for
persevering and getting this through.
On 22 August 2014 22:34, Nick Coghlan wrote:
> I just pushed Donald's final round of edits in response to the
> feedback on the last PEP 440 thread, and as such I'm happy to announce
> that I
Try clearing your cookies for PyPI and see if that helps. It has helped me
in the past.
On 22 August 2014 17:02, Adam GROSZER wrote:
> Hi,
>
> On some mornings (today too) I get such errors when trying to access any
> package on PyPI:
>
> Error 503 backend read error
>
> backend read error
>
>
Linux wheels are generally not compatible in a non-local sense, so it's
unlikely those will be distributable through PyPI. That would also mean
it's probably unlikely they'll be built there.
Something related to this also cane up in discussion at europython but I
don't want to steal any thunder :-
On 25 July 2014 15:21, Nick Coghlan wrote:
> On 25 July 2014 23:13, Richard Jones wrote:
> > A variation on the above two ideas is to just record the *link* to the
> > externally-hosted file from PyPI, rather than that file's content. It is
> > more error-prone,
[apologies for the terrible quoting, gmail's magic failed today]
On 24 July 2014 17:41, Donald Stufft wrote:
> On July 24, 2014 at 7:26:11 AM, Richard Jones (r1chardj0...@gmail.com)
wrote:
>
> > This PEP proposes a potentially confusing break for both users and
packagers. In p
Several great ideas came out of today's meetup. Some of those I'll leave to
the proponents themselves to post about, but a couple of little nuggets for
thought:
1. reject wheel uploads in the absence of an sdist in the index (the linux
guys were really happy about that as a proposal ;)
2. add a sy
p where I can have you
> install “django-foobar” which depends on “FakeDjango”, which provides
> “Django”, and then for all intents and purposes you have a “Django” package
> installed.
>
> Can you go into more detail? Particularly, the part where "FakeDjango"
> provid
Thanks for responding, even from your sick bed.
This message about users having to view and understand /simple/ indexes is
repeated many times. I didn't have to do that in the case of PIL. The tool
told me "use --allow-external PIL to allow" and then when that failed it
told me "use --allow-unveri
I have been mulling over PEP 470 for some time without having the time to
truly dedicate to addressing it. I believe I'm up to date with its contents
and the (quite significant, and detailed) discussion around it.
To summarise my understanding, PEP 470 proposes to remove the current link
spidering
hias Klose wrote:
> Am 21.07.2014 14:09, schrieb Richard Jones:
> > I've set the time for the packaging meetup to 11:00 this Thursday. There
> is
> > currently no meeting room available for such a gathering, so we'll just
> > meet outside in the garden.
>
>
I've set the time for the packaging meetup to 11:00 this Thursday. There is
currently no meeting room available for such a gathering, so we'll just
meet outside in the garden.
Richard
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://
Thanks for the feedback, Josh.
The Python 3 version of the distutils documentation is far improved on this
topic, I believe (though please, file a bug / change if you can improve it
:)
https://docs.python.org/3/distutils/sourcedist.html#manifest
The setuptools documentation is part of the rep
Yep, I understand and sympathise with the frustration.
On 15 July 2014 19:24, Wichert Akkerman wrote:
>
> > On 15 Jul 2014, at 11:22, Richard Jones wrote:
> >
> > Hi, I just want to note that I'm aware of this issue and I have "do
> something about it"
Hi, I just want to note that I'm aware of this issue and I have "do
something about it" in my long TODO.
That link is malformed in any case - docutils just passes it on through and
you're just lucky that browsers will guess that it is supposed to have a
"http://"; scheme on the front. PyPI does in
On 3 July 2014 17:03, holger krekel wrote:
> Hi Richard,
>
> On Wed, Jul 02, 2014 at 21:25 -0400, Donald Stufft wrote:
> > On Jul 2, 2014, at 9:07 PM, Richard Jones
> wrote:
> >
> > > Hi folks,
> > >
> > > I'd like to get interested folks
Hi folks,
I'd like to get interested folks together at EuroPython to get up to date,
talk through current issues and generally catch up on all things Python
Packaging.
Specific things we'll be talking about:
- current tools: where they're at and what their plans are
- the state of PEPs 426, 440,
I occasionally receive requests from package maintainers asking to
have their PyPI package renamed (for example, renaming
"eyepea_monitoring_agent" to "tanto"). The only response I have at the
moment is to tell them to release their package under both the new and
old names in parallel, and promote
I don't know who maintains it.
On 20 May 2014 23:45, Donald Stufft wrote:
>
> On May 20, 2014, at 9:39 AM, Max Norris wrote:
>
>> The PyPI Twitter feed stopped updating a couple of weeks back -- kind of
>> missing seeing it, found all sorts of fun things I wouldn't have otherwise
>> noticed, a
I'll be there, doing my best to hold up the PyPI / Warehouse banner. And
work on some of the code during the sprints, assuming I don't get
distracted by writing another PEP like last time (but look where that
eventually led us :)
I am most likely going to go to the language summit as a lurker to s
Let's do it. PEP accepted.
On 22 March 2014 07:51, Donald Stufft wrote:
> Ping on a decree/pronouncement for this? :]
>
> On Mar 11, 2014, at 3:53 PM, Christian Theune wrote:
>
> >
> > On 11. Mar2014, at 20:01, Donald Stufft wrote:
> >
> >> I think maybe we're ready for a decree on this? I di
It definitely looks like we've got some issues introduced in recent server
migrations and reconfigurations. Things I'm aware of:
- OAuth is busted
- OpenID is confused and/or busted
- password reset is possibly busted
- pypissh is busted
Richard
On 27 January 2014 00:26, Alex Clark wrote
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
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
[Oops. I keep forgetting to check the bitbucket tracker for support issues
which are intended to (and mostly do) go to the sourceforge tracker.]
As the PyPI admin, I deal with naming issues that come up, which happens
not too frequently thankfully. Usually they're resolved reasonably easily
when I
Hi, (just FYI I live in UTC+10 so immediate responses sometimes aren't
reasonable to expect), could you clarify which list of Python 3 packages
you're referring to? I presume it's this one:
https://pypi.python.org/pypi?:action=browse&c=533&show=all
In which case I think I might be able to quickly
On 5 December 2013 23:22, Jesus Cea wrote:
> Programming Language :: Python :: 3.4
>
Added!
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
I was working from (clearly hazy) memory. Sorry for the red herring.
On 1 December 2013 09:10, Donald Stufft wrote:
> Hiding a release doesn’t hide it from the simple index, so installers will
> still find it.
>
> On Nov 30, 2013, at 4:59 PM, Richard Jones wrote:
>
> There i
There is no way to mark a release as "pre-release" but you can hide it from
view which would prevent an installer discovering any files related to the
release. Log into PyPI and use the "releases" page for the project.
On 30 November 2013 22:05, anatoly techtonik wrote:
> hi, please cc
>
> i w
nk in my
> browser (FF), no rpc call was made. I expected a "not for browsers" message
> or similar rather than an error.
>
> -matt
>
>
> On Sat, Nov 16, 2013 at 12:29 AM, Richard Jones wrote:
>
>> Hi Matt,
>>
>> What method you were calling? What ar
Hi Matt,
What method you were calling? What arguments did you pass? What xml-rpc
library you were using?
Actual code would be ideal.
Thanks,
Richard
On 16 November 2013 18:12, Matt Wilkie wrote:
>
> On Fri, Nov 15, 2013 at 7:12 PM, Donald Stufft wrote:
>
>> https://preview-pypi.pytho
Because (distutils history) it's currently not possible to "python setup.py
upload" using the secure HTTPS URL of PyPI. It is possible using twine*
which I'd like to promote at:
https://pypi.python.org/pypi(in the "Package Authors" box)
http://docs.python.org/3/distutils/packageindex.html
features right now and not next
> PyCon. Also, am I right that bus factor for this stuff is one?
> --
> anatoly t.
>
>
> On Mon, Oct 28, 2013 at 2:53 AM, Richard Jones
> wrote:
> > I have merged that PR but I really don't see any point in making any
> changes
>
I have merged that PR but I really don't see any point in making any
changes to the current codebase beyond fixing significant issues. Cleaning
it up is not a priority. I've merged this PR to clean up the PyPI project
page on bitbucket a little, but I would ask that no further cosmetic PRs be
submi
Thanks for noticing, we'll have a look.
Richard
On 25 October 2013 02:14, Gabriel de Perthuis wrote:
> Hello,
> The IP log that shows who did what on PyPI pages shows
> some IPs that have no business being there; they seem
> to come from CDNs, in my case fastly and wikia.
> Can this be f
Yay! Thanks everyone involved, especially Donald and Nick.
On 22 October 2013 23:05, Nick Coghlan wrote:
> For those distutils-sig residents that don't follow python-dev, a
> certain PEP was formally accepted today :)
>
> -- Forwarded message --
> From: "Martin v. Löwis"
> Date
Er, yeah, sorry, I misspoke there. The change I made to the page just talks
about the DNS being killed off and points to the PEP.
On 29 September 2013 16:44, Donald Stufft wrote:
> Only the naming scheme is dead, protocol itself is still fine.
>
> On Sep 29, 2013, at 1:52 AM, Rich
I've edited the /mirrors page to reflect the new mirroring reality (and
pushed to the repos which I *think* will result in it being pushed to the
server, yes?)
Richard
On 29 September 2013 16:13, Nick Coghlan wrote:
> On 29 September 2013 13:07, Donald Stufft wrote:
> >
> > On Sep 28,
Like Nick I'm not sure I see the urgency here. I'm going to add a
deprecation statement to the public mirroring page at /mirrors so it's
clear that protocol is dead (not just resting).
Richard
On 29 September 2013 13:07, Donald Stufft wrote:
>
> On Sep 28, 2013, at 10:16 PM, Nick Coghlan
I added the use of README to catch all the github users who weren't filling
in their long_description (but also weren't using Markdown - I just didn't
find the time to also add something to detect Markdown and render it).
On 23 September 2013 08:01, Chris Jerdonek wrote:
> On Sun, Sep 22, 2013
Hi all,
Given that I believe all outstanding issues with PEP 449 <
http://python.org/dev/peps/pep-0449/> have been resolved I will accept it
in its current form (last modified August 16) so the immediate changes may
be made and publicity of the change can be started.
My thanks to everyone involve
Sorry Alexis!
I'm a little confused as to how Pelican deserves to be considered a
framework. Generally before we add a Framework classifier we need to
see a number of packages in PyPI which would have that classifier
applied to them. Can you point to such packages?
Richard
On 1 August 2013
Hi all,
I've just been contacted by someone who's set up a new public mirror
of PyPI and would like it integrated into the mirror ecosystem.
I think it's probably time we thought about how to demote the mirrors:
- they cause problems with security (being under the python.org domain
causes variou
The point of PEP 439 is that the current situation of "but first do
this" for any given 3rd-party package installation was a bad thing and
we desire to move away from it. The PEP therefore proposes to allow
"just do this" to eventually become the narrative. The direction this
conversation is headin
On 11 July 2013 06:50, Paul Moore wrote:
> I think "python -m pip" should be the canonical form (used in documentation,
> examples, etc). The unittest module has taken this route, as has timeit.
> Traditionally, python-dev have been lukewarm about the -m interface, but its
> key advantage is that
On 10 July 2013 19:55, Vinay Sajip wrote:
> Richard Jones python.org> writes:
>
>> It makes sense to me (and Nick) to simplify the packaging overhead for
>> users of Python 2. Currently the story is a bit of a mess (multiple
>> sites with different approaches).
>
&g
On 10 July 2013 19:08, Vinay Sajip wrote:
> Richard Jones gmail.com> writes:
>
>> pip without virtualenv in python 2 contexts is pretty rare (or at
>> least *should* be ) so I think I'll retain it in that bootstrap
>> code.
>
> Perhaps I misunderstand
On 10 July 2013 18:28, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/09/2013 11:20 PM, Donald Stufft wrote:
>
>> doesn't "PyEnv" which is bundled with Python 3.3+ replace virtualenv?
>> What's the purpose of including virtualenv in the bootstrap?
>> http://www.pyth
On 10 July 2013 14:19, Carl Meyer wrote:
> They certainly do today, but that's primarily because pyvenv isn't very
> useful yet, since the stdlib has no installer and thus a newly-created
> pyvenv has no way to install anything in it.
Ah, thanks for clarifying that.
> Certainly if the bootstrap
On 10 July 2013 14:18, Donald Stufft wrote:
> On Jul 9, 2013, at 11:47 PM, Richard Jones wrote:
>> On 10 July 2013 13:20, Donald Stufft wrote:
>>> On Jul 9, 2013, at 11:16 PM, Richard Jones wrote:
>>> Firstly, I've just made some additional changes to PEP 439
On 10 July 2013 13:20, Donald Stufft wrote:
> On Jul 9, 2013, at 11:16 PM, Richard Jones wrote:
> Firstly, I've just made some additional changes to PEP 439 to include:
>
> - installing virtualenv as well (so now pip, setuptools and virtualenv are
> installed)
>
>
1 - 100 of 132 matches
Mail list logo
