Bump pymatgen from 2020.01.28 to 2022.0.5

[dependabot-preview[bot]]

Bumps pymatgen from 2020.01.28 to 2022.0.5.

Release notes

Sourced from pymatgen's releases.

v2022.0.5

• Bug fix to remove possibility of duplicate edges in StructureGraph (@mkhorton, #2095)

v2022.0.4

• Element now has ionization_energies, ionization_energy and electron_affinity properties.
• Extensive documentation has been added on pymatgen compatibility and the new namespace architecture! We have also released a

v2022.0.3

• Another bug fix release! Now SETTINGS have been moved to pymatgen.core.

v2022.0.2

• pymatgen, pymatgen.ext, pymatgen.io and pymatgen.analysis are now namespace packages. Note that this does not affect normal usage of pymatgen from v2022.0.0. All imports remain the same. However, it does allow developers

Namespace package version

pymatgen, pymatgen.ext, pymatgen.io and pymatgen.analysis are now namespace packages. Note that this does not affect normal usage of pymatgen from v2022.0.0. All imports remain the same. However, it does allow developers to write "add-ons" to these subpackages. A full documentation with examples and templates is in the works to guide developers on how to write these packages.

Namespace package version

• Remove root-level imports in preparation for a transition to a namespace packaging system for pymatgen.

Backport of 2022.0.4

• Element now has ionization_energies, ionization_energy and electron_affinity properties.
• Minor reorganization (backwards compatible) of SETTINGS file to make it consistent with 2022.0.x to aid transition.

v2021.3.5

• Reverts breaking change of removing root imports introduced in version 2021.3.4.

v2021.3.4

• Backwards incompatible Pymatgen root imports have been removed from v2021.3.4 in preparation for a change to a more modular, extensible architecture that will allow more developers to contribute. If your existing code uses from pymatgen import <something>, you will need to make modifications. The easiest way is to use an IDE to run a Search and Replace. First, replace any from pymatgen import MPRester with from pymatgen.ext.matproj import MPRester. Then, replace from pymatgen import with from pymatgen.core import. Alternative, if you are using a Mac command line, you can do::

v2021.3.3

• *Backwards incompatible: pymatgen.SETTINGS have been moved to pymatgen.settings.SETTINGS. In general, this should not lead to many breakages

... (truncated)

Changelog

Sourced from pymatgen's changelog.

v2022.0.5

• Bug fix to remove possibility of duplicate edges in StructureGraph (@mkhorton, #2095)

v2022.0.4 / v2021.3.9

• Element now has ionization_energies, ionization_energy and electron_affinity properties.
• Extensive documentation has been added on pymatgen compatibility and the new namespace architecture! We have also released a template repo to help new developers write add-ons for pymatgen! Check out our contributing page</contributing> for details.

v2022.0.3

• Another bug fix release! Now SETTINGS have been moved to pymatgen.core.

v2022.0.2 (Yanked)

• Bug fix release for missing package data files in v2022.0.1

v2022.0.1 (Yanked)

• pymatgen, pymatgen.ext, pymatgen.io and pymatgen.analysis are now namespace packages. Note that this does not affect normal usage of pymatgen from v2022.0.0. All imports remain the same. However, it does allow developers to write "add-ons" to these subpackages. A full documentation with examples and templates is in the works to guide developers on how to write these packages.

v2022.0.0 (Yanked)

• This is the new version of pymatgen going forward. Root-level imports have been removed. Please see https://pymatgen.org/compatibility.html on how to update your code for compatibility with v2022.

v2021.3.5

• Backwards incompatible changes in v2021.3.4 have been removed. Instead another semantic version v2022.0.0 has been released. Future critical bug fixes will be backported to v2021.x.x, but the main line of development will occur on v2022.0.0 onwards.

v2021.3.4 (Yanked)

• Backwards incompatible: Pymatgen root imports have been removed from v2021.3.4 in preparation for a change to a more modular, extensible architecture that will allow more developers to contribute.

  If your existing code uses from pymatgen import <something>, you will need to make modifications. The easiest way is to use an IDE to run a Search and Replace. First, replace any from pymatgen import MPRester with from pymatgen.ext.matproj import MPRester. Then, replace from pymatgen import with from pymatgen.core import. Alternatively, if you are using a Mac command line, you can do:

  find . -name '*.py' | xargs sed -i "" 's/from pymatgen import MPRester/from pymatgen.ext.matproj import MPRester/g'
  find . -name '*.py' | xargs sed -i "" 's/from pymatgen import/from pymatgen.core import/g'
  

  From a Linux command line, you can do:

  find . -name '*.py' | xargs sed -i 's/from pymatgen import MPRester/from pymatgen.ext.matproj import MPRester/g'
  find . -name '*.py' | xargs sed -i 's/from pymatgen import/from pymatgen.core import/g'
  

... (truncated)

Commits

• 9de86c8 Update version
• e5c543a Merge pull request #2095 from materialsproject/graph-improvements
• 528ca07 Re-run black
• 732622f Add convention to remove duplicate hops when i==j + test
• ac8f65e Fix source code links in docs. Fixs #2093.
• fe84423 Update flake8
• c60b95c Run black on phase diagrma.
• 56288c2 Merge branch 'master' of github.com:materialsproject/pymatgen
• 1361e8c Remove verbose doc and add windows to wheel generation
• e4abbff Add back PhaseDiagramError
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #387.