This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Enewman
Recipients Enewman, terry.reedy
Date 2018-11-29.20:00:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543521638.64.0.788709270274.issue35355@psf.upfronthosting.co.za>
In-reply-to
Content
Formatted strings seem to have some quirks.  
if you try putting in this, for example;
print(f'{0 0}')
; you get a syntax error, which is probably intended, but where the error is reported is not always accurate.  for example;
#just a comment, it doesn't matter what it says
print(f'{0 0}')
;will raise the syntax error, and highlight the j,u,and s in the comment!  that doesn't help, and makes it look like the comment is the error.  this is a real pain to debug if you hadn't known about this.  it took me about 2 hours to track down the problem.  seriously, this should be fixed.  I haven't tested the problem in any editor but idle, so the cause could be anywhere.  I was first using 3.7.0, I've just updated to 3.7.1 to make sure it still happens, and it does.
History
Date User Action Args
2018-11-29 20:00:38Enewmansetrecipients: + Enewman, terry.reedy
2018-11-29 20:00:38Enewmansetmessageid: <1543521638.64.0.788709270274.issue35355@psf.upfronthosting.co.za>
2018-11-29 20:00:38Enewmanlinkissue35355 messages
2018-11-29 20:00:38Enewmancreate