Mailman 3 June 2020 - Distutils-SIG

Who is approving PyPI size limit exceptions these days?
by Steve Dower 18 Jun '20

18 Jun '20

These issues seem to be awaiting approval: https://github.com/pypa/pypi-support/labels/limit%20request Most pressing (for me ;) ) is my colleagues at https://github.com/pypa/pypi-support/issues/457, who are already dealing with confused users not finding the packages they expect. Thanks, Steve

1 0

(no subject)
by Raregem Augustine 16 Jun '20

16 Jun '20

Hello! I have tried several times and it has not been working to install external packages in Python. I continue to get ERROR: Could not find a version that satisfies the requirement SomePackage (from versions: non) ERROR: No matching distribution found for SomePackage. Please, how can I fix this. Thank you.

2 1

Installing a module
by Rishi 16 Jun '20

16 Jun '20

2 1

Re: July 1 deadline for Mercurial repositories on Bitbucket
by Vinay Sajip 16 Jun '20

16 Jun '20

FYI distlib has moved to Git, while remaining on BitBucket. The move was made in January 2020. https://bitbucket.org/pypa/distlib/src/master/ Regards, Vinay Sajip On Tuesday, 16 June 2020, 03:45:52 BST, distutils-sig-request(a)python.org <distutils-sig-request(a)python.org> wrote: Send Distutils-SIG mailing list submissions to distutils-sig(a)python.org To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman3/lists/distutils-sig.python.org/ or, via email, send a message with subject or body 'help' to distutils-sig-request(a)python.org You can reach the person managing the list at distutils-sig-owner(a)python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Distutils-SIG digest..." Today's Topics: 1. July 1 deadline for Mercurial repositories on Bitbucket (Sumana Harihareswara) 2. Re: July 1 deadline for Mercurial repositories on Bitbucket (Cooper Lees) 3. Re: July 1 deadline for Mercurial repositories on Bitbucket (Sumana Harihareswara) 4. Re: July 1 deadline for Mercurial repositories on Bitbucket (Sumana Harihareswara) ---------------------------------------------------------------------- Date: Mon, 15 Jun 2020 17:29:42 -0400 From: Sumana Harihareswara <sh(a)changeset.nyc> Subject: [Distutils] July 1 deadline for Mercurial repositories on Bitbucket To: DistUtils mailing list <distutils-sig(a)python.org> Message-ID: <372de837-9aa7-f489-bb42-0d3077ad50a7(a)changeset.nyc> Content-Type: text/plain; charset=utf-8; format=flowed TL;DR: distlib_hg and bandersnatch, you have a July 1st deadline to switch to Git or move off Bitbucket. https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket "we've decided to remove Mercurial support from Bitbucket Cloud and its API." "Mercurial features and repositories will be officially removed from Bitbucket and its API on July 1, 2020." Most of https://bitbucket.org/pypa/ is Mercurial repos. Maintainers of those repositories need to switch them to Git or move them off Bitbucket by July 1st. distlib_hg and bandersnatch are the active Mercurial repos that most clearly need to switch or move. A few repos in bitbucket.org/pypa have explicit "moved to GitHub" notices on them. And I assume its pkg_resources , setuptools, import_resources, pylauncher, and bootstrap projects are now defunct, but it's probably worth archiving them somehow anyway, for historical reference. -- Sumana Harihareswara Changeset Consulting https://changeset.nyc ------------------------------ Date: Mon, 15 Jun 2020 14:34:02 -0700 From: Cooper Lees <me(a)cooperlees.com> Subject: [Distutils] Re: July 1 deadline for Mercurial repositories on Bitbucket To: Sumana Harihareswara <sh(a)changeset.nyc> Cc: DistUtils mailing list <distutils-sig(a)python.org> Message-ID: <A8E14546-4C8C-45EE-9458-473E5A3D5BF5(a)cooperlees.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_108E09A8-924C-4637-B2BF-854F5C6C3608" --Apple-Mail=_108E09A8-924C-4637-B2BF-854F5C6C3608 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Bandersnatch moved over 2 years ago and has been displaying the move on = the repository this whole time via the README.md. I just deleted it from BitBucket. As we have been for the last 2 years, = all bandersnatch action can be found here: = https://github.com/pypa/bandersnatch = <https://github.com/pypa/bandersnatch> Cooper > On Jun 15, 2020, at 2:29 PM, Sumana Harihareswara <sh(a)changeset.nyc> = wrote: >=20 > TL;DR: distlib_hg and bandersnatch, you have a July 1st deadline to = switch to Git or move off Bitbucket. >=20 > https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket >=20 > "we've decided to remove Mercurial support from Bitbucket Cloud and = its API." >=20 > "Mercurial features and repositories will be officially removed from = Bitbucket and its API on July 1, 2020." >=20 > Most of https://bitbucket.org/pypa/ is Mercurial repos. Maintainers of = those repositories need to switch them to Git or move them off Bitbucket = by July 1st. >=20 > distlib_hg and bandersnatch are the active Mercurial repos that most = clearly need to switch or move. >=20 > A few repos in bitbucket.org/pypa have explicit "moved to GitHub" = notices on them. And I assume its pkg_resources , setuptools, = import_resources, pylauncher, and bootstrap projects are now defunct, = but it's probably worth archiving them somehow anyway, for historical = reference. >=20 > --=20 > Sumana Harihareswara > Changeset Consulting > https://changeset.nyc > -- > Distutils-SIG mailing list -- distutils-sig(a)python.org > To unsubscribe send an email to distutils-sig-leave(a)python.org > https://mail.python.org/mailman3/lists/distutils-sig.python.org/ > Message archived at = https://mail.python.org/archives/list/distutils-sig@python.org/message/QOS= UVOF6RY4EVFBFZRHL4WAENXVKH5YL/ --Apple-Mail=_108E09A8-924C-4637-B2BF-854F5C6C3608 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" = class=3D"">Bandersnatch moved over 2 years ago and has been displaying = the move on the repository this whole time via the README.md.<div = class=3D""><br class=3D""></div><div class=3D"">I just deleted it from = BitBucket. As we have been for the last 2 years, all bandersnatch action = can be found here: <a href=3D"https://github.com/pypa/bandersnatch" = class=3D"">https://github.com/pypa/bandersnatch</a><div class=3D""><br = class=3D""></div><div class=3D"">Cooper<br class=3D""><div><br = class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Jun = 15, 2020, at 2:29 PM, Sumana Harihareswara <<a = href=3D"mailto:sh@changeset.nyc" class=3D"">sh(a)changeset.nyc</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = class=3D"">TL;DR: distlib_hg and bandersnatch, you have a July 1st = deadline to switch to Git or move off Bitbucket.<br class=3D""><br = class=3D""><a = href=3D"https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbuck= et" = class=3D"">https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitb= ucket</a><br class=3D""><br class=3D"">"we've decided to remove = Mercurial support from Bitbucket Cloud and its API."<br class=3D""><br = class=3D"">"Mercurial features and repositories will be officially = removed from Bitbucket and its API on July 1, 2020."<br class=3D""><br = class=3D"">Most of https://bitbucket.org/pypa/ is Mercurial repos. = Maintainers of those repositories need to switch them to Git or move = them off Bitbucket by July 1st.<br class=3D""><br class=3D"">distlib_hg = and bandersnatch are the active Mercurial repos that most clearly need = to switch or move.<br class=3D""><br class=3D"">A few repos in = bitbucket.org/pypa have explicit "moved to GitHub" notices on them. And = I assume its pkg_resources , setuptools, import_resources, pylauncher, = and bootstrap projects are now defunct, but it's probably worth = archiving them somehow anyway, for historical reference.<br class=3D""><br= class=3D"">-- <br class=3D"">Sumana Harihareswara<br class=3D"">Changeset= Consulting<br class=3D"">https://changeset.nyc<br class=3D"">--<br = class=3D"">Distutils-SIG mailing list -- distutils-sig(a)python.org<br = class=3D"">To unsubscribe send an email to = distutils-sig-leave(a)python.org<br = class=3D"">https://mail.python.org/mailman3/lists/distutils-sig.python.org= /<br class=3D"">Message archived at = https://mail.python.org/archives/list/distutils-sig@python.org/message/QOS= UVOF6RY4EVFBFZRHL4WAENXVKH5YL/<br = class=3D""></div></div></blockquote></div><br = class=3D""></div></div></body></html>= --Apple-Mail=_108E09A8-924C-4637-B2BF-854F5C6C3608-- ------------------------------ Date: Mon, 15 Jun 2020 17:39:27 -0400 From: Sumana Harihareswara <sh(a)changeset.nyc> Subject: [Distutils] Re: July 1 deadline for Mercurial repositories on Bitbucket To: Cooper Lees <me(a)cooperlees.com> Cc: DistUtils mailing list <distutils-sig(a)python.org> Message-ID: <89166584-3008-dc33-df51-9ed53a9814cd(a)changeset.nyc> Content-Type: text/plain; charset=windows-1252; format=flowed Sorry I missed the note on the README! On 6/15/20 5:34 PM, Cooper Lees wrote: > Bandersnatch moved over 2 years ago and has been displaying the move on > the repository this whole time via the README.md. > > I just deleted it from BitBucket. As we have been for the last 2 years, > all bandersnatch action can be found here: > https://github.com/pypa/bandersnatch <https://github.com/pypa/bandersnatch> > > Cooper > >> On Jun 15, 2020, at 2:29 PM, Sumana Harihareswara <sh(a)changeset.nyc >> <mailto:sh@changeset.nyc>> wrote: >> >> TL;DR: distlib_hg and bandersnatch, you have a July 1st deadline to >> switch to Git or move off Bitbucket. >> >> https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket >> <https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket> >> >> "we've decided to remove Mercurial support from Bitbucket Cloud and >> its API." >> >> "Mercurial features and repositories will be officially removed from >> Bitbucket and its API on July 1, 2020." >> >> Most of https://bitbucket.org/pypa/ is Mercurial repos. Maintainers of >> those repositories need to switch them to Git or move them off >> Bitbucket by July 1st. >> >> distlib_hg and bandersnatch are the active Mercurial repos that most >> clearly need to switch or move. >> >> A few repos in bitbucket.org/pypa have explicit "moved to GitHub" >> notices on them. And I assume its pkg_resources , setuptools, >> import_resources, pylauncher, and bootstrap projects are now defunct, >> but it's probably worth archiving them somehow anyway, for historical >> reference. >> >> -- >> Sumana Harihareswara >> Changeset Consulting >> https://changeset.nyc >> -- >> Distutils-SIG mailing list -- distutils-sig(a)python.org >> To unsubscribe send an email to distutils-sig-leave(a)python.org >> https://mail.python.org/mailman3/lists/distutils-sig.python.org/ >> Message archived at >> https://mail.python.org/archives/list/distutils-sig@python.org/message/QOSU… > ------------------------------ Date: Mon, 15 Jun 2020 22:43:20 -0400 From: Sumana Harihareswara <sh(a)changeset.nyc> Subject: [Distutils] Re: July 1 deadline for Mercurial repositories on Bitbucket To: Cooper Lees <me(a)cooperlees.com> Cc: DistUtils mailing list <distutils-sig(a)python.org> Message-ID: <2b9c15d2-ac7d-ffaa-43ac-b2645a6f3bc3(a)changeset.nyc> Content-Type: text/plain; charset=utf-8; format=flowed I also just looked more closely at https://bitbucket.org/pypa/distlib_hg/src/default/ and https://bitbucket.org/pypa/distlib/src/master/ . The latter is a Git port of the former. So I still think it would be a very good idea to export and archive the old version history, issues, etc. for the Mercurial distlib repo, but it's less crucial. On 6/15/20 5:39 PM, Sumana Harihareswara wrote: > Sorry I missed the note on the README! > > On 6/15/20 5:34 PM, Cooper Lees wrote: >> Bandersnatch moved over 2 years ago and has been displaying the move >> on the repository this whole time via the README.md. >> >> I just deleted it from BitBucket. As we have been for the last 2 >> years, all bandersnatch action can be found here: >> https://github.com/pypa/bandersnatch >> <https://github.com/pypa/bandersnatch> >> >> Cooper >> >>> On Jun 15, 2020, at 2:29 PM, Sumana Harihareswara <sh(a)changeset.nyc >>> <mailto:sh@changeset.nyc>> wrote: >>> >>> TL;DR: distlib_hg and bandersnatch, you have a July 1st deadline to >>> switch to Git or move off Bitbucket. >>> >>> https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket >>> <https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket> >>> >>> "we've decided to remove Mercurial support from Bitbucket Cloud and >>> its API." >>> >>> "Mercurial features and repositories will be officially removed from >>> Bitbucket and its API on July 1, 2020." >>> >>> Most of https://bitbucket.org/pypa/ is Mercurial repos. Maintainers >>> of those repositories need to switch them to Git or move them off >>> Bitbucket by July 1st. >>> >>> distlib_hg and bandersnatch are the active Mercurial repos that most >>> clearly need to switch or move. >>> >>> A few repos in bitbucket.org/pypa have explicit "moved to GitHub" >>> notices on them. And I assume its pkg_resources , setuptools, >>> import_resources, pylauncher, and bootstrap projects are now defunct, >>> but it's probably worth archiving them somehow anyway, for historical >>> reference. >>> >>> -- >>> Sumana Harihareswara >>> Changeset Consulting >>> https://changeset.nyc >>> -- >>> Distutils-SIG mailing list -- distutils-sig(a)python.org >>> To unsubscribe send an email to distutils-sig-leave(a)python.org >>> https://mail.python.org/mailman3/lists/distutils-sig.python.org/ >>> Message archived at >>> https://mail.python.org/archives/list/distutils-sig@python.org/message/QOSU… >>> >> > -- > Distutils-SIG mailing list -- distutils-sig(a)python.org > To unsubscribe send an email to distutils-sig-leave(a)python.org > https://mail.python.org/mailman3/lists/distutils-sig.python.org/ > Message archived at > https://mail.python.org/archives/list/distutils-sig@python.org/message/N5QX… > ------------------------------ Subject: Digest Footer -- Distutils-SIG mailing list -- distutils-sig(a)python.org To unsubscribe send an email to distutils-sig-leave(a)python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ ------------------------------ End of Distutils-SIG Digest, Vol 206, Issue 1 *********************************************

