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 xtreak
Recipients Hasan Diwan, ezio.melotti, michael.foord, rbcollins, xtreak
Date 2019-07-24.12:38:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563971885.1.0.521713431063.issue37668@roundup.psfhosted.org>
In-reply-to
Content
If I understand the patch correctly this is is the behavior of the patch

./python.exe -m unittest test#test_keyword
.......
----------------------------------------------------------------------
Ran 7 tests in 0.001s

OK

Do you have a good use case over why # also needs to be supported? Using "." feels more readable and its more intuitive given import statements use it and almost used throughout the language. I am also not sure how "#" will behave in different shell environments since its a common character used as to denote comments.
History
Date User Action Args
2019-07-24 12:38:05xtreaksetrecipients: + xtreak, rbcollins, ezio.melotti, michael.foord, Hasan Diwan
2019-07-24 12:38:05xtreaksetmessageid: <1563971885.1.0.521713431063.issue37668@roundup.psfhosted.org>
2019-07-24 12:38:05xtreaklinkissue37668 messages
2019-07-24 12:38:04xtreakcreate