setup: add all executable modules as entry_points/console_scripts

[jhkennedy]

Description of proposed changes

This add all currently executable modules as console_scripts entry_points in setup.py, addressing Task 3 in #652 and (I think) finished off #497. This comment gives a detailed explination of how entrypoints work, and how it changes develoment workflows.

*I have not extensively tested these scripts beyond making sure arguments are passed through appropriately and all can be called with --help.

Note: I've not added tropo_pyaps.py as I believe it's a legacy script that's been superseded by tropo_pyaps3.py.

Other thoughts:

• It might be worth rearranging the setup.py file (e.g., move the packages and entry_points arguments to the bottom)

Reminders

• Pass Codacy code review (green)
• Pass Circle CI test (green)
• Make sure that your code follows our style. Use the other functions/files as a basis.
• If modifying functionality, describe changes to function behavior and arguments in a comment below the function declaration.
• If adding new functionality, add a detailed description to the documentation and/or an example.

[welcome]

💖 Thanks for opening this pull request! Please check out our contributing guidelines. 💖
Keep in mind that all new features should be documented. It helps to write the comments next to the code or below your functions describing all arguments, and return types before writing the code. This will help you think about your code design and usually results in better code.

[jhkennedy]

Oh, I also have not addressed any installation, etc. type documentation -- that could be addressed here, or in conjunction with documentation about conda-forge after this has been vetted more.

[yunjunz]

It might be worth rearranging the setup.py file (e.g., move the packages and entry_points arguments to the bottom)

Sounds good to me, please do it as you see fit.

[yunjunz]

Oh, I also have not addressed any installation, etc. type documentation -- that could be addressed here, or in conjunction with documentation about conda-forge after this has been vetted more.

Yep, there will be big (good) changes in the installation. I would prefer to do it in another PR when conda-forge is ready and this PR is tested more as you said.

[jhkennedy]

It might be worth rearranging the setup.py file (e.g., move the packages and entry_points arguments to the bottom)

Sounds good to me, please do it as you see fit.

Done!

[yunjunz]

Looks all good to me. I will do more testings on the weekend before merging it. Thank you @jhkennedy!

[yunjunz]

I installed and tested mintpy as below on macOS. Everything looks good to me.

# download
cd ~/tools
git clone https://github.com/insarlab/MintPy.git
# install
conda create --name test
conda activate test
conda install --file tools/MintPy/docs/requirements.txt pysolid pyaps3 gdal">=3"
cd ~/tools/MintPy
python setup.py install
# test
python ~/tools/MintPy/tests/test_smallbaselineApp.py

[welcome]

🎉 🎉 🎉 Congrats on merging your first pull request! We here at behaviorbot are proud of you! 🎉 🎉 🎉

[jhkennedy]

@yunjunz Just a note -- python -m pip install should be preferred over python setup.py install as setup.py invokes the old and depreciated egg protocol.

[yunjunz]

Good to know, thanks.