Message283878
| Author | r.david.murray |
|---|---|
| Recipients | eric.smith, martin.panter, r.david.murray, yan12125 |
| Date | 2016-12-23.13:55:37 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1482501337.55.0.789465344475.issue29051@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
These are not problems with f-strings in particular, they are problems in general with the way python parsing and error reporting happens. The second is presumably (I haven't gotten around to understanding how f-strings work under the hood) an example of error reporting from a separately evaled string. Improvements in this area are certainly welcome. There is an open issue relevant to your first example, issue 12458. I'm sure that f-strings complicate the solution at least slightly, but I think there are more fundamental pre-requisites to be addressed first in solving it. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-12-23 13:55:37 | r.david.murray | set | recipients: + r.david.murray, eric.smith, martin.panter, yan12125 |
| 2016-12-23 13:55:37 | r.david.murray | set | messageid: <1482501337.55.0.789465344475.issue29051@psf.upfronthosting.co.za> |
| 2016-12-23 13:55:37 | r.david.murray | link | issue29051 messages |
| 2016-12-23 13:55:37 | r.david.murray | create | |