Re: API for uploading packages to PyPI
anatoly techtonik <[email protected]> Sat, 23 Mar 2013 01:33:13 +0300
| Newsgroups | gmane.comp.python.catalog |
|---|---|
| Message-ID | <CAPkN8xLALTgZAFbWDyPKR9KqFaoTN5W9niR6hs-iztPy=Hm0LQ@mail.gmail.com> |
--===============0600901230== Content-Type: multipart/alternative; boundary=047d7b5d86d99bf54804d88b0b4e --047d7b5d86d99bf54804d88b0b4e Content-Type: text/plain; charset=UTF-8 On Fri, Mar 22, 2013 at 4:17 PM, M.-A. Lemburg <[email protected]> wrote: > On 22.03.2013 13:38, anatoly techtonik wrote: > > On Fri, Mar 22, 2013 at 3:26 PM, M.-A. Lemburg <[email protected]> wrote: > > > >> On 22.03.2013 13:20, anatoly techtonik wrote: > >>> On Fri, Mar 22, 2013 at 1:49 PM, M.-A. Lemburg <[email protected]> wrote: > >>>> Again: Please don't do this. > >>>> > >>> > >>> I think you're not against renaming pages, but against renaming without > >>> redirects. In fact, if MoinMoin could automatically insert #REDIRECT > >>> directives when a page is renamed, then there won't be any problem like > >>> this at all. I hope that pydotorg@ or infrastructure@ have this item > on > >>> their feature lists. > >> > >> You can add redirects from the page names you think are more > >> correct to the existing ones, but please don't rename the pages > >> themselves. > > > > > > You need to expand that, because I don't get it. Why do you want the > > canonical pages about PyPI JSON API to bear the name of PyPiJson? This > name > > is hard to synthesize if you want to type in directly into the URL > without > > waiting for the page to load to click a link or use search field. > > It's not about which name I want. It's about the name of the page > that was used to add content and which has been around long enough > to assume that others have linked to it. > > With the redirect from the new name to the existing one, > you get what you want and all others can continue to use > the existing name. All right. So it is the matter of using old name or the new name. But both names lead to the same page. So the point of conflict here is what should be the end name of this page. If you say that it is not about which name do you want, then say why this name should not be the name I want? I want canonical names for pages. Names that are consistent, which capitalization is easy to remember and reproduce, and I want that people linked to these names directly to avoid double redirects. --047d7b5d86d99bf54804d88b0b4e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">On Fri, Mar 22, 2013 at 4:17 PM, M.-A. Lemburg <span dir= =3D"ltr"><<a href=3D"mailto:[email protected]" target=3D"_blank">mal@egenix= .com</a>></span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmai= l_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e= x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl= e:solid;padding-left:1ex"> <div class=3D""><div class=3D"h5">On 22.03.2013 13:38, anatoly techtonik wr= ote:<br> > On Fri, Mar 22, 2013 at 3:26 PM, M.-A. Lemburg <<a href=3D"mailto:m= [email protected]">[email protected]</a>> wrote:<br> ><br> >> On 22.03.2013 13:20, anatoly techtonik wrote:<br> >>> On Fri, Mar 22, 2013 at 1:49 PM, M.-A. Lemburg <<a href=3D"= mailto:[email protected]">[email protected]</a>> wrote:<br> >>>> Again: Please don't do this.<br> >>>><br> >>><br> >>> I think you're not against renaming pages, but against ren= aming without<br> >>> redirects. In fact, if MoinMoin could automatically insert #RE= DIRECT<br> >>> directives when a page is renamed, then there won't be any= problem like<br> >>> this at all. I hope that pydotorg@ or infrastructure@ have thi= s item on<br> >>> their feature lists.<br> >><br> >> You can add redirects from the page names you think are more<br> >> correct to the existing ones, but please don't rename the page= s<br> >> themselves.<br> ><br> ><br> > You need to expand that, because I don't get it. Why do you want t= he<br> > canonical pages about PyPI JSON API to bear the name of PyPiJson? This= name<br> > is hard to synthesize if you want to type in directly into the URL wit= hout<br> > waiting for the page to load to click a link or use search field.<br> <br> </div></div>It's not about which name I want. It's about the name o= f the page<br> that was used to add content and which has been around long enough<br> to assume that others have linked to it.<br> <br> With the redirect from the new name to the existing one,<br> you get what you want and all others can continue to use<br> the existing name.</blockquote><div><br></div></div><div class=3D"gmail_quo= te">All right. So it is the matter of using old name or the new name. But b= oth</div><div class=3D"gmail_quote" style>names lead to the same page. So t= he point of conflict here is what should</div> <div class=3D"gmail_quote" style>be the end name of this page. If you say t= hat it is not about which name</div><div class=3D"gmail_quote" style>do you= want, then say why this name should not be the name I want?</div><div clas= s=3D"gmail_quote" style> <br></div><div class=3D"gmail_quote" style>I want canonical names for pages= . Names that are consistent, which</div><div class=3D"gmail_quote" style>ca= pitalization is easy to remember and reproduce, and I want that people</div= > <div class=3D"gmail_quote" style>linked to these names directly to avoid do= uble redirects.</div><div class=3D"gmail_quote"><br></div></div></div> --047d7b5d86d99bf54804d88b0b4e-- --===============0600901230== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig --===============0600901230==--