Message207232
| Author | arigo |
|---|---|
| Recipients | arigo |
| Date | 2014-01-03.17:59:12 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1388771953.42.0.332804570753.issue20115@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This is probably the smallest example of a .py file that behaves differently in CPython vs PyPy, and for once, I'd argue that the CPython behavior is unexpected:
# make the file:
>>> open('x.py', 'wb').write('#\x00\na')
# run it:
python x.py
Expected: either some SyntaxError, or "NameError: global name 'a' is not defined". Got: nothing. It seems that CPython completely ignores the line that is immediately after a line with a '#' and a following '\x00'. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-01-03 17:59:13 | arigo | set | recipients: + arigo |
| 2014-01-03 17:59:13 | arigo | set | messageid: <1388771953.42.0.332804570753.issue20115@psf.upfronthosting.co.za> |
| 2014-01-03 17:59:13 | arigo | link | issue20115 messages |
| 2014-01-03 17:59:12 | arigo | create | |