Message 310071 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	uranusjr
Recipients	uranusjr
Date	2018-01-16.10:44:16
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1516099456.9.0.467229070634.issue32567@psf.upfronthosting.co.za>
In-reply-to

Content
I’m not sure if it is intended, but it seems wrong to me that pyvenv.cfg is using a format that ConfigParser does not recognise. ConfigParser requires all values be placed under a section, but pyvenv.cfg does not do that. Maybe related: * ConfigParser’s format requirement: https://docs.python.org/3/library/configparser.html#supported-ini-file-structure * How venv creates the configuration file: https://github.com/python/cpython/blob/master/Lib/venv/__init__.py#L141 * Abandoned discussion on whether ConfigParser should support section-less format #22253

I’m not sure if it is intended, but it seems wrong to me that pyvenv.cfg is using a format that ConfigParser does not recognise. ConfigParser requires all values be placed under a section, but pyvenv.cfg does not do that.

Maybe related:

* ConfigParser’s format requirement: https://docs.python.org/3/library/configparser.html#supported-ini-file-structure
* How venv creates the configuration file: https://github.com/python/cpython/blob/master/Lib/venv/__init__.py#L141
* Abandoned discussion on whether ConfigParser should support section-less format #22253

History
Date	User	Action	Args
2018-01-16 10:44:16	uranusjr	set	recipients: + uranusjr
2018-01-16 10:44:16	uranusjr	set	messageid: <1516099456.9.0.467229070634.issue32567@psf.upfronthosting.co.za>
2018-01-16 10:44:16	uranusjr	link	issue32567 messages
2018-01-16 10:44:16	uranusjr	create