pypsa 1.2.0__tar.gz → 1.2.2__tar.gz

{pypsa-1.2.0 → pypsa-1.2.2}/.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -14,6 +14,8 @@ body:
       Thanks for taking the time to fill out this bug report!
       Please do not post usage questions here. Ask them on the [PyPSA Discord server](https://discord.gg/AnuJBk23FU).
 
+      Please write this issue description yourself. Any potentially verbose AI-generated content should be marked. See [Contributing guidelines](https://docs.pypsa.org/latest/contributing/contributing/).
+
 - type: checkboxes
   id: checks
   attributes:

{pypsa-1.2.0 → pypsa-1.2.2}/.github/ISSUE_TEMPLATE/feature_request.md

@@ -10,6 +10,8 @@ assignees: ''
 
 <!-- Please do not post usage questions here. Ask them on the PyPSA Discord server: https://discord.gg/AnuJBk23FU -->
 
+<!-- Please write this issue description yourself. Any potentially verbose AI-generated content should be marked. See Contributing guidelines: https://docs.pypsa.org/latest/contributing/contributing/ -->
+
 ## Describe the feature you'd like to see
 
 *Please give a clear and concise description and provide context why the feature would be useful.*

{pypsa-1.2.0 → pypsa-1.2.2}/.github/pull_request_template.md

@@ -8,4 +8,5 @@ Closes # (if applicable).
 - [ ] Code changes are sufficiently documented; i.e. new functions contain docstrings and further explanations may be given in `docs`.
 - [ ] Unit tests for new features were added (if applicable).
 - [ ] A note for the release notes `docs/release-notes.md` of the upcoming release is included.
+- [ ] PR description is written by me. Any potentially verbose AI-generated content is marked (see [Contributing guidelines](https://docs.pypsa.org/latest/contributing/contributing/)).
 - [ ] I consent to the release of this PR's code under the MIT license.

{pypsa-1.2.0 → pypsa-1.2.2}/.github/workflows/release.yml

@@ -92,8 +92,14 @@ jobs:
             print(f"repointed {dst_key} -> {src_key}")
       shell: python
 
+  test:
+    needs: [publish-examples]
+    uses: ./.github/workflows/test.yml
+    secrets: inherit
+
   build:
     name: Build and verify package
+    needs: [test]
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v6
@@ -105,7 +111,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v6
-    - uses: softprops/action-gh-release@v2
+    - uses: softprops/action-gh-release@v3
       with:
         body: |
           Revised release notes are available in the [documentation](https://docs.pypsa.org/latest/release-notes/).

{pypsa-1.2.0 → pypsa-1.2.2}/.github/workflows/test-models.yml

@@ -84,7 +84,7 @@ jobs:
       if: steps.filter.outputs.src == 'true' || github.event_name == 'schedule'
       uses: prefix-dev/setup-pixi@v0.9.5
       with:
-        pixi-version: v0.59.0
+        pixi-version: v0.68.1
         cache: true
         # Do not cache in branches
         cache-write: ${{ github.event_name == 'push' && github.ref_name == 'main' }}
@@ -120,7 +120,10 @@ jobs:
     - name: Install package from ref
       if: (steps.filter.outputs.src == 'true' || github.event_name == 'schedule') && env.pinned == 'false'
       run: |
+        # Allow upgrading internal packages without exclude-newer cap
+        sed -i '/^exclude-newer\s*=/d' pixi.toml
         pixi remove ${{ env.PACKAGE_NAME }}
+        pixi upgrade linopy
         pixi add --pypi --git https://github.com/${{ github.repository }}.git ${{ github.event.repository.name }} --rev ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}
 
     - name: Run snakemake test workflows

{pypsa-1.2.0 → pypsa-1.2.2}/.github/workflows/test.yml

@@ -13,6 +13,7 @@ on:
     branches: ["*"]
   schedule:
   - cron: "0 5 * * *"
+  workflow_call:
 
 # Cancel any in-progress runs when a new run is triggered
 concurrency:

pypsa-1.2.2/CONTRIBUTING.md

@@ -0,0 +1,14 @@
+<!--
+SPDX-FileCopyrightText: PyPSA Contributors
+
+SPDX-License-Identifier: MIT
+-->
+
+🎉 Thank you for your interest in contributing to PyPSA! 🎉
+
+We strongly welcome anyone interested in contributing to PyPSA and its related projects. All types of contributions are encouraged and valued!
+
+For detailed instructions on how to contribute, please refer to the [Contributing](https://docs.pypsa.org/latest/contributing/contributing/) section of our documentation. This includes guidelines for code contributions, documentation improvements, and example submissions.
+
+To handle the influx of AI-assisted contributions, we have established some basic principles.
+See the [AI-based Contributions](https://docs.pypsa.org/latest/contributing/contributing/#ai-based-contributions) section in our documentation for more details.

{pypsa-1.2.0/pypsa.egg-info → pypsa-1.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pypsa
-Version: 1.2.0
+Version: 1.2.2
 Summary: Python for Power Systems Analysis
 Author-email: "PyPSA Developers, see https://docs.pypsa.org/latest/contributing/contributors.html" <t.brown@tu-berlin.de>
 License: MIT License
@@ -42,9 +42,9 @@ License-File: LICENSE
 Requires-Dist: numpy
 Requires-Dist: scipy
 Requires-Dist: pandas>=2.0
-Requires-Dist: xarray<2026.4
+Requires-Dist: xarray
 Requires-Dist: netcdf4
-Requires-Dist: linopy>=0.6.1
+Requires-Dist: linopy>=0.7.0
 Requires-Dist: matplotlib
 Requires-Dist: plotly
 Requires-Dist: pydeck>=0.6
@@ -320,7 +320,7 @@ on [Zenodo](https://zenodo.org/) with a release-specific DOI:
 
 ## Licence
 
-Copyright [PyPSA Contributors](https://docs.pypsa.org/latest/developers.html)
+Copyright [PyPSA Contributors](https://docs.pypsa.org/latest/contributing/contributors/)
 
 PyPSA is licensed under the open source [MIT License](LICENSES/MIT.txt).
 The documentation is licensed under [CC-BY-4.0](LICENSES/CC-BY-4.0.txt).

{pypsa-1.2.0 → pypsa-1.2.2}/README.md

@@ -206,7 +206,7 @@ on [Zenodo](https://zenodo.org/) with a release-specific DOI:
 
 ## Licence
 
-Copyright [PyPSA Contributors](https://docs.pypsa.org/latest/developers.html)
+Copyright [PyPSA Contributors](https://docs.pypsa.org/latest/contributing/contributors/)
 
 PyPSA is licensed under the open source [MIT License](LICENSES/MIT.txt).
 The documentation is licensed under [CC-BY-4.0](LICENSES/CC-BY-4.0.txt).

{pypsa-1.2.0 → pypsa-1.2.2}/docs/contributing/contributing.md

@@ -154,6 +154,24 @@ For simple changes, you can also edit the documentation directly on GitHub:
 2. Make your changes in the file.
 3. Commit your changes and create a pull request.
 
+## AI-based Contributions
+
+We do not impose general restrictions on the use of AI for contributions.
+But we require that all contributions, whether AI-assisted or not, adhere to the same standards of quality, relevance, and maintainability.
+This boils down to:
+
+1. PR and issue descriptions should read like you wrote them. Keep them concise and human. Any potentially verbose AI-generated content should be marked, e.g. in a collapsed `<details>` block. Please don't mix both.
+2. Take responsibility for the content and quality of your contribution, even if you used AI.
+3. Keep the code simple. AI tools often produce verbose or over-engineered code. Review and trim it back before submitting.
+4. Before you submit large contributions, coordinate with the maintainers to ensure they align with the project's goals and roadmap.
+4. Minimize the review burden on us by keeping your contributions focused, don't solve multiple tangential issues in one PR.
+
+We may close AI-based contributions without further review if we consider them to bind up excessive maintainer time.
+
+Why?
+Because the PyPSA project has limited maintainer capacity.
+Let's respect everyone's time and token budget.
+
 ## Examples
 
 Nice examples are always welcome.

{pypsa-1.2.0 → pypsa-1.2.2}/docs/examples/tracing-infeasibilities.ipynb

@@ -167,11 +167,7 @@
    "cell_type": "markdown",
    "id": "d3a8d32d",
    "metadata": {},
-   "source": [
-    "## Tracing the Infeasibility\n",
-    "\n",
-    "When the optimization fails due to infeasibility, PyPSA provides a convenient method to diagnose the problem. The `print_infeasibilities()` method on the optimization model will show us exactly which constraints are causing the infeasibility."
-   ]
+   "source": "## Tracing the Infeasibility\n\nWhen the optimization fails due to infeasibility, PyPSA provides a convenient method to diagnose the problem. The `format_infeasibilities()` method on the optimization model will show us exactly which constraints are causing the infeasibility."
   },
   {
    "cell_type": "code",
@@ -179,34 +175,13 @@
    "id": "4989a457",
    "metadata": {},
    "outputs": [],
-   "source": [
-    "n.model.print_infeasibilities()"
-   ]
+   "source": "print(n.model.format_infeasibilities())"
   },
   {
    "cell_type": "markdown",
    "id": "ee963ad8",
    "metadata": {},
-   "source": [
-    "### Interpreting the Infeasibility Output\n",
-    "\n",
-    "The infeasibility trace above shows us exactly what's wrong:\n",
-    "\n",
-    "1. **`Link-fix-p-lower[2015-01-01 00:00:00, DC link]: +1 Link-p[2015-01-01 00:00:00, DC link] ≥ -0`**\n",
-    "   - This constraint says the DC link power flow must be ≥ 0 (can't flow negative)\n",
-    "   - But we set the DC link capacity to 0, so Link-p value is bounded to 0\n",
-    "\n",
-    "2. **`Bus-nodal_balance[London, 2015-01-01 00:00:00]: -1 Link-p[2015-01-01 00:00:00, DC link] = 35.7962441027`**\n",
-    "   - This is London's nodal balance equation: generation ± trade ± storage = load\n",
-    "   - London has no generation, 35.8 MW load, and no AC interconnectors\n",
-    "   - The DC link (the only remaining connection) can't provide any power because its capacity is 0\n",
-    "\n",
-    "Under the hood, `print_infeasibilities()` uses Gurobi's infeasibility analysis to identify conflicting constraints.\n",
-    " **Irreducible Inconsistent Set (IIS)** identified by Gurobi shows these two constraints are fundamentally incompatible:\n",
-    "- London needs power inflow via the DC link to meet its load\n",
-    "- But the DC link is constrained to zero power\n",
-    "- This creates an impossible situation that no solution can satisfy"
-   ]
+   "source": "### Interpreting the Infeasibility Output\n\nThe infeasibility trace above shows us exactly what's wrong:\n\n1. **`Link-fix-p-lower[2015-01-01 00:00:00, DC link]: +1 Link-p[2015-01-01 00:00:00, DC link] ≥ -0`**\n   - This constraint says the DC link power flow must be ≥ 0 (can't flow negative)\n   - But we set the DC link capacity to 0, so Link-p value is bounded to 0\n\n2. **`Bus-nodal_balance[London, 2015-01-01 00:00:00]: -1 Link-p[2015-01-01 00:00:00, DC link] = 35.7962441027`**\n   - This is London's nodal balance equation: generation ± trade ± storage = load\n   - London has no generation, 35.8 MW load, and no AC interconnectors\n   - The DC link (the only remaining connection) can't provide any power because its capacity is 0\n\nUnder the hood, `format_infeasibilities()` uses Gurobi's infeasibility analysis to identify conflicting constraints.\n **Irreducible Inconsistent Set (IIS)** identified by Gurobi shows these two constraints are fundamentally incompatible:\n- London needs power inflow via the DC link to meet its load\n- But the DC link is constrained to zero power\n- This creates an impossible situation that no solution can satisfy"
   }
  ],
  "metadata": {

{pypsa-1.2.0 → pypsa-1.2.2}/docs/home/features.md

@@ -146,7 +146,7 @@ Interactive **network visualization** of SciGRID example network clustered by fe
 Interactive area plot of **electricity balance time series** in a highly-renewable sector-coupled example network, showing temporal generation (positive values) and consumption (negative values) of different technologies:
 
 <div style="width: 100%; height: 550px;">
-    <iframe src="../../../assets/interactive/carbon_management-energy_balance-area_iplot-AC-bus_carrier.html"
+    <iframe src="../../assets/interactive/carbon_management-energy_balance-area_iplot-AC-bus_carrier.html"
             width="100%" height="100%" frameborder="0" style="border: 0px solid #ccc;">
     </iframe>
 </div>

{pypsa-1.2.0 → pypsa-1.2.2}/docs/home/models.md

@@ -42,6 +42,8 @@ open source and actively maintained. Below is a list of some known models.
 - **[:flag_br: PyPSA-Brazil](https://gitlab.com/dlr-ve/esy/open-brazil-energy-data/open-brazilian-energy-data)**: Brazilian power system model (see [paper](https://doi.org/10.1038/s41597-023-01992-9)), developed by the German Aerospace Center (DLR)
 - **[:flag_ca: PyPSA-BC](https://github.com/DeltaE/PyPSA_BC)**: BC PyPSA work for the PICS Decarbonization project, maintained by Simon Fraser University
 - **[:flag_us: pypsa-illinois](https://github.com/ucsusa/pypsa-illinois)**: Using PyPSA to model the Illinois electricity system for storage requirement analysis maintained by Union of Concerned Scientists (UCS).
+- **[:flag_ar: PyPSA-AR](https://github.com/FTDT-PyPSA/PyPSA-AR)**: Reproducible model of the Argentine high-voltage power grid using PyPSA maintained by Fundación Torcuato Di Tella (FTDT).
+- **[:flag_ca: PyPSA-Canada](https://github.com/NRCan/pypsa-canada)**: used PyPSA for a workflow-based modeling framework for power system analysis in Canada maintained by Natural Resources Canada (NRCan).
 
 ### Africa
 - **[:flag_za: PyPSA-RSA](https://github.com/MeridianEconomics/pypsa-rsa)**: South-African electricity model, maintained by [Meridian Economics](https://meridianeconomics.co.za/)

{pypsa-1.2.0 → pypsa-1.2.2}/docs/home/users.md

@@ -99,6 +99,8 @@ The following universities, research institutes, companies, governmental and non
 
 - **[:flag_us: Union of Concerned Scientists (UCS)](https://www.ucs.org/)**: used PyPSA to assess the storage needs for Illinois electricity system.
 
+- **[:flag_ca: Natural Resources Canada (NRCan)](https://natural-resources.canada.ca/science-data/science-research/research-centres/canmetenergy)**: used PyPSA create a workflow-based modeling framework for power system analysis in Canada.
+
 ## Companies
 
 * **[:flag_de: TransnetBW](https://www.transnetbw.de/)**, the electricity transmission system operator in southwest Germany, **[:flag_de: ONTRAS](https://www.ontras.com/)**, the gas transmission system operator in eastern Germany and **[:flag_de: d-fine](https://www.d-fine.com/)**, a consultancy firm, used PyPSA-Eur-Sec for a study in 2020 of the grid requirements in 2050 with a 90% reduction of carbon dioxide emissions in electricity, buildings and transport, see [Stromnetz 2050](https://www.transnetbw.de/de/stromnetz2050/), for an article in a 2021 issue of Energiewirtschaftliche Tagesfragen [Die Rolle von Wasserstoff in einem klimaneutralen europäischen Energiesystem – eine modellbasierte Analyse bis 2050](https://www.d-fine.com/fileadmin/user_upload/Wasserstoff_et_0102-2021.pdf), and for their 2022 study [Energy System 2050 - Towards a decarbonised Europe](https://www.energysystem2050.net/).
@@ -166,3 +168,5 @@ The following universities, research institutes, companies, governmental and non
 * **[:flag_gb: ClimateXChange](https://www.climatexchange.org.uk/)** commissioned a report for the Scottish Government on [Electricity system security of supply in Scotland](https://www.climatexchange.org.uk/projects/electricity-system-security-of-supply-in-scotland/) using PyPSA-GB.
 
 - **[:flag_kr: PLANiT Institute](https://planit.institute)** A non-profit research institute based in Seoul developed [PyPSA_KR](https://github.com/PLANiT-Institute/PyPSA_KR), a comprehensive power system analysis toolkit for modeling and optimizing electricity networks in South Korea with multi-node network modeling at different granularities, and [pyPPA](https://github.com/PLANiT-Institute/pyPPA), a Power Purchase Agreement modeling and optimization framework for evaluating renewable energy procurement strategies.
+
+- **[:flag_ar: FTDT (Fundación Torcuato Di Tella)](https://ftdt.cc/)** A non-profit research institute based in Argentina developed [PyPSA-AR](https://github.com/FTDT-PyPSA/PyPSA-AR), a comprehensive power system  model of the Argentine high-voltage power grid.

{pypsa-1.2.0 → pypsa-1.2.2}/docs/release-notes.md

@@ -6,13 +6,38 @@ SPDX-License-Identifier: CC-BY-4.0
 
 # Release Notes
 
-<!--## Upcoming Release
+## [**v1.2.2**](https://github.com/PyPSA/PyPSA/releases/tag/v1.2.2) <small>25th May 2026</small> { id="v1.2.2" }
 
+<!--
 !!! info "Upcoming Release"
 
     The features listed below have not yet been released, but will be included in the
     next update! If you would like to use these features in the meantime, you will need
-    to install the `master` branch, e.g. `pip install git+https://github.com/pypsa/pypsa`.-->
+    to install the `master` branch, e.g. `pip install git+https://github.com/pypsa/pypsa`.
+-->
+
+### Bug Fixes
+
+- Fix the sign of [Loads](./user-guide/components/loads.md) not being taken into account in the nodal balance constraint when calling [`n.optimize()`][pypsa.optimization.OptimizationAccessor.__call__]. (<!-- md:pr 1685 -->)
+
+- Fix operational constraints for non-extendable components producing `NaN` bounds when `p_nom` is infinite and `p_min_pu`/`p_max_pu` is zero. The bound now falls back to zero in this case. Relevant for linopy versions `>=0.7` where `NaN` bounds are not dropped explicitly. (<!-- md:pr 1683 -->)
+
+- Lift `xarray<2026.4` upper bound and bump `linopy>=0.7.0` floor. (<!-- md:pr 1686 -->)
+
+
+## [**v1.2.1**](https://github.com/PyPSA/PyPSA/releases/tag/v1.2.1) <small>19th May 2026</small> { id="v1.2.1" }
+
+### Documentation
+
+- Updated our contribution guidelines outline what we expect from AI-based contributions. See [AI-based Contributions](https://docs.pypsa.org/latest/contributing/contributing/#ai-based-contributions) in our documentation for more details. (<!-- md:pr 1672 -->)
+
+### Bug Fixes
+
+- Fix ramp limit constraints leaking another [Generator](./user-guide/components/generators.md)'s `p_nom` variable into the constraint when a component held both fixed and extendable generators. (<!-- md:pr 1677 -->)
+
+- Fix [`n.statistics.transmission()`][pypsa.statistics.StatisticsAccessor.transmission] returning zero flows when `bus_carrier` is set. (<!-- md:pr 1662 -->)
+
+- Fix [`n.add(..., overwrite=True)`][pypsa.Network.add] leaving stale dynamic attributes from the previously existing component, which silently shadowed the new static values at solve time. `overwrite=True` now behaves consistently with [`n.remove(...)`][pypsa.Network.remove] followed by `n.add(...)`. (<!-- md:pr 1666 -->)
 
 
 ## [**v1.2.0**](https://github.com/PyPSA/PyPSA/releases/tag/v1.2.0) <small>21st April 2026</small> { id="v1.2.0" }

{pypsa-1.2.0 → pypsa-1.2.2}/docs/requirements.txt

@@ -13,7 +13,7 @@ babel==2.18.0
     # via
     #   mkdocs-git-revision-date-localized-plugin
     #   mkdocs-material
-backrefs==6.2
+backrefs==7.0
     # via mkdocs-material
 beautifulsoup4==4.14.3
     # via nbconvert
@@ -27,7 +27,7 @@ cairosvg==2.9.0
     # via pypsa
 cartopy==0.25.0
     # via pypsa
-certifi==2026.2.25
+certifi==2026.4.22
     # via
     #   netcdf4
     #   pyogrio
@@ -36,13 +36,12 @@ certifi==2026.2.25
 cffi==2.0.0
     # via
     #   cairocffi
-    #   cryptography
     #   pyzmq
 cftime==1.6.5
     # via netcdf4
 charset-normalizer==3.4.7
     # via requests
-click==8.3.2
+click==8.4.0
     # via
     #   dask
     #   mkdocs
@@ -62,8 +61,6 @@ comm==0.2.3
     # via ipykernel
 contourpy==1.3.3
     # via matplotlib
-cryptography==46.0.7
-    # via google-auth
 cssselect2==0.9.0
     # via cairosvg
 cycler==0.12.1
@@ -72,7 +69,7 @@ dask==2026.3.0
     # via linopy
 debugpy==1.8.20
     # via ipykernel
-decorator==5.2.1
+decorator==5.3.1
     # via ipython
 defusedxml==0.7.1
     # via
@@ -90,9 +87,9 @@ executing==2.2.1
     # via stack-data
 fastjsonschema==2.21.2
     # via nbformat
-fonttools==4.62.1
+fonttools==4.63.0
     # via matplotlib
-fsspec==2026.3.0
+fsspec==2026.4.0
     # via dask
 geopandas==1.1.3
     # via pypsa
@@ -102,38 +99,17 @@ ghp-import==2.1.0
     #   properdocs
 gitdb==4.0.12
     # via gitpython
-gitpython==3.1.46
+gitpython==3.1.50
     # via mkdocs-git-revision-date-localized-plugin
-google-api-core==2.30.3
-    # via
-    #   google-cloud-core
-    #   google-cloud-storage
-google-auth==2.49.2
-    # via
-    #   google-api-core
-    #   google-cloud-core
-    #   google-cloud-storage
-google-cloud-core==2.5.1
-    # via google-cloud-storage
-google-cloud-storage==3.10.1
-    # via linopy
-google-crc32c==1.8.0
-    # via
-    #   google-cloud-storage
-    #   google-resumable-media
-google-resumable-media==2.8.2
-    # via google-cloud-storage
-googleapis-common-protos==1.74.0
-    # via google-api-core
 griffelib==2.0.2
     # via mkdocstrings-python
-gurobipy==13.0.1
+gurobipy==13.0.2
     # via pypsa
-highspy==1.13.1
+highspy==1.14.0
     # via
     #   pypsa
     #   tsam
-idna==3.12
+idna==3.15
     # via requests
 importlib-metadata==9.0.0 ; python_full_version < '3.12'
     # via dask
@@ -141,13 +117,11 @@ iniconfig==2.3.0
     # via pytest
 ipykernel==7.2.0
     # via mkdocs-jupyter
-ipython==9.10.1 ; python_full_version < '3.12'
-    # via ipykernel
-ipython==9.12.0 ; python_full_version >= '3.12'
+ipython==9.13.0
     # via ipykernel
 ipython-pygments-lexers==1.1.1
     # via ipython
-jedi==0.19.2
+jedi==0.20.0
     # via ipython
 jinja2==3.1.6
     # via
@@ -176,17 +150,17 @@ jupyter-core==5.9.1
     #   nbformat
 jupyterlab-pygments==0.3.0
     # via nbconvert
-jupytext==1.19.1
+jupytext==1.19.3
     # via mkdocs-jupyter
 kiwisolver==1.5.0
     # via matplotlib
 levenshtein==0.27.3
     # via pypsa
-linopy==0.6.7
+linopy==0.7.0
     # via pypsa
 locket==1.0.0
     # via partd
-lxml==6.1.0
+lxml==6.1.1
     # via mkdocs-video
 markdown==3.10.2
     # via
@@ -196,7 +170,7 @@ markdown==3.10.2
     #   mkdocstrings
     #   properdocs
     #   pymdown-extensions
-markdown-it-py==4.0.0
+markdown-it-py==4.2.0
     # via
     #   jupytext
     #   mdit-py-plugins
@@ -208,17 +182,17 @@ markupsafe==3.0.3
     #   mkdocstrings
     #   nbconvert
     #   properdocs
-matplotlib==3.10.8
+matplotlib==3.10.9
     # via
     #   cartopy
     #   pypsa
     #   salib
     #   seaborn
-matplotlib-inline==0.2.1
+matplotlib-inline==0.2.2
     # via
     #   ipykernel
     #   ipython
-mdit-py-plugins==0.5.0
+mdit-py-plugins==0.6.1
     # via jupytext
 mdurl==0.1.2
     # via markdown-it-py
@@ -226,7 +200,7 @@ mergedeep==1.3.4
     # via
     #   mkdocs
     #   mkdocs-get-deps
-mistune==3.2.0
+mistune==3.2.1
     # via nbconvert
 mkdocs==1.6.1
     # via
@@ -250,7 +224,7 @@ mkdocs-ezlinks-plugin==0.1.14
     # via pypsa
 mkdocs-get-deps==0.2.2
     # via mkdocs
-mkdocs-git-revision-date-localized-plugin==1.5.1
+mkdocs-git-revision-date-localized-plugin==1.5.2
     # via pypsa
 mkdocs-jupyter==0.26.3
     # via pypsa
@@ -272,7 +246,7 @@ mkdocstrings-python==2.0.3
     # via pypsa
 multiprocess==0.70.19
     # via salib
-narwhals==2.20.0
+narwhals==2.21.2
     # via plotly
 nbclient==0.10.4
     # via nbconvert
@@ -293,7 +267,7 @@ networkx==3.6.1
     #   tsam
 numexpr==2.14.1
     # via linopy
-numpy==2.4.4
+numpy==2.4.6
     # via
     #   bottleneck
     #   cartopy
@@ -348,11 +322,11 @@ pandas==2.3.3
     #   xarray
 pandocfilters==1.5.1
     # via nbconvert
-parso==0.8.6
+parso==0.8.7
     # via jedi
 partd==1.4.2
     # via dask
-pathspec==1.0.4
+pathspec==1.1.1
     # via
     #   mkdocs
     #   properdocs
@@ -373,31 +347,22 @@ plotly==6.7.0
     # via pypsa
 pluggy==1.6.0
     # via pytest
-polars==1.40.0
+polars==1.40.1
     # via linopy
-polars-runtime-32==1.40.0
+polars-runtime-32==1.40.1
     # via polars
 prompt-toolkit==3.0.52
     # via ipython
 properdocs==1.6.7
     # via mkdocs-redirects
-proto-plus==1.27.2
-    # via google-api-core
-protobuf==7.34.1
-    # via
-    #   google-api-core
-    #   googleapis-common-protos
-    #   proto-plus
 psutil==7.2.2
-    # via ipykernel
+    # via
+    #   ipykernel
+    #   ipython
 ptyprocess==0.7.0 ; sys_platform != 'emscripten' and sys_platform != 'win32'
     # via pexpect
 pure-eval==0.2.3
     # via stack-data
-pyasn1==0.6.3
-    # via pyasn1-modules
-pyasn1-modules==0.4.2
-    # via google-auth
 pycparser==3.0 ; implementation_name != 'PyPy'
     # via cffi
 pydeck==0.9.2
@@ -412,7 +377,7 @@ pygments==2.20.0
     #   pytest
 pygtrie==2.5.0
     # via mkdocs-ezlinks-plugin
-pymdown-extensions==10.21.2
+pymdown-extensions==10.21.3
     # via
     #   mkdocs-material
     #   mkdocstrings
@@ -426,7 +391,7 @@ pyproj==3.7.2
     # via
     #   cartopy
     #   geopandas
-pyshp==3.0.3
+pyshp==3.0.5
     # via cartopy
 pytest==9.0.3
     # via pypsa
@@ -438,7 +403,7 @@ python-dateutil==2.9.0.post0
     #   jupyter-client
     #   matplotlib
     #   pandas
-pytz==2026.1.post1
+pytz==2026.2
     # via pandas
 pyyaml==6.0.3
     # via
@@ -464,12 +429,8 @@ referencing==0.37.0
     # via
     #   jsonschema
     #   jsonschema-specifications
-requests==2.33.1
-    # via
-    #   google-api-core
-    #   google-cloud-storage
-    #   linopy
-    #   mkdocs-material
+requests==2.34.2
+    # via mkdocs-material
 rpds-py==0.30.0
     # via
     #   jsonschema
@@ -521,7 +482,7 @@ tqdm==4.67.3
     # via
     #   linopy
     #   tsam
-traitlets==5.14.3
+traitlets==5.15.0
     # via
     #   ipykernel
     #   ipython
@@ -531,18 +492,18 @@ traitlets==5.14.3
     #   nbclient
     #   nbconvert
     #   nbformat
-tsam==3.3.0
+tsam==2.3.9
     # via pypsa
 typing-extensions==4.15.0
     # via
     #   beautifulsoup4
     #   ipython
     #   referencing
-tzdata==2026.1
+tzdata==2026.2
     # via
     #   mkdocs-git-revision-date-localized-plugin
     #   pandas
-urllib3==2.6.3
+urllib3==2.7.0
     # via requests
 validators==0.35.0
     # via pypsa
@@ -550,7 +511,7 @@ watchdog==6.0.0
     # via
     #   mkdocs
     #   properdocs
-wcwidth==0.6.0
+wcwidth==0.7.0
     # via prompt-toolkit
 webencodings==0.5.1
     # via
@@ -561,5 +522,5 @@ xarray==2026.2.0
     # via
     #   linopy
     #   pypsa
-zipp==3.23.1 ; python_full_version < '3.12'
+zipp==4.1.0 ; python_full_version < '3.12'
     # via importlib-metadata

{pypsa-1.2.0 → pypsa-1.2.2}/pyproject.toml

@@ -33,9 +33,9 @@ dependencies = [
     "numpy",
     "scipy",
     "pandas>=2.0",
-    "xarray<2026.4",  # See https://github.com/PyPSA/linopy/pull/647
+    "xarray",
     "netcdf4",
-    "linopy>=0.6.1",
+    "linopy>=0.7.0",
     "matplotlib",
     "plotly",
     "pydeck>=0.6",

{pypsa-1.2.0 → pypsa-1.2.2}/pypsa/components/types.py

@@ -27,7 +27,7 @@ _standard_types_path = Path(__file__).parent.parent / "data" / "standard_types"
 component_types_df = pd.read_csv(_components_path, index_col=0)
 default_components = component_types_df.index.to_list()
 
-all_components = {}
+all_components: dict[str, ComponentType] = {}
 
 
 def add_component_type(