Dealing with an existing MetPy installation

[winash12]

As explained in this URL - https://unidata.github.io/MetPy/latest/devel/CONTRIBUTING.html I have forked and cloned my forked repository to my local desktop. I will be making changes to this repository in order to make a pull request.

Now in my desktop I already have an existing MetPy installation. What should I do with that one ? Should I delete that egg file on that installation and install this cloned repository and then start making changes to the source code ?

[dopplershift]

Yes, I would do:

pip uninstall metpy
pip install -e .

from within the source checkout.

[dcamron]

To supplement, we also strongly recommend the use of virtual environments, such as with conda env, so that you can have multiple totally separate installs of MetPy without interfering with one-another.

[winash12]

Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'done'
ERROR: Package 'MetPy-0.0.post5779-ge149219' requires a different Python: 3.8.10 not in '>=3.9'

I am getting this error when I do a pip3 install. I want to be able to install with 3.8 not 3.9 although both are in my environment. How can I do that ?

https://stackoverflow.com/questions/61863309/package-requires-a-different-python-2-7-17-not-in-3-6-1-while-setting-up-pr Is this the solution ?

[dopplershift]

MetPy 1.5.1 was the last release that supports Python 3.8, so there's no way to run the current MetPy main branch on Python 3.9. While you are of course welcome to continue using Python 3.8 and MetPy 1.5.1, any contributions will need to be on the main branch and tested using Python >=3.9.

[winash12]

I have managed to get it working with python3.9. So where does one add the new modifications to the code ? Is it the kinematics.py file in the calc module ?

[dopplershift]

It depends on what you're trying to add. If this is related to the wind field decomposition from vorticity & divergence, then yes, kinematics.py seems appropriate.