[issue31898] Add a `recommended-packages.txt` file

[Joannah Nanjekye]

Change by Joannah Nanjekye :


--
nosy: +nanjekyejoannah

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31898] Add a `recommended-packages.txt` file

[Nick Coghlan]

Nick Coghlan  added the comment:

Removing the issue assignment, as I'm not actively working on this (although I 
still think it's a reasonable idea).

--
assignee: ncoghlan -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31898] Add a `recommended-packages.txt` file

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +xtreak

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31898] Add a `recommended-packages.txt` file

[Paul Ganssle]

Paul Ganssle  added the comment:

> datetime.timezone -> pytz.timezone (updates driven by IANA timezone database)

I will note that `pytz.timezone` and `datetime.timezone` are not really 
comparable (they do two very different things), and as of Python 3.6, 
`dateutil.tz` is the recommended source for IANA time zones, not `pytz`, per 
https://docs.python.org/3/library/datetime.html

--
nosy: +p-ganssle

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31898] Add a `recommended-packages.txt` file

[Nick Coghlan]

Nick Coghlan  added the comment:

In https://mail.python.org/pipermail/python-ideas/2017-October/047599.html, 
Guido suggested managing this as an occasionally updated Informational PEP 
(somewhat akin to PEP 394), and I think that will actually work fairly well:

* it clearly gives the information PEP level status (which merely being in the 
developer guide wouldn't)
* it means the guidance can be mostly version independent (which would be a 
source of irritation if the list was in the reference documentation)
* it means we can use the same process for amendments as we do for other 
informational PEPs (a combination of python-dev discussions, bugs.python.org 
issues, and specific PR reviews)

My current thoughts on structuring that:

Title: Recommended Independently Updated Python Packages

Tone/Audience: I'll aim the PEP primarily at answering the "Why isn't  in 
the standard library?" question, as that helps us keep the list focused on 
python-dev specific concerns and avoid turning it into a general categorised 
list of Python library recommendations like 
https://github.com/vinta/awesome-python

The key criterion for something being mentioned will be when the standard 
library *already* contains comparable functionality, but there's a language 
version independent third party alternative that even core developers will 
often use instead. That list is currently:

urllib.requests -> requests (pace of change in web standards)
re -> regex (technical challenges with backend migration)
datetime.timezone -> pytz.timezone (updates driven by IANA timezone database)
ctypes -> cffi (build tools should be version independent)
distutils -> setuptools (build tools should be version independent)

I'll likely also include a list of libraries where version independence is a 
key feature, so they've never even been proposed for stdlib inclusion, despite 
their broad popularity:

- the six compatibility module
- various backport libraries (e.g. importlib2, contextlib2, unittest2)
- third party libraries like lxml

I'm not sure if or how I'll cover the scientific Python stack (especially 
NumPy.ndarray being the reference implementation for multi-dimensional arrays), 
but Nathaniel Smith has some interesting thoughts on that in 
https://mail.python.org/pipermail/python-ideas/2017-November/047636.html

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31898] Add a `recommended-packages.txt` file

[Éric Araujo]

Change by Éric Araujo :


--
nosy: +eric.araujo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31898] Add a `recommended-packages.txt` file

[Nick Coghlan]

Nick Coghlan  added the comment:

Thinking about it further, this list is actually going to be version 
independent, suggest it may actually belong somewhere outside the main 
documentation.

The Developer's Guide may be a reasonable stopgap measure until there's a 
better option available (e.g. if I ever get around to turning 
https://github.com/python/redistributor-guide/ into something more than a 
nearly empty repo)

--
title: Add `recommended-packages.txt` to `venv` documentation -> Add a 
`recommended-packages.txt` file

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com