Crash report when importing easter egg #720

Closed
scaryclam opened this Issue Aug 22, 2011 · 5 comments

Comments

Projects
None yet
3 participants
@scaryclam

Running the command:

from __future__ import braces

crashes iPython. This isn't exactly a critical issue but I thought you may like to know in case the problem is further reaching.

I thought it was kind of funny that ipython was so disgusted with the idea of braces it couldn't cope :)

The full crash report can be found: http://pastebin.com/A9fghfZA

@scaryclam

This comment has been minimized.

Show comment
Hide comment
@scaryclam

scaryclam Aug 22, 2011

Just to note, future has double underscores either side of it but github obviously uses that as markup for bold.

Just to note, future has double underscores either side of it but github obviously uses that as markup for bold.

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Aug 22, 2011

Member

Thanks. It is slightly broader - it seems that from __future__ import x causes the problem, where x is anything that's not a valid name. We just need to catch SyntaxError at another point.

Member

takluyver commented Aug 22, 2011

Thanks. It is slightly broader - it seems that from __future__ import x causes the problem, where x is anything that's not a valid name. We just need to catch SyntaxError at another point.

@ghost ghost assigned takluyver Aug 22, 2011

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Aug 22, 2011

Member

(P.S. backticks format code blocks. Or

` tags.)

Member

takluyver commented Aug 22, 2011

(P.S. backticks format code blocks. Or

` tags.)

@minrk

This comment has been minimized.

Show comment
Hide comment
@minrk

minrk Sep 7, 2011

Member

@takluyver, did you fix this? I don't see a crash in master.

Member

minrk commented Sep 7, 2011

@takluyver, did you fix this? I don't see a crash in master.

@takluyver

This comment has been minimized.

Show comment
Hide comment
@takluyver

takluyver Sep 7, 2011

Member

Not me. I think it was @fperez, with 1a64b37 (in the drawing room). Anyway, I agree that it's fixed.

Member

takluyver commented Sep 7, 2011

Not me. I think it was @fperez, with 1a64b37 (in the drawing room). Anyway, I agree that it's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment