Éric Araujo added the comment:
I don’t believe aliases would help, on the contrary. There already are a good
number of fields to remember. Anyway I expect people to use “pysetup create”
or copy-pasting, so the spelling is not important: nobody will really have to
remember it. I have no per
anatoly techtonik added the comment:
1. Why not to add aliases?
2. Why not to postpone it to 3.4?
3. Why PEP change is a heavy process? Can we lighten it? (where is the
description is PEP change process at all)
--
status: closed -> pending
___
Pytho
Éric Araujo added the comment:
Sorry, Alexis is right. The fields in setup.cfg directly come from the PEP.
Tarek insisted on that. We’ve only added some fields, like description-file,
but never changed the names.
--
resolution: -> works for me
stage: -> committed/rejected
status:
Alexis Metaireau added the comment:
While I kind of agree with you, this field is proposed by the PEP 345
and had been approved as it is. It seems probably better to stick with
what's defined there mainly because any change to the PEP is a heavy
process and we won't have time to go trough it
New submission from anatoly techtonik :
home_page is too conservative, ugly and requires more time typing. "home page"
is also 2.15 times less popular that "homepage" spelling
http://www.google.com/trends/?q=%22home+page%22,+%22homepage%22
Writing setup.cfg files for humans should be simple an
