Pymatgen

Latest version: v2024.5.1

Safety actively analyzes 630094 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 14 of 59

2022.0.2

Not secure
* Bug fix release for missing package data files in v2022.0.1

2022.0.1

Not secure
* `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.

2022.0.0

Not secure
* 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.

2021.3.5

Not secure
* 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.

2021.3.4

Not secure
* **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'

This should resolve most import errors and only a few more modifications may
need to be done by hand.

Specifically, the following "convenience imports" have been removed in favor of
their canonical import::

from pymatgen import Composition now "from pymatgen.core.composition import Composition"
from pymatgen import Lattice now "from pymatgen.core.lattice import Lattice"
from pymatgen import SymmOp now "from pymatgen.core.operations import SymmOp"
from pymatgen import DummySpecie, DummySpecies, Element, Specie, Species now "from pymatgen.core.periodic_table ..."
from pymatgen import PeriodicSite, Site now "from pymatgen.core.sites ..."
from pymatgen import IMolecule, IStructure, Molecule, Structure now "from pymatgen.core.structure ..."
from pymatgen import ArrayWithUnit, FloatWithUnit, Unit now "from pymatgen.core.units ..."
from pymatgen import Orbital, Spin now "from pymatgen.electronic_structure.core ..."
from pymatgen import MPRester now "from pymatgen.ext.matproj ..."

2021.3.3

Not secure
* **Backwards incompatible**: pymatgen.SETTINGS have been moved to
pymatgen.settings.SETTINGS. In general, this should not lead to many breakages
since most of these settings are used within pymatgen itself.
* **Backwards incompatible**: pymatgen.loadfn and get_structure_from_mp have been
removed since no one was using them.
* critic2_caller has been refactored. (samblau)
* Improved hash for Composition (CompRhys)
* Fixes Outcar parsing for VASP 6.2.0. (MichaelWolloch)
* Allow None for Gaussian functional, bset, charge and multiplicity (eimrek)

Page 14 of 59

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.