GitXplorerGitXplorer
J

lxml-stubs

public
12 stars
3 forks
2 issues

Commits

List of commits on branch master.
Unverified
bec20aa359797ce28e60957a0a94d9ba5470dd92

etree: Add missing "None" return types

ssuutari committed 5 years ago
Unverified
475c14ae381b9bacbfa6ae4556711a75e0b4a702

etree: Annotate couple missing argument types

ssuutari committed 5 years ago
Unverified
4c6e8a09fbc1ae538685922c96b3c7fcc052d932

etree: Fix signature of _Attrib.__contains__

ssuutari committed 5 years ago
Verified
65e56adf4007b7b0227c04d4ba695f554ecd7129

Merge pull request #3 from funkyfuture/additions_as_needed

JJelleZijlstra committed 5 years ago
Verified
9d3a4814e5b520e1f74f01bef75fa1b4b37b1ae0

Merge branch 'master' into additions_as_needed

JJelleZijlstra committed 5 years ago
Verified
1b278e2633ff1c6df51d8f1a45fe16daee9ed14f

Merge pull request #6 from suutari/fix-any-generics

JJelleZijlstra committed 5 years ago

README

The README file for this repository.

lxml-stubs

About

This repository contains external type annotations (see PEP 484) for the lxml package. Such type annotations are normally included in typeshed, but lxml's annotations were frequently problematic and have therefore been deleted from typeshed. In particular, the stubs are incomplete and it has been difficult to provide complete stubs.

This repo provides lxml stubs as they existed in typeshed for those who find them useful. Eventually, it should become a PEP 561-style stubs package.

Usage

To use these stubs, clone this repo and point your type checker to it. For example, to use them in mypy, you can set the $MYPYPATH environment variable or set mypy_path = /path/to/lxml-stubs in your mypy.ini.

Contributing

Contributions should follow the same style guidelines as typeshed.

Git history

The early git history of this repo contains commits from typeshed, filtered to only changes that affect typeshed (using git filter-branch).

Authors

This repository was created by Jelle Zijlstra. Numerous others have contributed to the lxml stubs; see the git history for details.

TODOs

  • Provide testing (both a local test script and a Travis setup)
  • Provide a PEP 561-style setup script.