1 0

July 1 deadline for Mercurial repositories on Bitbucket
by Sumana Harihareswara 16 Jun '20

16 Jun '20

TL;DR: distlib_hg and bandersnatch, you have a July 1st deadline to switch to Git or move off Bitbucket. https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket "we've decided to remove Mercurial support from Bitbucket Cloud and its API." "Mercurial features and repositories will be officially removed from Bitbucket and its API on July 1, 2020." Most of https://bitbucket.org/pypa/ is Mercurial repos. Maintainers of those repositories need to switch them to Git or move them off Bitbucket by July 1st. distlib_hg and bandersnatch are the active Mercurial repos that most clearly need to switch or move. A few repos in bitbucket.org/pypa have explicit "moved to GitHub" notices on them. And I assume its pkg_resources , setuptools, import_resources, pylauncher, and bootstrap projects are now defunct, but it's probably worth archiving them somehow anyway, for historical reference. -- Sumana Harihareswara Changeset Consulting https://changeset.nyc

2 3

setup() arguments documentation
by Johannes Müller 02 Jun '20

02 Jun '20

Hi, Shouldn't it be documented that the keyword argument "license_file" is supported as an agrument in setup()? It's currently not listed in the section https://setuptools.readthedocs.io/en/latest/setuptools.html#new-and-changed… Writing setup(..., license_file="LICENSE.txt", ...) has actually the same effect as adding "license_file" to the metadata section of setup.cfg. Such an elementary functionality as adding a license_file to a package should be considered to be a standard functionality of setup(), that should be properly documented. Right now, the users get's the impression, that it's necessary to use a setup.cfg file, if they want to use the license_file property. Regards, Johannes

1 0