Mailman 3 - Distutils-SIG

python3 prefixed package RPMs
by Ratliff, John 08 Jan '20

08 Jan '20

It seems RHEL/CentOS prefers python3-{package}.rpm as the RPM name, with the python3 part of the package name. If I add python3 as a name prefix in setuptools, it works, but it changes the egg-info directory to have the python3- prefix as well, which is not what I've seen in other python RPMs in CentOS. Is there a way I can add the python3 prefix when doing python3 setup.py bdist_rpm? Thanks. --John

2 1

Setuptools use pip over easy_install when installing through setup.py
by Pokestar Fan 25 Dec '19

25 Dec '19

I was running a test program through setup.py, and it threw an error whenever it tried to install a package on a Windows 10 Python 3.8 installation (It worked on mac/ubuntu all versions and Python 3.5-3.7 on Windows 10). However, if I installed the packages through pip instead of easy install the tests ran as excepted. Can installing packages through setup.py go through pip and not easy install, as easy install is deprecated?

2 1

Listing
by Daniel Scott 13 Dec '19

13 Dec '19

Sent from Yahoo Mail on Android

1 0

Post UTME Screening Form
by tinyang60＠gmail.com 29 Nov '19

29 Nov '19

<a href="https://www.downloadpastquestion.com.ng/category/admission-form/">Post UTME Screening form</a> and registration 2020/2021 academic session is out.

1 0

Post UTME Screening Form
by tinyang60＠gmail.com 29 Nov '19

29 Nov '19

The <a href="https://www.downloadpastquestion.com.ng/category/admission-form/">Post UTME Screening form</a> and registration 2020/2021 academic session is out

1 0

Apply by Nov 22 for paid contract on pip
by Sumana Harihareswara 26 Nov '19

26 Nov '19

Freelancers and other programming consultants: Get paid to improve pip. Specifically, to help finish the dependency resolver overhaul. https://pyfound.blogspot.com/2019/11/seeking-developers-for-paid-contract.h… Role 1: We seek a senior Python developer, work starting in mid-December 2019 or early January 2020, work ending at the end of May 2020. Pay: USD$116,375 total (665 hours of work at $175 per hour). Detailed task list and timeline: https://github.com/python/request-for/blob/master/2020-pip/RFP.md#role-1-se… Role 2: We seek an intermediate-to-senior Python developer, work starting in early January 2020, till the end of December 2020. Pay: USD$103,700 (670 hours of work at $150 per hour), plus $1600 budgeted for onboarding travel and $1600 budgeted for PyCon travel. Details: https://github.com/python/request-for/blob/master/2020-pip/RFP.md#role-2-in… Full request for proposals: https://github.com/python/request-for/blob/master/2020-pip/RFP.md Please apply by November 22nd, or please spread the word. Here's the giant list of reasons why this project is important: https://wiki.python.org/psf/Fundable%20Packaging%20Improvements#Finish_depe… -- Sumana Harihareswara contract project manager for PSF Changeset Consulting https://changeset.nyc

1 2

Re: Keywords field in metadata: space separated or comma separated?
by Pradyun Gedam 19 Nov '19

19 Nov '19

Resending, since the previous attempt was blocked by the mailing list. On Tue, 19 Nov 2019 at 11:53 PM, Pradyun Gedam <pradyunsg(a)gmail.com> wrote: > > > On Tue, Nov 19, 2019 at 1:31 PM Thomas Kluyver <thomas(a)kluyver.me.uk> > wrote: > >> There seems to be a loose agreement in favour of changing the spec to >> match what distutils & setuptools do, so I've opened a PR against the spec: >> >> https://github.com/pypa/packaging.python.org/pull/674 >> > > The PR has been merged. > > Overall, this looks like a good idea to me, as might be clear from the > fact that I approved the PR. > > -- > Pradyun >

1 0

Keywords field in metadata: space separated or comma separated?
by Thomas Kluyver 19 Nov '19

19 Nov '19

Hi all, The metadata specification shows the keyword field as a space separated list: https://packaging.python.org/specifications/core-metadata/#keywords PEP 566 backs that up, saying that the transformation to JSON should split that field on whitespace: https://www.python.org/dev/peps/pep-0566/#json-compatible-metadata However, distutils reads and writes that field as a comma separated list: https://github.com/python/cpython/blob/5383956583bb758f3828513bcdd011871f24… https://github.com/python/cpython/blob/5383956583bb758f3828513bcdd011871f24… And setuptools has inherited that: https://github.com/pypa/setuptools/blob/68dbb703705cdd64e25261a6fcc1c0cc96b… https://github.com/pypa/setuptools/blob/68dbb703705cdd64e25261a6fcc1c0cc96b… Given the dominance of distutils and setuptools, and the difficulty of changing distutils, I suspect it's easier to change the spec to adopt their de-facto standard as the official standard. But I'd like confirmation of this, as it will require some changes in Flit. The comma-separated format allows keywords containing a space - like 'orbital mechanics' in the example I was investigating (poliastro). Thanks, Thomas

