From g.brandl at gmx.net Tue May 1 09:32:41 2012
From: g.brandl at gmx.net (Georg Brandl)
Date: Tue, 01 May 2012 09:32:41 +0200
Subject: [Catalog-sig] PGP key for pip package
In-Reply-To: <CALKRDOmrnjiTVyXJ=sHLqUW3iQxMUXN3Z8r_wT=4B=SrpviX5g@mail.gmail.com>
References: <CALKRDOmrnjiTVyXJ=sHLqUW3iQxMUXN3Z8r_wT=4B=SrpviX5g@mail.gmail.com>
Message-ID: <jno3hp$16o$1@dough.gmane.org>
On 30.04.2012 17:52, David Fischer wrote:
> Hi,
>
> I've been playing around with PGP signing as it relates to Python
> packages. There are relatively few signed packages in Cheeseshop but
> one of them is the pip package[1]. Does anyone know where I could get
> the public key used to verify this package (key ID 0171DF30)? Perhaps
> I am missing something obvious.
I could import it from hkp://wwwkeys.pgp.net, but only when searching for
"Leidel", and not for the ID.
Georg
From martin at v.loewis.de Tue May 1 12:10:56 2012
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 01 May 2012 12:10:56 +0200
Subject: [Catalog-sig] PGP key for pip package
In-Reply-To: <jno3hp$16o$1@dough.gmane.org>
References: <CALKRDOmrnjiTVyXJ=sHLqUW3iQxMUXN3Z8r_wT=4B=SrpviX5g@mail.gmail.com>
<jno3hp$16o$1@dough.gmane.org>
Message-ID: <4F9FB6B0.9080303@v.loewis.de>
On 01.05.2012 09:32, Georg Brandl wrote:
> On 30.04.2012 17:52, David Fischer wrote:
>> Hi,
>>
>> I've been playing around with PGP signing as it relates to Python
>> packages. There are relatively few signed packages in Cheeseshop but
>> one of them is the pip package[1]. Does anyone know where I could get
>> the public key used to verify this package (key ID 0171DF30)? Perhaps
>> I am missing something obvious.
>
> I could import it from hkp://wwwkeys.pgp.net, but only when searching for
> "Leidel", and not for the ID.
If you put "0x0171DF30" into "Search String" at http://pgp.mit.edu/,
it sends you to
http://pgp.mit.edu:11371/pks/lookup?search=0x0171DF30&op=index
Regards,
Martin
From djfische at gmail.com Tue May 1 18:19:15 2012
From: djfische at gmail.com (David Fischer)
Date: Tue, 1 May 2012 09:19:15 -0700
Subject: [Catalog-sig] PGP key for pip package
In-Reply-To: <4F9FB6B0.9080303@v.loewis.de>
References: <CALKRDOmrnjiTVyXJ=sHLqUW3iQxMUXN3Z8r_wT=4B=SrpviX5g@mail.gmail.com>
<jno3hp$16o$1@dough.gmane.org> <4F9FB6B0.9080303@v.loewis.de>
Message-ID: <CALKRDOmaKyBbu_rUFJKnzEeJ_xz-ziG6vQSV9LOF7kvR6UL+OA@mail.gmail.com>
This is perfect. I had looked on pgp.mit.edu, but I had neglected the
"0x" prefix and my search turned up nothing.
Thanks guys.
-David
On Tue, May 1, 2012 at 3:10 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> On 01.05.2012 09:32, Georg Brandl wrote:
>>
>> On 30.04.2012 17:52, David Fischer wrote:
>>>
>>> Hi,
>>>
>>> I've been playing around with PGP signing as it relates to Python
>>> packages. There are relatively few signed packages in Cheeseshop but
>>> one of them is the pip package[1]. Does anyone know where I could get
>>> the public key used to verify this package (key ID 0171DF30)? Perhaps
>>> I am missing something obvious.
>>
>>
>> I could import it from hkp://wwwkeys.pgp.net, but only when searching for
>> "Leidel", and not for the ID.
>
>
> If you put "0x0171DF30" into "Search String" at http://pgp.mit.edu/,
> it sends you to
>
> http://pgp.mit.edu:11371/pks/lookup?search=0x0171DF30&op=index
>
> Regards,
> Martin
>
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig
From techtonik at gmail.com Tue May 8 16:28:14 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 8 May 2012 14:28:14 +0000 (UTC)
Subject: [Catalog-sig] PyPI code now on bitbucket
References: <4F6219D0.6050507@v.loewis.de>
<91210437-8AED-4E98-9A2D-60E7A08621EF@coderanger.net>
<4F622D10.2060901@v.loewis.de>
<65F51FC4-6703-4322-8AA9-F6C0372BB73C@coderanger.net>
<CAJgxfqbZ5UEY5qUdowdviNye+7x0PSbeZT-wwAcWLz776pPrxw@mail.gmail.com>
<4F6236AD.1020909@v.loewis.de>
<7C4DF68A-0D46-484F-8E2B-7E03F6010FF8@coderanger.net>
Message-ID: <loom.20120508T161525-13@post.gmane.org>
Hi,
Noah Kantrowitz <noah <at> coderanger.net> writes:
>
> Doug, can you make a PyPI repo under the PSF account and add martin and
richard as admins? Then you can just
> push there too and all will be well You might want to just remove the copy
under your username and fork the
> main one after that so it is in the forks list, but the repo under your
username can be used for your personal
> development while the main one stays stable for deployment.
>
> --Noah
>
> On Mar 15, 2012, at 11:36 AM, Martin v. L?wis wrote:
>
> > Am 15.03.12 11:19, schrieb Jesper Noehr:
> >> Doug Hellmann sits on the PSF account on our end.
> >
> > Ah, ok. Who needs to do what to make this happen?
> >
> > Regards,
> > Martin
Great news. I may now kill my own mirror. =)
Sorry for the mess - Gmane doesn't allow top posting.
Who not just open `pydotorg` account and move all *.python.org code there? PSF
looks more like a financial institution than a community that supports this
stuff. It will make clear that you don't need to be a member of PSF to
contribute.
Please, CC.
From techtonik at gmail.com Wed May 9 12:51:53 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 9 May 2012 13:51:53 +0300
Subject: [Catalog-sig] PyPI pull request
Message-ID: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
Hi,
Anybody to merge my changes from
https://bitbucket.org/techtonik/pypi-techtonik ?
--
anatoly t.
From dglick at gmail.com Fri May 11 00:56:24 2012
From: dglick at gmail.com (David Glick)
Date: Thu, 10 May 2012 22:56:24 +0000 (UTC)
Subject: [Catalog-sig] spam on PyPI
Message-ID: <loom.20120511T005507-518@post.gmane.org>
Someone is posting spam to PyPI today. Examples:
http://pypi.python.org/pypi/drsultan/Spell%20Caster%20and%20spiritual%20healer.%20Call%3B%20%20%20%2B27722820647
http://pypi.python.org/pypi/drsultan/Strong%20Spell%20Caster%20and%20spiritual%20healer.%20Call%3B%20%20%20%2B27722820647
From richard at python.org Fri May 11 01:27:23 2012
From: richard at python.org (Richard Jones)
Date: Fri, 11 May 2012 09:27:23 +1000
Subject: [Catalog-sig] spam on PyPI
In-Reply-To: <loom.20120511T005507-518@post.gmane.org>
References: <loom.20120511T005507-518@post.gmane.org>
Message-ID: <CAHrZfZCmmY+=yTgZ2tHCWP4jvThu-oMvsMLXtxB0b+7P=q7D7A@mail.gmail.com>
On 11 May 2012 08:56, David Glick <dglick at gmail.com> wrote:
> Someone is posting spam to PyPI today. Examples:
> http://pypi.python.org/pypi/drsultan/Spell%20Caster%20and%20spiritual%20healer.%20Call%3B%20%20%20%2B27722820647
> http://pypi.python.org/pypi/drsultan/Strong%20Spell%20Caster%20and%20spiritual%20healer.%20Call%3B%20%20%20%2B27722820647
Thanks for reporting it, and thanks to whoever cleaned it up.
Richard
From martin at v.loewis.de Fri May 11 01:29:10 2012
From: martin at v.loewis.de (martin at v.loewis.de)
Date: Fri, 11 May 2012 01:29:10 +0200
Subject: [Catalog-sig] spam on PyPI
In-Reply-To: <loom.20120511T005507-518@post.gmane.org>
References: <loom.20120511T005507-518@post.gmane.org>
Message-ID: <20120511012910.Horde.3nPbcVNNcXdPrE9GZujieGA@webmail.df.eu>
Zitat von David Glick <dglick at gmail.com>:
> Someone is posting spam to PyPI today.
Thanks! Deleted.
Regards,
Martin
From techtonik at gmail.com Sat May 12 11:21:05 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 12 May 2012 12:21:05 +0300
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
Message-ID: <CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
On Wed, May 9, 2012 at 1:51 PM, anatoly techtonik <techtonik at gmail.com> wrote:
> Hi,
>
> Anybody to merge my changes from
> https://bitbucket.org/techtonik/pypi-techtonik ?
Richard told me he is busy preparing for the PyCon AU and
administering ongoing PyGame, so no help here.
Martin told it will take time. So, anybody else at least to review and comment?
https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
I also sent mail to PSF requesting a new `pydotorg` account on
Bitbucket, so that there will be a permanent home for official mirror
for PyPI that can be found using Bitbucket search along with other
open repositories for web to send pull requests to.
In the meanwhile there few more clean up changes, one of which loosens
dependency on M2Crypto, which is not installable in virtualenv if you
don't have SWIG installed systemwide. Although it doesn't remove it
completely yet. The goal is to make pycrypto an optional alternative
for M2Crypto for an easy development.
From pydanny at gmail.com Sat May 12 15:17:41 2012
From: pydanny at gmail.com (Daniel Greenfeld)
Date: Sat, 12 May 2012 06:17:41 -0700
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
Message-ID: <CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
Anatoly,
Here's a major issues with your pull request:
It's not atomic enough. PyPI is a massive effort so any pull request
should be as small as possible. For example, "running without sentry
client" should be just a single pull request. By combining multiple
"actions" into one pull requests, you've made it harder for the PyPI
authors to evaluate your work. Which means they'll be less inclined to
review it.
Break this up into 3 separate pull requests. It's easy to do with
branching, and the maintainers of the project will appreciate you for
it.
In fact, one thing we did with Open Comparison
(http://djangopackages.com, http://pyramid.opencomparison.org, and
soon http://python.opencomparison.org) that as helped us a lot as
maintainers is write a formal contributing document that spells this
out and more. See:
http://opencomparison.readthedocs.org/en/latest/contributing.html
and in your case, specifically:
http://opencomparison.readthedocs.org/en/latest/contributing.html#how-to-get-your-pull-request-accepted
I suggest to Richard and Martin they adopt something similar. Or they
can use our contributing rules in the same manner as Read the Docs:
https://github.com/rtfd/readthedocs.org/blob/master/docs/contribute.rst
Danny
On Sat, May 12, 2012 at 2:21 AM, anatoly techtonik <techtonik at gmail.com> wrote:
> On Wed, May 9, 2012 at 1:51 PM, anatoly techtonik <techtonik at gmail.com> wrote:
>> Hi,
>>
>> Anybody to merge my changes from
>> https://bitbucket.org/techtonik/pypi-techtonik ?
>
> Richard told me he is busy preparing for the PyCon AU and
> administering ongoing PyGame, so no help here.
> Martin told it will take time. So, anybody else at least to review and comment?
>
> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
>
> I also sent mail to PSF requesting a new `pydotorg` account on
> Bitbucket, so that there will be a permanent home for official mirror
> for PyPI that can be found using Bitbucket search along with other
> open repositories for web to send pull requests to.
>
> In the meanwhile there few more clean up changes, one of which loosens
> dependency on M2Crypto, which is not installable in virtualenv if you
> don't have SWIG installed systemwide. Although it doesn't remove it
> completely yet. The goal is to make pycrypto an optional alternative
> for M2Crypto for an easy development.
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig
--
'Knowledge is Power'
Daniel Greenfeld
http://pydanny.com
From techtonik at gmail.com Sat May 12 17:09:44 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 12 May 2012 18:09:44 +0300
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
<CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
Message-ID: <CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
Hi Daniel,
You're request and proposed action would be nice if it used Mercurial,
but it uses Git + GitHub and have
https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-inabsolutely
no idea how to apply it to Mercurial + Bitbucket. If I understand you
correctly for every 7 commits in queue I need to make a separate clone
and commit it separately. That's far from the that beautiful promise
DVCS made. =)
All commits are available in pull request separately. If you take
another look at
https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
you'll see there is an ongoing discussion over a questionable commit
with Martin. Feel free to comment on any revision. I can rework them
one by one on request if they are taking too much time to review.
Your wish is valid and well understood, but for specific big features.
For a series of small clean up changes such as this one this places a
more constrain on the person submitting changes. So unless there is a
comment that code is too complicated, I'd prefer to save this extra
time to polishing other aspects.
There are also 4 more commits in my copy waiting for this review to
complete, which I deliberately doesn't add to this request to
On Sat, May 12, 2012 at 4:17 PM, Daniel Greenfeld <pydanny at gmail.com> wrote:
> Anatoly,
>
> Here's a major issues with your pull request:
>
> It's not atomic enough. PyPI is a massive effort so any pull request
> should be as small as possible. For example, "running without sentry
> client" should be just a single pull request. By combining multiple
> "actions" into one pull requests, you've made it harder for the PyPI
> authors to evaluate your work. Which means they'll be less inclined to
> review it.
>
> Break this up into 3 separate pull requests. It's easy to do with
> branching, and the maintainers of the project will appreciate you for
> it.
>
> In fact, one thing we did with Open Comparison
> (http://djangopackages.com, http://pyramid.opencomparison.org, and
> soon http://python.opencomparison.org) that as helped us a lot as
> maintainers is write a formal contributing document that spells this
> out and more. See:
>
> http://opencomparison.readthedocs.org/en/latest/contributing.html
>
> and in your case, specifically:
>
> http://opencomparison.readthedocs.org/en/latest/contributing.html#how-to-get-your-pull-request-accepted
>
> I suggest to Richard and Martin they adopt something similar. Or they
> can use our contributing rules in the same manner as Read the Docs:
>
> https://github.com/rtfd/readthedocs.org/blob/master/docs/contribute.rst
>
> Danny
>
> On Sat, May 12, 2012 at 2:21 AM, anatoly techtonik <techtonik at gmail.com> wrote:
>> On Wed, May 9, 2012 at 1:51 PM, anatoly techtonik <techtonik at gmail.com> wrote:
>>> Hi,
>>>
>>> Anybody to merge my changes from
>>> https://bitbucket.org/techtonik/pypi-techtonik ?
>>
>> Richard told me he is busy preparing for the PyCon AU and
>> administering ongoing PyGame, so no help here.
>> Martin told it will take time. So, anybody else at least to review and comment?
>>
>> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
>>
>> I also sent mail to PSF requesting a new `pydotorg` account on
>> Bitbucket, so that there will be a permanent home for official mirror
>> for PyPI that can be found using Bitbucket search along with other
>> open repositories for web to send pull requests to.
>>
>> In the meanwhile there few more clean up changes, one of which loosens
>> dependency on M2Crypto, which is not installable in virtualenv if you
>> don't have SWIG installed systemwide. Although it doesn't remove it
>> completely yet. The goal is to make pycrypto an optional alternative
>> for M2Crypto for an easy development.
>> _______________________________________________
>> Catalog-SIG mailing list
>> Catalog-SIG at python.org
>> http://mail.python.org/mailman/listinfo/catalog-sig
>
>
>
> --
> 'Knowledge is Power'
> Daniel Greenfeld
> http://pydanny.com
From pydanny at gmail.com Sat May 12 17:24:12 2012
From: pydanny at gmail.com (Daniel Greenfeld)
Date: Sat, 12 May 2012 08:24:12 -0700
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
<CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
<CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
Message-ID: <CAOoSJ_okuLpMRWShQurfJGAKWCkpmwVJjv0QaGh8NjOj2mEnBw@mail.gmail.com>
This is Martin and Richard's project. If they want to insist on
separate pull requests per feature being worked on, rather than having
to cherry pick and analyze each segment of code you submitted before
accepting it, then that's how they should do it. Of course they
haven't said anything yet, but I'm just saying it's up to them.
Also, the pattern I described to you fits very well within the
beautiful promise of DVCS. The cleaner branching and merging of DVCS
makes this sort of approach wonderful for all parties involved. Rather
than giant, monolithic pull requests with lots of tiny commits, they
get very easy to integrate pull requests.
Smaller, atomic pieces are much easier to handle then larger
multi-task components. Isn't that the promise of OOP and functional
programming? :-)
Danny
On Sat, May 12, 2012 at 8:09 AM, anatoly techtonik <techtonik at gmail.com> wrote:
> Hi Daniel,
>
> You're request and proposed action would be nice if it used Mercurial,
> but it uses Git + GitHub and have
> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-inabsolutely
> no idea how to apply it to Mercurial + Bitbucket. If I understand you
> correctly for every 7 commits in queue I need to make a separate clone
> and commit it separately. That's far from the that beautiful promise
> DVCS made. =)
>
> All commits are available in pull request separately. If you take
> another look at
> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
> you'll see there is an ongoing discussion over a questionable commit
> with Martin. Feel free to comment on any revision. I can rework them
> one by one on request if they are taking too much time to review.
>
> Your wish is valid and well understood, but for specific big features.
> For a series of small clean up changes such as this one this places a
> more constrain on the person submitting changes. So unless there is a
> comment that code is too complicated, I'd prefer to save this extra
> time to polishing other aspects.
>
> There are also 4 more commits in my copy waiting for this review to
> complete, which I deliberately doesn't add to this request to
>
> On Sat, May 12, 2012 at 4:17 PM, Daniel Greenfeld <pydanny at gmail.com> wrote:
>> Anatoly,
>>
>> Here's a major issues with your pull request:
>>
>> It's not atomic enough. PyPI is a massive effort so any pull request
>> should be as small as possible. For example, "running without sentry
>> client" should be just a single pull request. By combining multiple
>> "actions" into one pull requests, you've made it harder for the PyPI
>> authors to evaluate your work. Which means they'll be less inclined to
>> review it.
>>
>> Break this up into 3 separate pull requests. It's easy to do with
>> branching, and the maintainers of the project will appreciate you for
>> it.
>>
>> In fact, one thing we did with Open Comparison
>> (http://djangopackages.com, http://pyramid.opencomparison.org, and
>> soon http://python.opencomparison.org) that as helped us a lot as
>> maintainers is write a formal contributing document that spells this
>> out and more. See:
>>
>> http://opencomparison.readthedocs.org/en/latest/contributing.html
>>
>> and in your case, specifically:
>>
>> http://opencomparison.readthedocs.org/en/latest/contributing.html#how-to-get-your-pull-request-accepted
>>
>> I suggest to Richard and Martin they adopt something similar. Or they
>> can use our contributing rules in the same manner as Read the Docs:
>>
>> https://github.com/rtfd/readthedocs.org/blob/master/docs/contribute.rst
>>
>> Danny
>>
>> On Sat, May 12, 2012 at 2:21 AM, anatoly techtonik <techtonik at gmail.com> wrote:
>>> On Wed, May 9, 2012 at 1:51 PM, anatoly techtonik <techtonik at gmail.com> wrote:
>>>> Hi,
>>>>
>>>> Anybody to merge my changes from
>>>> https://bitbucket.org/techtonik/pypi-techtonik ?
>>>
>>> Richard told me he is busy preparing for the PyCon AU and
>>> administering ongoing PyGame, so no help here.
>>> Martin told it will take time. So, anybody else at least to review and comment?
>>>
>>> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
>>>
>>> I also sent mail to PSF requesting a new `pydotorg` account on
>>> Bitbucket, so that there will be a permanent home for official mirror
>>> for PyPI that can be found using Bitbucket search along with other
>>> open repositories for web to send pull requests to.
>>>
>>> In the meanwhile there few more clean up changes, one of which loosens
>>> dependency on M2Crypto, which is not installable in virtualenv if you
>>> don't have SWIG installed systemwide. Although it doesn't remove it
>>> completely yet. The goal is to make pycrypto an optional alternative
>>> for M2Crypto for an easy development.
>>> _______________________________________________
>>> Catalog-SIG mailing list
>>> Catalog-SIG at python.org
>>> http://mail.python.org/mailman/listinfo/catalog-sig
>>
>>
>>
>> --
>> 'Knowledge is Power'
>> Daniel Greenfeld
>> http://pydanny.com
--
'Knowledge is Power'
Daniel Greenfeld
http://pydanny.com
From martin at v.loewis.de Sat May 12 17:28:11 2012
From: martin at v.loewis.de (martin at v.loewis.de)
Date: Sat, 12 May 2012 17:28:11 +0200
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
<CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
<CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
Message-ID: <20120512172811.Horde.3dUEP9jz9kRProGL2w6wkFA@webmail.df.eu>
> All commits are available in pull request separately.
This is not sufficient, is it? If I want to accept change 1 and change 3,
and reject change 2, how can I pull change 3 without also integrating change
2?
Regards,
Martin
From kai.diefenbach at iqpp.de Sat May 12 19:27:02 2012
From: kai.diefenbach at iqpp.de (Kai Diefenbach)
Date: Sat, 12 May 2012 19:27:02 +0200
Subject: [Catalog-sig] PyPI pull request
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
<CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
<CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
<20120512172811.Horde.3dUEP9jz9kRProGL2w6wkFA@webmail.df.eu>
Message-ID: <jom6h6$nol$1@dough.gmane.org>
Hi,
On 2012-05-12 15:28:11 +0000, martin at v.loewis.de said:
>> All commits are available in pull request separately.
>
> This is not sufficient, is it? If I want to accept change 1 and change 3,
> and reject change 2, how can I pull change 3 without also integrating change
> 2?
I see your point, but this is technically possible with transplant:
http://mercurial.selenic.com/wiki/TransplantExtension
Regards
Kai
From martin at v.loewis.de Sat May 12 21:25:13 2012
From: martin at v.loewis.de (martin at v.loewis.de)
Date: Sat, 12 May 2012 21:25:13 +0200
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <jom6h6$nol$1@dough.gmane.org>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
<CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
<CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
<20120512172811.Horde.3dUEP9jz9kRProGL2w6wkFA@webmail.df.eu>
<jom6h6$nol$1@dough.gmane.org>
Message-ID: <20120512212513.Horde.BWchDqGZi1VPrrkZFSuQV7A@webmail.df.eu>
> I see your point, but this is technically possible with transplant:
>
> http://mercurial.selenic.com/wiki/TransplantExtension
I see. The page points to using the graft command; I'll try it out.
Thanks,
Martin
From techtonik at gmail.com Sun May 13 11:02:20 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Sun, 13 May 2012 12:02:20 +0300
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAOoSJ_okuLpMRWShQurfJGAKWCkpmwVJjv0QaGh8NjOj2mEnBw@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+i2PefUTqdwyQT_UAZDyASJR9OtocPQuj0w0gzYexJ0w@mail.gmail.com>
<CAOoSJ_q3O_zpAQdSay1PmnakxRFeVGXw0k+WWh6RPOy93LLo8Q@mail.gmail.com>
<CAPkN8xJnxLGMfwSEgqFkheL6R8E057DSr+Y8=iH5FX_VAw7fpg@mail.gmail.com>
<CAOoSJ_okuLpMRWShQurfJGAKWCkpmwVJjv0QaGh8NjOj2mEnBw@mail.gmail.com>
Message-ID: <CAPkN8xKiCLEUwRrP7+hMvYU32Wm4kK2ovV_2Nyn0KWTwQ6F=FA@mail.gmail.com>
On Sat, May 12, 2012 at 6:24 PM, Daniel Greenfeld <pydanny at gmail.com> wrote:
>
> Also, the pattern I described to you fits very well within the
> beautiful promise of DVCS. The cleaner branching and merging of DVCS
> makes this sort of approach wonderful for all parties involved. Rather
> than giant, monolithic pull requests with lots of tiny commits, they
> get very easy to integrate pull requests.
With all respect to abstract theories I can't immediately see how it
applies to Mercurial in this particular case.
> Smaller, atomic pieces are much easier to handle then larger
> multi-task components. Isn't that the promise of OOP and functional
> programming? :-)
The contribution process is two fold. If maintainers are too picky
about bells and whistles surrounding the submitted patches (as I do
too) you can expect a significant drop in amount of people who want to
submit those patches. That's one of the reasons some project have a
lot of contributors and other are not.
> On Sat, May 12, 2012 at 8:09 AM, anatoly techtonik <techtonik at gmail.com> wrote:
>> Hi Daniel,
>>
>> You're request and proposed action would be nice if it used Mercurial,
>> but it uses Git + GitHub and have
>> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-inabsolutely
>> no idea how to apply it to Mercurial + Bitbucket. If I understand you
>> correctly for every 7 commits in queue I need to make a separate clone
>> and commit it separately. That's far from the that beautiful promise
>> DVCS made. =)
>>
>> All commits are available in pull request separately. If you take
>> another look at
>> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
>> you'll see there is an ongoing discussion over a questionable commit
>> with Martin. Feel free to comment on any revision. I can rework them
>> one by one on request if they are taking too much time to review.
>>
>> Your wish is valid and well understood, but for specific big features.
>> For a series of small clean up changes such as this one this places a
>> more constrain on the person submitting changes. So unless there is a
>> comment that code is too complicated, I'd prefer to save this extra
>> time to polishing other aspects.
>>
>> There are also 4 more commits in my copy waiting for this review to
>> complete, which I deliberately doesn't add to this request to
>>
>> On Sat, May 12, 2012 at 4:17 PM, Daniel Greenfeld <pydanny at gmail.com> wrote:
>>> Anatoly,
>>>
>>> Here's a major issues with your pull request:
>>>
>>> It's not atomic enough. PyPI is a massive effort so any pull request
>>> should be as small as possible. For example, "running without sentry
>>> client" should be just a single pull request. By combining multiple
>>> "actions" into one pull requests, you've made it harder for the PyPI
>>> authors to evaluate your work. Which means they'll be less inclined to
>>> review it.
>>>
>>> Break this up into 3 separate pull requests. It's easy to do with
>>> branching, and the maintainers of the project will appreciate you for
>>> it.
>>>
>>> In fact, one thing we did with Open Comparison
>>> (http://djangopackages.com, http://pyramid.opencomparison.org, and
>>> soon http://python.opencomparison.org) that as helped us a lot as
>>> maintainers is write a formal contributing document that spells this
>>> out and more. See:
>>>
>>> http://opencomparison.readthedocs.org/en/latest/contributing.html
>>>
>>> and in your case, specifically:
>>>
>>> http://opencomparison.readthedocs.org/en/latest/contributing.html#how-to-get-your-pull-request-accepted
>>>
>>> I suggest to Richard and Martin they adopt something similar. Or they
>>> can use our contributing rules in the same manner as Read the Docs:
>>>
>>> https://github.com/rtfd/readthedocs.org/blob/master/docs/contribute.rst
>>>
>>> Danny
>>>
>>> On Sat, May 12, 2012 at 2:21 AM, anatoly techtonik <techtonik at gmail.com> wrote:
>>>> On Wed, May 9, 2012 at 1:51 PM, anatoly techtonik <techtonik at gmail.com> wrote:
>>>>> Hi,
>>>>>
>>>>> Anybody to merge my changes from
>>>>> https://bitbucket.org/techtonik/pypi-techtonik ?
>>>>
>>>> Richard told me he is busy preparing for the PyCon AU and
>>>> administering ongoing PyGame, so no help here.
>>>> Martin told it will take time. So, anybody else at least to review and comment?
>>>>
>>>> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
>>>>
>>>> I also sent mail to PSF requesting a new `pydotorg` account on
>>>> Bitbucket, so that there will be a permanent home for official mirror
>>>> for PyPI that can be found using Bitbucket search along with other
>>>> open repositories for web to send pull requests to.
>>>>
>>>> In the meanwhile there few more clean up changes, one of which loosens
>>>> dependency on M2Crypto, which is not installable in virtualenv if you
>>>> don't have SWIG installed systemwide. Although it doesn't remove it
>>>> completely yet. The goal is to make pycrypto an optional alternative
>>>> for M2Crypto for an easy development.
>>>> _______________________________________________
>>>> Catalog-SIG mailing list
>>>> Catalog-SIG at python.org
>>>> http://mail.python.org/mailman/listinfo/catalog-sig
>>>
>>>
>>>
>>> --
>>> 'Knowledge is Power'
>>> Daniel Greenfeld
>>> http://pydanny.com
>
>
>
> --
> 'Knowledge is Power'
> Daniel Greenfeld
> http://pydanny.com
From tjreedy at udel.edu Fri May 18 21:15:33 2012
From: tjreedy at udel.edu (Terry Reedy)
Date: Fri, 18 May 2012 15:15:33 -0400
Subject: [Catalog-sig] Copyright footer at http://pypi.python.org/pypi still
ends in 2011
Message-ID: <jp6759$uv6$1@dough.gmane.org>
http://pypi.python.org/pypi
Copyright ? 1990-2011, Python Software Foundation
Time to update?
--
Terry Jan Reedy
From martin at v.loewis.de Fri May 18 23:09:46 2012
From: martin at v.loewis.de (martin at v.loewis.de)
Date: Fri, 18 May 2012 23:09:46 +0200
Subject: [Catalog-sig] Copyright footer at http://pypi.python.org/pypi
still ends in 2011
In-Reply-To: <jp6759$uv6$1@dough.gmane.org>
References: <jp6759$uv6$1@dough.gmane.org>
Message-ID: <20120518230946.Horde.PMVVcLuWis5PtrqaHuDRo6A@webmail.df.eu>
> Copyright ? 1990-2011, Python Software Foundation
>
> Time to update?
No time.
Martin
From alexis at notmyidea.org Wed May 23 17:58:15 2012
From: alexis at notmyidea.org (=?ISO-8859-1?Q?Alexis_M=E9taireau?=)
Date: Wed, 23 May 2012 17:58:15 +0200
Subject: [Catalog-sig] Distinguishing PEP 345 distributions from old ones.
Message-ID: <4FBD0917.9000701@notmyidea.org>
Heya folks,
Do you know if there are any ways to distinguish PEP 345 based
distributions from other ones (distutils1 or setuptools) , when hitting
PyPI?
That could be useful to have a specific record in what's returned by
PyPI so we are able to decide what to do with them from there.
Any idea? If that's not something already available, any concerns about
a possible implementation?
-- Alexis
From tarek at ziade.org Wed May 23 18:41:18 2012
From: tarek at ziade.org (=?ISO-8859-1?Q?Tarek_Ziad=E9?=)
Date: Wed, 23 May 2012 18:41:18 +0200
Subject: [Catalog-sig] Distinguishing PEP 345 distributions from old
ones.
In-Reply-To: <4FBD0917.9000701@notmyidea.org>
References: <4FBD0917.9000701@notmyidea.org>
Message-ID: <4FBD132E.3030402@ziade.org>
On 5/23/12 5:58 PM, Alexis M?taireau wrote:
> Heya folks,
>
> Do you know if there are any ways to distinguish PEP 345 based
> distributions from other ones (distutils1 or setuptools) , when
> hitting PyPI?
>
> That could be useful to have a specific record in what's returned by
> PyPI so we are able to decide what to do with them from there.
>
> Any idea? If that's not something already available, any concerns
> about a possible implementation?
the metadata version, which is 1.2
>
> -- Alexis
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig
From techtonik at gmail.com Wed May 23 23:30:08 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Thu, 24 May 2012 00:30:08 +0300
Subject: [Catalog-sig] Fwd: [PythonInfo Wiki] Update of "CheeseShop" by
BarryWarsaw
In-Reply-To: <20120523202205.27855.81163@dinsdale.python.org>
References: <20120523202205.27855.81163@dinsdale.python.org>
Message-ID: <CAPkN8xLN8c=m3J+f6AHSnNSNZNdt_JBkJhaB55orzgWcu7W0VQ@mail.gmail.com>
Can we still have an 'official' repostitory under the 'pydotorg' name
on BitBucket, so that PyPI won't look like a personal project?
--
anatoly t.
---------- Forwarded message ----------
From: python.org wiki <wiki at python.org>
Date: Wed, May 23, 2012 at 11:22 PM
Subject: [PythonInfo Wiki] Update of "CheeseShop" by BarryWarsaw
To: "python.org wiki" <wiki at python.org>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "PythonInfo
Wiki" for change notification.
The "CheeseShop" page has been changed by BarryWarsaw:
http://wiki.python.org/moin/CheeseShop?action=diff&rev1=7&rev2=8
? * PyPiJson describes JSON interface to access PyPI from applications
? * CheeseShopXmlRpc describes XML-RPC interface to access PyPI from
applications
? * CheeseShopDev contains all necessary information to help PyPI get better
-
+ ?* [[https://bitbucket.org/loewis/pypi|PyPI source on Bitbucket]]
? * PyPiImplementations page lists alternative implementations of
Python package catalogs
?----
?CategoryDevelopmentProcess
From noah at coderanger.net Wed May 23 23:33:34 2012
From: noah at coderanger.net (Noah Kantrowitz)
Date: Wed, 23 May 2012 14:33:34 -0700
Subject: [Catalog-sig] Fwd: [PythonInfo Wiki] Update of "CheeseShop" by
BarryWarsaw
In-Reply-To: <CAPkN8xLN8c=m3J+f6AHSnNSNZNdt_JBkJhaB55orzgWcu7W0VQ@mail.gmail.com>
References: <20120523202205.27855.81163@dinsdale.python.org>
<CAPkN8xLN8c=m3J+f6AHSnNSNZNdt_JBkJhaB55orzgWcu7W0VQ@mail.gmail.com>
Message-ID: <BAFE1451-A38F-491E-BBA6-1C2E116EB0ED@coderanger.net>
This is not a priority for the Catalog-SIG at this time. Thank you for your input.
--Noah
On May 23, 2012, at 2:30 PM, anatoly techtonik wrote:
> Can we still have an 'official' repostitory under the 'pydotorg' name
> on BitBucket, so that PyPI won't look like a personal project?
> --
> anatoly t.
>
>
>
> ---------- Forwarded message ----------
> From: python.org wiki <wiki at python.org>
> Date: Wed, May 23, 2012 at 11:22 PM
> Subject: [PythonInfo Wiki] Update of "CheeseShop" by BarryWarsaw
> To: "python.org wiki" <wiki at python.org>
>
>
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "PythonInfo
> Wiki" for change notification.
>
> The "CheeseShop" page has been changed by BarryWarsaw:
> http://wiki.python.org/moin/CheeseShop?action=diff&rev1=7&rev2=8
>
> * PyPiJson describes JSON interface to access PyPI from applications
> * CheeseShopXmlRpc describes XML-RPC interface to access PyPI from
> applications
> * CheeseShopDev contains all necessary information to help PyPI get better
> -
> + * [[https://bitbucket.org/loewis/pypi|PyPI source on Bitbucket]]
> * PyPiImplementations page lists alternative implementations of
> Python package catalogs
> ----
> CategoryDevelopmentProcess
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20120523/f7173002/attachment.pgp>
From techtonik at gmail.com Thu May 24 09:24:54 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Thu, 24 May 2012 10:24:54 +0300
Subject: [Catalog-sig] Fwd: [PythonInfo Wiki] Update of "CheeseShop" by
BarryWarsaw
In-Reply-To: <BAFE1451-A38F-491E-BBA6-1C2E116EB0ED@coderanger.net>
References: <20120523202205.27855.81163@dinsdale.python.org>
<CAPkN8xLN8c=m3J+f6AHSnNSNZNdt_JBkJhaB55orzgWcu7W0VQ@mail.gmail.com>
<BAFE1451-A38F-491E-BBA6-1C2E116EB0ED@coderanger.net>
Message-ID: <CAPkN8xLHePCir-EbY2B7ZVfgQBKsdWWgZooQbMuxXz1MxaxTuQ@mail.gmail.com>
What is the priority to catalog-sig at this time?
My pull request to PyPI is hanging there for two weeks already with
nobody except Martin even to comment on it. And Martin is busy.
https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
PyPI definitely needs more committers. For me it's the top priority
right now, or there will be -1 contributor soon. =)
--
anatoly t.
On Thu, May 24, 2012 at 12:33 AM, Noah Kantrowitz <noah at coderanger.net> wrote:
> This is not a priority for the Catalog-SIG at this time. Thank you for your input.
>
> --Noah
>
> On May 23, 2012, at 2:30 PM, anatoly techtonik wrote:
>
>> Can we still have an 'official' repostitory under the 'pydotorg' name
>> on BitBucket, so that PyPI won't look like a personal project?
>> --
>> anatoly t.
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: python.org wiki <wiki at python.org>
>> Date: Wed, May 23, 2012 at 11:22 PM
>> Subject: [PythonInfo Wiki] Update of "CheeseShop" by BarryWarsaw
>> To: "python.org wiki" <wiki at python.org>
>>
>>
>> Dear Wiki user,
>>
>> You have subscribed to a wiki page or wiki category on "PythonInfo
>> Wiki" for change notification.
>>
>> The "CheeseShop" page has been changed by BarryWarsaw:
>> http://wiki.python.org/moin/CheeseShop?action=diff&rev1=7&rev2=8
>>
>> ? * PyPiJson describes JSON interface to access PyPI from applications
>> ? * CheeseShopXmlRpc describes XML-RPC interface to access PyPI from
>> applications
>> ? * CheeseShopDev contains all necessary information to help PyPI get better
>> -
>> + ?* [[https://bitbucket.org/loewis/pypi|PyPI source on Bitbucket]]
>> ? * PyPiImplementations page lists alternative implementations of
>> Python package catalogs
>> ?----
>> ?CategoryDevelopmentProcess
>> _______________________________________________
>> Catalog-SIG mailing list
>> Catalog-SIG at python.org
>> http://mail.python.org/mailman/listinfo/catalog-sig
>
From donald.stufft at gmail.com Thu May 24 14:12:20 2012
From: donald.stufft at gmail.com (Donald Stufft)
Date: Thu, 24 May 2012 08:12:20 -0400
Subject: [Catalog-sig] Fwd: [PythonInfo Wiki] Update of "CheeseShop" by
BarryWarsaw
In-Reply-To: <CAPkN8xLHePCir-EbY2B7ZVfgQBKsdWWgZooQbMuxXz1MxaxTuQ@mail.gmail.com>
References: <20120523202205.27855.81163@dinsdale.python.org>
<CAPkN8xLN8c=m3J+f6AHSnNSNZNdt_JBkJhaB55orzgWcu7W0VQ@mail.gmail.com>
<BAFE1451-A38F-491E-BBA6-1C2E116EB0ED@coderanger.net>
<CAPkN8xLHePCir-EbY2B7ZVfgQBKsdWWgZooQbMuxXz1MxaxTuQ@mail.gmail.com>
Message-ID: <F8EE710C9F0F40D1962D4263F7BDF342@gmail.com>
I doubt the username is the reasoning for the pull request hanging, it's most likely
the amount of time that the people involved have currently.
On Thursday, May 24, 2012 at 3:24 AM, anatoly techtonik wrote:
> What is the priority to catalog-sig at this time?
>
> My pull request to PyPI is hanging there for two weeks already with
> nobody except Martin even to comment on it. And Martin is busy.
> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
>
> PyPI definitely needs more committers. For me it's the top priority
> right now, or there will be -1 contributor soon. =)
> --
> anatoly t.
>
>
> On Thu, May 24, 2012 at 12:33 AM, Noah Kantrowitz <noah at coderanger.net (mailto:noah at coderanger.net)> wrote:
> > This is not a priority for the Catalog-SIG at this time. Thank you for your input.
> >
> > --Noah
> >
> > On May 23, 2012, at 2:30 PM, anatoly techtonik wrote:
> >
> > > Can we still have an 'official' repostitory under the 'pydotorg' name
> > > on BitBucket, so that PyPI won't look like a personal project?
> > > --
> > > anatoly t.
> > >
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: python.org wiki <wiki at python.org (mailto:wiki at python.org)>
> > > Date: Wed, May 23, 2012 at 11:22 PM
> > > Subject: [PythonInfo Wiki] Update of "CheeseShop" by BarryWarsaw
> > > To: "python.org wiki" <wiki at python.org (mailto:wiki at python.org)>
> > >
> > >
> > > Dear Wiki user,
> > >
> > > You have subscribed to a wiki page or wiki category on "PythonInfo
> > > Wiki" for change notification.
> > >
> > > The "CheeseShop" page has been changed by BarryWarsaw:
> > > http://wiki.python.org/moin/CheeseShop?action=diff&rev1=7&rev2=8
> > >
> > > * PyPiJson describes JSON interface to access PyPI from applications
> > > * CheeseShopXmlRpc describes XML-RPC interface to access PyPI from
> > > applications
> > > * CheeseShopDev contains all necessary information to help PyPI get better
> > > -
> > > + * [[https://bitbucket.org/loewis/pypi|PyPI source on Bitbucket]]
> > > * PyPiImplementations page lists alternative implementations of
> > > Python package catalogs
> > > ----
> > > CategoryDevelopmentProcess
> > > _______________________________________________
> > > Catalog-SIG mailing list
> > > Catalog-SIG at python.org (mailto:Catalog-SIG at python.org)
> > > http://mail.python.org/mailman/listinfo/catalog-sig
> > >
> >
> >
>
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org (mailto:Catalog-SIG at python.org)
> http://mail.python.org/mailman/listinfo/catalog-sig
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20120524/76a305fd/attachment.html>
From alexis at notmyidea.org Thu May 24 15:07:20 2012
From: alexis at notmyidea.org (=?UTF-8?B?QWxleGlzIE3DqXRhaXJlYXU=?=)
Date: Thu, 24 May 2012 15:07:20 +0200
Subject: [Catalog-sig] Distinguishing PEP 345 distributions from old
ones.
In-Reply-To: <4FBD132E.3030402@ziade.org>
References: <4FBD0917.9000701@notmyidea.org> <4FBD132E.3030402@ziade.org>
Message-ID: <4FBE3288.7060105@notmyidea.org>
> the metadata version, which is 1.2
That doesn't seem to be available in PyPI direclty, nor via the XML-RPC
interface: http://pypi.python.org/pypi/pelican/json
>>> import xmlrpclib
>>> client = xmlrpclib.ServerProxy('http://pypi.python.org/pypi')
>>> client.release_data('Pelican', '2.8.1')/keys()
['maintainer',
'docs_url',
'requires_python',
'maintainer_email',
'cheesecake_code_kwalitee_id',
'keywords',
'package_url',
'author',
'author_email',
'download_url',
'platform',
'version',
'cheesecake_documentation_id',
'_pypi_hidden',
'description',
'release_url',
'_pypi_ordering',
'classifiers',
'name',
'bugtrack_url',
'license',
'summary',
'home_page',
'stable_version',
'cheesecake_installability_id']
However, this is present in the uploaded distributions, in the
generated PKG-INFO when creating the sdist. Any reason this information
is not available without having to download the sdist?
From tarek at ziade.org Thu May 24 15:26:00 2012
From: tarek at ziade.org (=?UTF-8?B?VGFyZWsgWmlhZMOp?=)
Date: Thu, 24 May 2012 15:26:00 +0200
Subject: [Catalog-sig] Distinguishing PEP 345 distributions from old
ones.
In-Reply-To: <4FBE3288.7060105@notmyidea.org>
References: <4FBD0917.9000701@notmyidea.org> <4FBD132E.3030402@ziade.org>
<4FBE3288.7060105@notmyidea.org>
Message-ID: <4FBE36E8.8000108@ziade.org>
On 5/24/12 3:07 PM, Alexis M?taireau wrote:
>> the metadata version, which is 1.2
>
> That doesn't seem to be available in PyPI direclty, nor via the
> XML-RPC interface: http://pypi.python.org/pypi/pelican/json
>
>>>> import xmlrpclib
>>>> client = xmlrpclib.ServerProxy('http://pypi.python.org/pypi')
>>>> client.release_data('Pelican', '2.8.1')/keys()
Weird, I could have swore it was in there. We should add the
'metadata_version' key.
In the interim you can detect when it's a 1.2 because it has specific
fields , by loading the metadata in a packaging.metadata.Metadata instance
and ask it to detect the version.
You can try with http://pypi.python.org/pypi/gitbuster/
(notice the UI that lists the dependencies)
Also, as discussed with Richard we said we would publish 'setup.cfg' in
PyPI. So that will be another way
Cheers
Tarek
From alexis at notmyidea.org Thu May 24 15:49:26 2012
From: alexis at notmyidea.org (=?UTF-8?B?QWxleGlzIE3DqXRhaXJlYXU=?=)
Date: Thu, 24 May 2012 15:49:26 +0200
Subject: [Catalog-sig] Distinguishing PEP 345 distributions from old
ones.
In-Reply-To: <4FBE36E8.8000108@ziade.org>
References: <4FBD0917.9000701@notmyidea.org> <4FBD132E.3030402@ziade.org>
<4FBE3288.7060105@notmyidea.org> <4FBE36E8.8000108@ziade.org>
Message-ID: <4FBE3C66.9050200@notmyidea.org>
Le 24/05/2012 15:26, Tarek Ziad? a ?crit :
> On 5/24/12 3:07 PM, Alexis M?taireau wrote:
>>> the metadata version, which is 1.2
>>
>> That doesn't seem to be available in PyPI direclty, nor via the
>> XML-RPC interface: http://pypi.python.org/pypi/pelican/json
>>
>>>>> import xmlrpclib
>>>>> client = xmlrpclib.ServerProxy('http://pypi.python.org/pypi')
>>>>> client.release_data('Pelican', '2.8.1')/keys()
>
> Weird, I could have swore it was in there. We should add the
> 'metadata_version' key.
>
> In the interim you can detect when it's a 1.2 because it has specific
> fields , by loading the metadata in a packaging.metadata.Metadata
> instance
> and ask it to detect the version.
Oh, it seems that new distributions do have a "requires_dist" field, so
I can use this and determine if it's a PEP 345 dist or not from there.
Well, I could if I had the metadata fields there, but they aren't
present (PyPI doesn't do anything with the setup.py to get the metadata
related fields it seems).
Using packaging/distutils2.metadata.Metadata to guess the version of the
metadata is thus not working for me when getting this metadata from PyPI.
For instance:
>>> from distutils2.pypi import xmlrpc
>>> rel = xmlrpc.Client().get_metadata('gitbuster', '2.1b7')
>>> rel.metadata['metadata-version']
UNKNOWN
>>> rel.metadata['requires-dist']
['gfbi_core (==0.5b6)', 'argparse']
So I guess I will rely on having something in the "requires-dist" or not
to determine the version of the metadata for now..
From tarek at ziade.org Thu May 24 15:55:08 2012
From: tarek at ziade.org (=?UTF-8?B?VGFyZWsgWmlhZMOp?=)
Date: Thu, 24 May 2012 15:55:08 +0200
Subject: [Catalog-sig] Distinguishing PEP 345 distributions from old
ones.
In-Reply-To: <4FBE3C66.9050200@notmyidea.org>
References: <4FBD0917.9000701@notmyidea.org> <4FBD132E.3030402@ziade.org>
<4FBE3288.7060105@notmyidea.org> <4FBE36E8.8000108@ziade.org>
<4FBE3C66.9050200@notmyidea.org>
Message-ID: <4FBE3DBC.2000605@ziade.org>
On 5/24/12 3:49 PM, Alexis M?taireau wrote:
> Le 24/05/2012 15:26, Tarek Ziad? a ?crit :
>> On 5/24/12 3:07 PM, Alexis M?taireau wrote:
>>>> the metadata version, which is 1.2
>>>
>>> That doesn't seem to be available in PyPI direclty, nor via the
>>> XML-RPC interface: http://pypi.python.org/pypi/pelican/json
>>>
>>>>>> import xmlrpclib
>>>>>> client = xmlrpclib.ServerProxy('http://pypi.python.org/pypi')
>>>>>> client.release_data('Pelican', '2.8.1')/keys()
>>
>> Weird, I could have swore it was in there. We should add the
>> 'metadata_version' key.
>>
>> In the interim you can detect when it's a 1.2 because it has specific
>> fields , by loading the metadata in a packaging.metadata.Metadata
>> instance
>> and ask it to detect the version.
> Oh, it seems that new distributions do have a "requires_dist" field,
> so I can use this and determine if it's a PEP 345 dist or not from there.
>
> Well, I could if I had the metadata fields there, but they aren't
> present (PyPI doesn't do anything with the setup.py to get the
> metadata related fields it seems).
that's done on client side when you call "register", it sends the
metadata as a dict
see
http://hg.python.org/distutils2/file/0291648eb2b2/distutils2/command/register.py#l220
then PyPI just stores them into a SQL table - so the values that are
kept are the one defined by the sql schema since it does not store a blob.
What we need to add is a feature at PyPI that extracts setup.cfg from
the release, and make it available at an url
so if you have it you know it's the new standard,
>
> Using packaging/distutils2.metadata.Metadata to guess the version of
> the metadata is thus not working for me when getting this metadata
> from PyPI.
>
> For instance:
>
> >>> from distutils2.pypi import xmlrpc
> >>> rel = xmlrpc.Client().get_metadata('gitbuster', '2.1b7')
> >>> rel.metadata['metadata-version']
> UNKNOWN
> >>> rel.metadata['requires-dist']
> ['gfbi_core (==0.5b6)', 'argparse']
>
> So I guess I will rely on having something in the "requires-dist" or
> not to determine the version of the metadata for now..
Yes but if the project does not have any dependencies it won't work.
From techtonik at gmail.com Thu May 24 17:28:39 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Thu, 24 May 2012 18:28:39 +0300
Subject: [Catalog-sig] Fwd: [PythonInfo Wiki] Update of "CheeseShop" by
BarryWarsaw
In-Reply-To: <F8EE710C9F0F40D1962D4263F7BDF342@gmail.com>
References: <20120523202205.27855.81163@dinsdale.python.org>
<CAPkN8xLN8c=m3J+f6AHSnNSNZNdt_JBkJhaB55orzgWcu7W0VQ@mail.gmail.com>
<BAFE1451-A38F-491E-BBA6-1C2E116EB0ED@coderanger.net>
<CAPkN8xLHePCir-EbY2B7ZVfgQBKsdWWgZooQbMuxXz1MxaxTuQ@mail.gmail.com>
<F8EE710C9F0F40D1962D4263F7BDF342@gmail.com>
Message-ID: <CAPkN8xLBD5fZF2Ec7t-vAR9+8Jn4c592gX5Rwoby+94r9NUaJg@mail.gmail.com>
Right. More people - more time.
count(people(t)) = math.floor( visibility(project) *
interest(person) / entrybarrier(project) * t )
My commits are reducing entrybarrier() component.
Moving to `pydotorg` group will increase visibility(), because it will
likely contains the mirror for www.python.org, and link to it can be
placed in the footer.
--
anatoly t.
On Thu, May 24, 2012 at 3:12 PM, Donald Stufft <donald.stufft at gmail.com> wrote:
> I doubt the username is the reasoning for the pull request hanging, it's
> most likely
> the amount of time that the people involved have currently.
>
> On Thursday, May 24, 2012 at 3:24 AM, anatoly techtonik wrote:
>
> What is the priority to catalog-sig at this time?
>
> My pull request to PyPI is hanging there for two weeks already with
> nobody except Martin even to comment on it. And Martin is busy.
> https://bitbucket.org/loewis/pypi/pull-request/1/fix-imports-add-logging-to-console-in
>
> PyPI definitely needs more committers. For me it's the top priority
> right now, or there will be -1 contributor soon. =)
> --
> anatoly t.
>
>
> On Thu, May 24, 2012 at 12:33 AM, Noah Kantrowitz <noah at coderanger.net>
> wrote:
>
> This is not a priority for the Catalog-SIG at this time. Thank you for your
> input.
>
> --Noah
>
> On May 23, 2012, at 2:30 PM, anatoly techtonik wrote:
>
> Can we still have an 'official' repostitory under the 'pydotorg' name
> on BitBucket, so that PyPI won't look like a personal project?
> --
> anatoly t.
>
>
>
> ---------- Forwarded message ----------
> From: python.org wiki <wiki at python.org>
> Date: Wed, May 23, 2012 at 11:22 PM
> Subject: [PythonInfo Wiki] Update of "CheeseShop" by BarryWarsaw
> To: "python.org wiki" <wiki at python.org>
>
>
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "PythonInfo
> Wiki" for change notification.
>
> The "CheeseShop" page has been changed by BarryWarsaw:
> http://wiki.python.org/moin/CheeseShop?action=diff&rev1=7&rev2=8
>
> ? * PyPiJson describes JSON interface to access PyPI from applications
> ? * CheeseShopXmlRpc describes XML-RPC interface to access PyPI from
> applications
> ? * CheeseShopDev contains all necessary information to help PyPI get better
> -
> + ?* [[https://bitbucket.org/loewis/pypi|PyPI source on Bitbucket]]
> ? * PyPiImplementations page lists alternative implementations of
> Python package catalogs
> ?----
> ?CategoryDevelopmentProcess
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig
>
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig
>
>
From noah at coderanger.net Mon May 28 09:43:34 2012
From: noah at coderanger.net (Noah Kantrowitz)
Date: Mon, 28 May 2012 00:43:34 -0700
Subject: [Catalog-sig] New hostname for SSH uploads
Message-ID: <E4C61C83-3546-4439-8AE2-9F9F1FBEFF5D@coderanger.net>
Can someone with commit access please update the pypissh package to use the hostname "ssh.pypi.python.org". For now this points to the same place as "pypi.python.org", but this is in advance of moving the main "pypi.python.org" hostname to an external CDN. Once that transition is complete, the old hostname will no longer be accessible for SSH uploads. What do people think is a reasonable deprecation timeline for this? To pull numbers out of nowhere, three months seems like a reasonable threshold. Given that the latest version of the package has been out for over a year and has only been downloaded 500 times, a much shorter timeline might also be reasonable given the low impact on the user base.
--Noah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20120528/53cb6c91/attachment.pgp>
From techtonik at gmail.com Mon May 28 13:29:27 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Mon, 28 May 2012 14:29:27 +0300
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
Message-ID: <CAPkN8x+pMdCK_u-HknR2=wsK+DwKg62798O9DR0JBFqpBQakXA@mail.gmail.com>
On Wed, May 9, 2012 at 1:51 PM, anatoly techtonik <techtonik at gmail.com> wrote:
>
> Anybody to merge my changes from
> https://bitbucket.org/techtonik/pypi-techtonik ?
Anybody?
--
anatoly t.
From aclark at aclark.net Mon May 28 21:02:57 2012
From: aclark at aclark.net (Alex Clark)
Date: Mon, 28 May 2012 15:02:57 -0400
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <CAPkN8x+pMdCK_u-HknR2=wsK+DwKg62798O9DR0JBFqpBQakXA@mail.gmail.com>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+pMdCK_u-HknR2=wsK+DwKg62798O9DR0JBFqpBQakXA@mail.gmail.com>
Message-ID: <jq0i53$o31$1@dough.gmane.org>
On 5/28/12 7:29 AM, anatoly techtonik wrote:
> On Wed, May 9, 2012 at 1:51 PM, anatoly techtonik<techtonik at gmail.com> wrote:
>>
>> Anybody to merge my changes from
>> https://bitbucket.org/techtonik/pypi-techtonik ?
>
> Anybody?
I believe the culture of open source is such that one needs to make
contributions, then back away and let whatever else is going to happen
happen (vs. continuing to alert folks of what they are already aware of,
that you have a pull request waiting.) That said, there is of course the
occasional need to remind folks of things, but I don't think this is one
of those cases.
TL;DR I think everyone on this list is now aware that you have a pull
request waiting, so there is no need for a reminder at this time. (In
fact I'd argue that too frequent reminders may have the opposite effect
of the desired effect.)
Alex
> --
> anatoly t.
--
Alex Clark ? http://pythonpackages.com
From martin at v.loewis.de Mon May 28 22:28:11 2012
From: martin at v.loewis.de (martin at v.loewis.de)
Date: Mon, 28 May 2012 22:28:11 +0200
Subject: [Catalog-sig] PyPI pull request
In-Reply-To: <jq0i53$o31$1@dough.gmane.org>
References: <CAPkN8xJ+2C9Thp8J7BBg06kRpF+XF2CM89OBsmP4XsBi28kicg@mail.gmail.com>
<CAPkN8x+pMdCK_u-HknR2=wsK+DwKg62798O9DR0JBFqpBQakXA@mail.gmail.com>
<jq0i53$o31$1@dough.gmane.org>
Message-ID: <20120528222811.Horde.2IjeKNjz9kRPw9-bfyAVKWA@webmail.df.eu>
> TL;DR I think everyone on this list is now aware that you have a
> pull request waiting, so there is no need for a reminder at this
> time. (In fact I'd argue that too frequent reminders may have the
> opposite effect of the desired effect.)
I can certainly confirm that it has this very effect in this case.
Regards,
Martin
From aclark at aclark.net Tue May 29 17:30:10 2012
From: aclark at aclark.net (Alex Clark)
Date: Tue, 29 May 2012 11:30:10 -0400
Subject: [Catalog-sig] Basic auth broken on http://testpypi.python.org/pypi?
Message-ID: <jq2q22$jod$1@dough.gmane.org>
Hi,
Just trying to do some testing with: http://testpypi.python.org/pypi and
I can't login. Is basic auth supposed to work with my regular PyPI
account credentials, or is there some generic test credentials?
Alex
--
Alex Clark ? http://pythonpackages.com
From chris at simplistix.co.uk Tue May 29 20:26:17 2012
From: chris at simplistix.co.uk (Chris Withers)
Date: Tue, 29 May 2012 19:26:17 +0100
Subject: [Catalog-sig] is there a way to rename a package?
Message-ID: <4FC514C9.5030104@simplistix.co.uk>
Hi All,
Is there a way to rename a package on pypi?
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
From mal at egenix.com Tue May 29 20:49:46 2012
From: mal at egenix.com (M.-A. Lemburg)
Date: Tue, 29 May 2012 20:49:46 +0200
Subject: [Catalog-sig] is there a way to rename a package?
In-Reply-To: <4FC514C9.5030104@simplistix.co.uk>
References: <4FC514C9.5030104@simplistix.co.uk>
Message-ID: <4FC51A4A.8080903@egenix.com>
Chris Withers wrote:
> Hi All,
>
> Is there a way to rename a package on pypi?
I suppose this can be had by opening a ticket on the issue tracker
and asking nicely :-)
Other than that, I think there's only delete + recreate with different
name. The latter may actually be the better option in terms of being
able to sync the change across mirrors, since I don't think the mirror
protocol supports renaming.
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1, May 29 2012)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
________________________________________________________________________
2012-07-17: Python Meeting Duesseldorf ... 49 days to go
2012-07-02: EuroPython 2012, Florence, Italy ... 34 days to go
2012-05-16: Released eGenix pyOpenSSL 0.13 ... http://egenix.com/go29
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
http://www.egenix.com/company/contact/
From martin at v.loewis.de Tue May 29 23:35:45 2012
From: martin at v.loewis.de (martin at v.loewis.de)
Date: Tue, 29 May 2012 23:35:45 +0200
Subject: [Catalog-sig] is there a way to rename a package?
In-Reply-To: <4FC514C9.5030104@simplistix.co.uk>
References: <4FC514C9.5030104@simplistix.co.uk>
Message-ID: <20120529233545.Horde.3k2hUKGZi1VPxUExduY2ROA@webmail.df.eu>
> Is there a way to rename a package on pypi?
Yes, submit a support request to the PyPI bug tracker.
Note that this may be less useful than you might think:
any files uploaded cannot be renamed (but they'll move
to the new package's directory).
Regards,
Martin
From martin at v.loewis.de Tue May 29 23:57:14 2012
From: martin at v.loewis.de (martin at v.loewis.de)
Date: Tue, 29 May 2012 23:57:14 +0200
Subject: [Catalog-sig] is there a way to rename a package?
In-Reply-To: <4FC51A4A.8080903@egenix.com>
References: <4FC514C9.5030104@simplistix.co.uk> <4FC51A4A.8080903@egenix.com>
Message-ID: <20120529235714.Horde.ETdHLqGZi1VPxUY6qPL2aYA@webmail.df.eu>
> Other than that, I think there's only delete + recreate with different
> name. The latter may actually be the better option in terms of being
> able to sync the change across mirrors, since I don't think the mirror
> protocol supports renaming.
It actually does: the mirrors will notice notice appearance of the
new package, and will re-download all files. In theory, there should be
a bug where they keep the old package as well, but I wasn't able to
observe that problem in practice.
Regards,
Martin
From donald.stufft at gmail.com Wed May 30 03:43:01 2012
From: donald.stufft at gmail.com (Donald Stufft)
Date: Tue, 29 May 2012 21:43:01 -0400
Subject: [Catalog-sig] is there a way to rename a package?
In-Reply-To: <20120529235714.Horde.ETdHLqGZi1VPxUY6qPL2aYA@webmail.df.eu>
References: <4FC514C9.5030104@simplistix.co.uk> <4FC51A4A.8080903@egenix.com>
<20120529235714.Horde.ETdHLqGZi1VPxUY6qPL2aYA@webmail.df.eu>
Message-ID: <3B04117C2E4F405AA27A81147E105488@gmail.com>
Does it generate a changelog event?
On Tuesday, May 29, 2012 at 5:57 PM, martin at v.loewis.de wrote:
> > Other than that, I think there's only delete + recreate with different
> > name. The latter may actually be the better option in terms of being
> > able to sync the change across mirrors, since I don't think the mirror
> > protocol supports renaming.
> >
>
>
> It actually does: the mirrors will notice notice appearance of the
> new package, and will re-download all files. In theory, there should be
> a bug where they keep the old package as well, but I wasn't able to
> observe that problem in practice.
>
> Regards,
> Martin
>
>
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org (mailto:Catalog-SIG at python.org)
> http://mail.python.org/mailman/listinfo/catalog-sig
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20120529/cbe11f12/attachment.html>
From richard at python.org Wed May 30 05:13:10 2012
From: richard at python.org (Richard Jones)
Date: Wed, 30 May 2012 13:13:10 +1000
Subject: [Catalog-sig] Basic auth broken on
http://testpypi.python.org/pypi?
In-Reply-To: <jq2q22$jod$1@dough.gmane.org>
References: <jq2q22$jod$1@dough.gmane.org>
Message-ID: <CAHrZfZBgvWJN7KzM48xyOm=Qk1EKePtSutV5DLLr3P4hz1DYLg@mail.gmail.com>
On 30 May 2012 01:30, Alex Clark <aclark at aclark.net> wrote:
> Just trying to do some testing with: http://testpypi.python.org/pypi and I
> can't login. Is basic auth supposed to work with my regular PyPI account
> credentials, or is there some generic test credentials?
The user database is completely separate. You'll need to register on testpypi.
Richard
From martin at v.loewis.de Wed May 30 07:42:28 2012
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 30 May 2012 07:42:28 +0200
Subject: [Catalog-sig] Basic auth broken on
http://testpypi.python.org/pypi?
In-Reply-To: <CAHrZfZBgvWJN7KzM48xyOm=Qk1EKePtSutV5DLLr3P4hz1DYLg@mail.gmail.com>
References: <jq2q22$jod$1@dough.gmane.org>
<CAHrZfZBgvWJN7KzM48xyOm=Qk1EKePtSutV5DLLr3P4hz1DYLg@mail.gmail.com>
Message-ID: <4FC5B344.8050906@v.loewis.de>
On 30.05.2012 05:13, Richard Jones wrote:
> On 30 May 2012 01:30, Alex Clark<aclark at aclark.net> wrote:
>> Just trying to do some testing with: http://testpypi.python.org/pypi and I
>> can't login. Is basic auth supposed to work with my regular PyPI account
>> credentials, or is there some generic test credentials?
>
> The user database is completely separate. You'll need to register on testpypi.
In addition, the database might be reset at any time, so you'll have to
re-register if you find that your password doesn't work anymore.
Regards,
Martin
From martin at v.loewis.de Wed May 30 07:46:31 2012
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Wed, 30 May 2012 07:46:31 +0200
Subject: [Catalog-sig] is there a way to rename a package?
In-Reply-To: <3B04117C2E4F405AA27A81147E105488@gmail.com>
References: <4FC514C9.5030104@simplistix.co.uk> <4FC51A4A.8080903@egenix.com>
<20120529235714.Horde.ETdHLqGZi1VPxUY6qPL2aYA@webmail.df.eu>
<3B04117C2E4F405AA27A81147E105488@gmail.com>
Message-ID: <4FC5B437.3080702@v.loewis.de>
On 30.05.2012 03:43, Donald Stufft wrote:
> Does it generate a changelog event?
Yes, for the new package, with an action of "rename from <old package>".
I'm considering to also add a changelog item "renamed to" for the old
package. I'm somewhat puzzled why the renamed packages are not available
on the mirrors, despite there being no such record yet. FWIW, the
renamed packages are
name | action | submitted_date
------------------+-------------------------------+---------------------
feedparser | rename from FeedParser | 2011-02-20 22:34:47
py4j | rename from Py4J | 2011-06-02 18:59:05
translate-toolkit | rename from Translate Toolkit | 2012-05-11 11:18:28
pgulp | rename from pulp | 2009-01-17 13:53:05
python-nosexml | rename from nosexml | 2009-01-17 13:50:11
configobj | rename from ConfigObj | 2009-07-14 05:34:51
flufl.enum | rename from munepy | 2010-04-26 22:12:06
Flask-Mail | rename from flask-mail | 2010-07-26 08:31:11
Regards,
Martin
From alexis at notmyidea.org Wed May 30 10:13:52 2012
From: alexis at notmyidea.org (=?ISO-8859-1?Q?Alexis_M=E9taireau?=)
Date: Wed, 30 May 2012 10:13:52 +0200
Subject: [Catalog-sig] is there a way to rename a package?
In-Reply-To: <4FC514C9.5030104@simplistix.co.uk>
References: <4FC514C9.5030104@simplistix.co.uk>
Message-ID: <4FC5D6C0.5070509@notmyidea.org>
Le 29/05/2012 20:26, Chris Withers a ?crit :
> Is there a way to rename a package on pypi?
This answer will probably sound beside the point, but that's probably
worth noticing that renaming a distribution on PyPI can be a bad idea,
as for deletion of anything on the Index.
Please, ensure that no-one is using the distribution you want to rename.
If some users are using the distribution under its old name, then
releasing a new version of the distribution under the old name, with
documentation pointing to the new location seems a good way to have your
users not too upset too much.
Of course, if it was a simple typo in the name when uploading the
distribution, then fair enough, having a simple way to rename a
distribution sounds like a good idea.
Note to potential implementors of this feature in PyPI: please take
extra care of the rename mechanism so that it doesn't break for
end-users in weird ways. Having a distribution renamed might sound
straightforward, but probably isn't.
Alexis