`ElementTree.parse` type hinted to return unusable generic types
Personne n'a encore pris cette issue.
- Langage dominant
- Python
- Étoiles
- 5.1k
- Forks
- 2.1k
- Merge moyen
- 1 j 19 h
- PR mergées (30 j)
- 82
Description
Bug Report
Since upgrading to mypy 1.15+, using ElementTree has become increasingly difficult. Likely due to https://github.com/python/typeshed/pull/13349. I'm not sure if this extra strictness is expected or if I'm just holding it wrong.
One example is the ElementTree.parse function that now returns a generic ET.ElementTree[ET.Element[str]], which is no longer compatible with basic type signatures like ET.ElementTree, which is interpreted as ElementTree[Element[str] | None].
This adds many challenges that make it difficult to work with.
- The generic argument here is very difficult to understand what it means and is lacking documentation. From what i've been able to deduce it's possible that the root node is of a different Element type or that the root node is None. While perhaps a valid scenario, it adds a big uphill to learning and usability.
- If one were to use these generic types, typing out
ET.ElementTree[ET.Element[str]]is a lot more verbose thanET.ElementTree, and i'm questioning if the strictness here is worth it. - If one tries to type hint the code with these generics. Python throws errors that
'ElementTree.Element' is not subscriptable. One workaround i found for this is to surround the type hints with double-quotes.
To Reproduce
import xml.etree.ElementTree as ET
def process_document(doc: ET.ElementTree) -> None:
pass
def process_document2(doc: ET.ElementTree[ET.Element[str]]) -> None: # TypeError: type 'xml.etree.ElementTree.Element' is not subscriptable
pass
process_document(ET.parse("foo.xml")) # mypy error: Argument 1 to "process_document" has incompatible type "ElementTree[Element[str]]"; expected "ElementTree[Element[str] | None]" [arg-type]
process_document2(ET.parse("foo.xml"))
Run with mypy --strict
Expected Behavior
ET.parse returns types assignable to ET.ElementTree
Actual Behavior
Mypy returns errror
# mypy error: Argument 1 to "process_document" has incompatible type "ElementTree[Element[str]]"; expected "ElementTree[Element[str] | None]" [arg-type]
Workarounds
- Use
ET.ElementTree().parse()function instead ofET.parse(), it returns the root-node as a type that can be assigned toET.Elementwithout any generic arguments.
This is actually a pretty decent option, if this is considered to be the primary way of using ElementTree from now on, the documentation should reflect that, right now it's suggestingET.parse() - Type out the complete
"ElementTree[Element[str] | None]"wrapped with double-quotes.
Your Environment
- Mypy version used:
- Mypy command-line flags:
- Mypy configuration options from
mypy.ini(and other config files): - Python version used:
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par lire typeshed PR 13349 et les annotations de ElementTree.parse, puis comparez-les avec le contournement ElementTree().parse() et la documentation Python ElementTree. Le travail est terminé lorsque le comportement générique prévu et l’assignabilité attendue de ET.parse() sont établis, et que le problème de typage ou de documentation correspondant est traité.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- devtools
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100