Author Topic: Python block comments broken in v19  (Read 2211 times)

mlevedahl

  • Junior Community Member
  • Posts: 4
  • Hero Points: 0
Python block comments broken in v19
« 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'''

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1471
  • Hero Points: 131
Re: Python block comments broken in v19
« Reply #1 on: November 17, 2014, 02:32:36 pm »
Reproduced it, taking a look.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1471
  • Hero Points: 131
Re: Python block comments broken in v19
« Reply #2 on: November 17, 2014, 09:12:49 pm »
Fixed.  Unfortunately, it's not hot-fixable, so it will be in the first update.

IkerAriz

  • Senior Community Member
  • Posts: 148
  • Hero Points: 6
Re: Python block comments broken in v19
« Reply #3 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

brainsalad

  • Community Member
  • Posts: 11
  • Hero Points: 2
Re: Python block comments broken in v19
« Reply #4 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.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5714
  • Hero Points: 457
Re: Python block comments broken in v19
« Reply #5 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.