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 wrobell
Recipients
Date 2005-02-23.14:44:04
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=387193

I do understand that the patch will not be accepted. :-)
That's ok. Too much fight with people's habits for me. :]

But, let's see what common script names are forbidden now
(among others):
array.py, binascii.py, bz2.py, collections.py, crypt.py,
datetime.py, math.py, md5.py, mmap.py, parser.py, pwd.py,
regex.py, resource.py, select.py, sha.py, syslog.py,
time.py, timing.py, timeit.py, binhex.py, calendar.py,
cgi.py, chunk.py, cmd.py, code.py, commands.py,
compileall.py, compiler.py, copy.py, csv.py, decimal.py...

And in the future there can be even more depending on the
new modules in Python itself and third party modules (i.e.
spread.py, dbus.py, eca.py, etc.). If new module or package
appears, then you will have to change your name of the
script. I do understand that it is not frequent situation,
but we should not to be forced to avoid certain
_common_ words for script naming.

IMHO, it is a problem and should be fixed. The question is
"How?".
Maybe page listed below should be discussed (again I think):

   http://hkn.eecs.berkeley.edu/~dyoo/python/__std__/

I would set Resolution to "Remind" if you agree to discuss
it later and fix the problem somehow in the future. If not,
then "Won't fix".
History
Date User Action Args
2007-08-23 15:37:35adminlinkissue946373 messages
2007-08-23 15:37:35admincreate