Unbalanced LaTeX style quotes in PyPy3 welcome message

Create issue
Issue #2519 new
Peter Cock created an issue

PyPy2 does not show a welcome message starting "And now for something completely different", e.g.

$ ~/Downloads/pypy-5.7-linux_x86_64-portable/bin/pypy
Python 2.7.13 (fa3249d55d15b9829e1be69cdf45b5a44cec902d, Mar 21 2017, 14:51:03)
[PyPy 5.7.0 with GCC 6.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>> quit()

However, PyPy3 shows a random quote wrapped in LaTeX style quote marks (double back tick for opening, double apostrophe for closing), e.g.

$ ~/Downloads/pypy3.5-5.7-beta-linux_x86_64-portable/bin/pypy
Python 3.5.3 (b16a4363e930f6401bceb499b9520955504c6cb0, Mar 21 2017, 12:36:24)
[PyPy 5.7.0-beta0 with GCC 6.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``"Somewhere inside the large
lumbering blob of PyPy there is an elegant core trying to get out." - cfbolz''
>>>> quit()

or:

$ ~/Downloads/pypy3.5-5.7-beta-linux_x86_64-portable/bin/pypy
Python 3.5.3 (b16a4363e930f6401bceb499b9520955504c6cb0, Mar 21 2017, 12:36:24)
[PyPy 5.7.0-beta0 with GCC 6.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``happy new year''
>>>> quit()

This style is now archaic and likely to cause trouble in other settings after copy-and-pasting. In particular most markdown languages consider back-ticks to indicate a code literal - and many bug trackers (e.g. GitHub, BitBucket) use this for reporting issues.

I propose that you simply remove the double-back-tick and the double-apostrophe.

Comments (1)

  1. Log in to comment