Revision history  [back]

I filed a bug report yet, but because it might be of interests for others too (and I've been bitten again), I would like emphasize the issue here again:

I'm using f-strings more and more. Up to now, Wing is not able to track variables in a comprehensive way, if they are used inside f-strings. This affects all tools: "Find Points of use", refactorings (renames!) etc.. The syntax highliter OTH 'sees' variables in f-strings (but of course also functions of them there only as a single entity). But perhaps this could be utilized for complete detection of this references. In my opinion, a solution of the problem is quite important for any non-trivial (yet by scope alone) refactoring usage.

I filed a bug report yet, but because it might be of interests for others too (and I've been bitten again), I would like emphasize the issue here again:

I'm using f-strings more and more. Up to now, Wing is not able to track variables in a comprehensive way, if they are used inside f-strings. This affects all tools: "Find Points of use", refactorings (renames!) etc.. The syntax highliter OTH 'sees' variables in f-strings (but of course also functions of them there only as a single entity). But perhaps this could be utilized for complete detection of this references. In my opinion, a solution of the problem is quite important for any non-trivial (yet by scope alone) refactoring usage.

I filed a bug report yet, but because it might be of interests for others too (and I've been bitten again), I would like emphasize the issue here again:

I'm using f-strings more and more. Up to now, Wing is not able to track variables in a comprehensive way, if they are used inside f-strings. This affects all tools: "Find Points of use", refactorings (renames!) etc.. The syntax highliter OTH 'sees' variables in f-strings (but of course also functions of them there only as a single entity). But perhaps this could be utilized for complete detection of used detecting this references. In my opinion, a solution of the problem is quite important for any non-trivial (yet by scope alone) refactoring usage.