Peter Cock

I suspected you might say that - I'm not sure without digging into it if this is an oversight in just the recently added ``\begin{minted}{pycon}`` regex, or all the LaTeX...

Probably not unexpected, but ``d`` has the same issue: ``` v = 3.14159 print(f"{v:0.2f}") level = 123 print(f"Level is {level:d}") ``` ``` $ flake8 --select PIE pie.py pie.py:2:7: PIE782: Unnecessary...

Would the rule be useful if it was something as crude as ``f"string"`` without at least one ``{`` and at least one ``}`` character present?

OK, I see now that the ast does not easily give you the literal value. Currently you look at any ``JoinedStr`` and if it contains a ``FormattedValue`` it is fine,...

I've spent a while looking into the AST tree, but failed to spot how to solve this. Removing the PIE782 warning may be the pragmatic way forward :(

Slightly on a tangent, but I've started working on a plugin to flag the different Python string formatting styles: https://github.com/peterjc/flake8-sfs https://pypi.org/project/flake8-sfs/ I would ideally include pointless f-strings as a special...

I mentioned another hybrid example on #5 using what I would call ``MAJOR.0Y.0M.0D`` in the CalVer style notation.

And on the other hand, if you wanted to _require_ both the forward and reverse primers be present, you'd use ``-g`` instead of ``-a``

@chapmanb pointed this possible but quite ambitious Biopython GSoC 2013 idea of mine has some overlap (but what I had in mind was much more general than just GFF covering...

Can you do this on the in-browser version as well as the iOS app, or does Safari not allow that?