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 johnreese
Recipients
Date 2007-03-04.08:40:44
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Given that in Python 3000 you can now use ... as an expression, it seemed like its repr might as well be ... too.  The thread quoted in pep 3100 as the reason for the decision suggested using '(int, ...)' as a type annotation; in such expressions, having ... print as ... would be more readable.

Note that this would break any doctests including ellipses; none of the Lib/test tests do, and the non-doctests don't care about the repr and still pass.  Since prior to Python 3000 ... could only be used in slices, it's unlikely this will break much.

I have now written about 100 times more characters than are changed by the patch.
History
Date User Action Args
2007-08-23 15:56:58adminlinkissue1673355 messages
2007-08-23 15:56:58admincreate