Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Clark
« on: November 23, 2014, 03:38:28 AM »

Sorry about this issue. We know we can't wait that long for an update which fixes this.
Posted by: brainsalad
« on: November 21, 2014, 04:49:52 PM »

Update soon, please.  I have temporarily switched to using triple double-quoted doc strings, and it pains me.  If I can't switch back to triple single quotes soon, I might die.  I am aware that is unreasonable.
Posted by: IkerAriz
« on: November 19, 2014, 06:26:10 PM »

This seems to apply to triple-quoted strings more generally. Eg, setting a variable to TQ string that spans multiple lines.

Will the update be available soon? The loss of syntax coloring really puts a damper on using SE for python projects.

Regards,
Iker
Posted by: patrick
« on: November 17, 2014, 09:12:49 PM »

Fixed.  Unfortunately, it's not hot-fixable, so it will be in the first update.
Posted by: patrick
« on: November 17, 2014, 02:32:36 PM »

Reproduced it, taking a look.
Posted by: mlevedahl
« on: November 17, 2014, 01:52:45 PM »

In python, a sequence of 3 single quotes or double quotes are used to denote a block comment. v19 does not recognize the closing set of single quotes unless on the same line. e.g.
""" some stuff
     works"""

''' a single line using triple quotes works '''

''' but a comment on multiple lines
   ends up treating the rest of the file as a comment'''