3 3

proposing Python package index upload API spec (potential PEP)
by Sumana Harihareswara 18 Nov '19

18 Nov '19

As a new Twine maintainer I've been running into questions like: * Now that Warehouse doesn't use "register" anymore, can we deprecate it from distutils, setuptools, and twine? Are any other package indexes or upload tools using it? https://github.com/pypa/twine/issues/311 * It would be nice if Twine could depend on a package index providing an HTTP 201 response in response to a successful upload, and fail on 200 (a response some non-package-index servers will give to an arbitrary POST request). I do not see specifications to guide me here, e.g., in the official guidance on hosting one's own package index https://packaging.python.org/guides/hosting-your-own-index/ . PEP 301 was long enough ago that it's due an update, and PEP 503 only concerns browsing and download, not upload. I suggest that I write a PEP specifying an API for uploading to a Python package index. This PEP would partially supersede PEP 301 and would document the Warehouse reference implementation. I would write it in collaboration with the Warehouse maintainers who will develop the reference implementation per pypa/warehouse/issues/284 and maybe add a header referring to compliance with this new standard. And I would consult with the maintainers of packaging and distribution tools such as zest.releaser, flit, poetry, devpi, pypiserver, etc. Per Nick Coghlan's formulation, my specific goal here would be close to: > Documenting what the current upload API between twine & warehouse actually is, similar to the way PEP 503 focused on describing the status quo, without making any changes to it. That way, other servers (like devpi) and other upload clients have the info they need to help ensure interoperability. Since Warehouse is trying to redo its various APIs in the next several months, I think it might be more useful to document and work with the new upload API, but I'm open to feedback on this. After a little conversation here on distutils-sig, I believe my steps would be: 1. start a very early PEP draft with lots of To Be Determined blanks, submit as a PR to the python/peps repo, and share it with distutils-sig 2. ping maintainers of related tools 3. discuss with others at the packaging sprints https://wiki.python.org/psf/PackagingSprints next week 4. revise and get consensus, preferably mostly on this list 5. finalize PEP and get PEP accepted by BDFL-Delegate 6. coordinate with PyPA, maintainers of `distutils`, maintainers of packaging and distribution tools, and documentation maintainers to implement PEP compliance Thoughts are welcome. I originally posted this at https://github.com/pypa/packaging-problems/issues/128 . -- Sumana Harihareswara Changeset Consulting https://changeset.nyc

4 4

Python 3.8
by Шехматов С.В. 13 Nov '19

13 Nov '19

Здравствуйте, Distutils-sig. That is what i have after attempt to install pygame module in Python 3.8. c:\Users\AMD\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0>pip3.8 install pygame Collecting pygame Using cached https://files.pythonhosted.org/packages/0f/9c/78626be04e193c0624842090fe555… ERROR: Command errored out with exit status 1: command: 'C:\Users\AMD\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\AMD\\AppData\\Local\\Temp\\pip-install-fl0na0dp\\pygame\\setup.py'"'"'; __file__='"'"'C:\\Users\\AMD\\AppData\\Local\\Temp\\pip-install-fl0na0dp\\pygame\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base pip-egg-info cwd: C:\Users\AMD\AppData\Local\Temp\pip-install-fl0na0dp\pygame\ Complete output (17 lines): WARNING, No "Setup" File Exists, Running "buildconfig/config.py" Using WINDOWS configuration... Download prebuilts to "prebuilt_downloads" and copy to "./prebuilt-x64"? [Y/n]Traceback (most recent call last): File "<string>", line 1, in <module> File "C:\Users\AMD\AppData\Local\Temp\pip-install-fl0na0dp\pygame\setup.py", line 194, in <module> buildconfig.config.main(AUTO_CONFIG) File "C:\Users\AMD\AppData\Local\Temp\pip-install-fl0na0dp\pygame\buildconfig\config.py", line 210, in main deps = CFG.main(**kwds) File "C:\Users\AMD\AppData\Local\Temp\pip-install-fl0na0dp\pygame\buildconfig\config_win.py", line 576, in main and download_win_prebuilt.ask(**download_kwargs): File "C:\Users\AMD\AppData\Local\Temp\pip-install-fl0na0dp\pygame\buildconfig\download_win_prebuilt.py", line 302, in ask reply = raw_input( EOFError: EOF when reading a line ---------------------------------------- ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. WARNING: You are using pip version 19.2.3, however version 19.3.1 is available. You should consider upgrading via the 'python -m pip install --upgrade pip' command. P,S. Python 3.7 did this operation without problem!? -- С уважением, Шехматов mailto:shex@yandex.ru

2 1