PyPSA / PyPSA/linopy

Check exposed types

Open
#367 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data-model refactor
Dominant language
Python
Stars
257
Forks
87
Avg merge
1d 3h
Merged PRs (30d)
29

Description

Static types of linopy are now exposed via py.typed. But this leads to tons of mypy problems in packages importing linopy. These need to be fixed. A good starting point is to simply check mypy with linopy in PyPSA by reverting https://github.com/PyPSA/PyPSA/pull/1028/commits/1f99f5dc143dbc4808ddcee0eab48973433e8b60.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reverting PyPSA pull request 1028 commit 1f99f5dc143dbc4808ddcee0eab48973433e8b60 and run mypy with linopy's py.typed package exposed. Use the resulting errors to identify the typing changes needed, with completion indicated by the importing PyPSA packages passing mypy.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
developer-experience
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.