Feature #461 move to pyproject.toml

[John-Sharples]

• Remove existing setup.py and replace with pyproject.toml
• move pytest and coverage config into pyproject.toml
• update documentation
• coverage report updated to ignore contributed plots

Note a change in behaviour: pip install . will now install ALL DEPENDANCIES as well as METplotpy. See docs for ways to avoid this.

Pull Request Testing

• Describe testing already performed for these changes:
  
  tested local builds

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Confirm docs make sense and result in correct installation.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes or No]
  Yes

• Do these changes include sufficient testing updates? [Yes or No]
  NA

• Will this PR result in changes to the test suite? [Yes or No]
  
  If yes, describe the new output and/or changes to the existing output:
  
  No

• Do these changes introduce new SonarQube findings? [Yes or No]
  
  If yes, please describe:
  No

• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Add any new Python packages to the METplus Components Python Requirements table.
• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the version that will include these changes
  Select: Coordinated METplus-X.Y Support project for bugfix releases or METplotpy-X.Y.Z Development project for official releases
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[georgemccabe]

We have technically deprecated the use of the email address [email protected] in favor of having users create new GitHub Discussion topics. @JohnHalleyGotway, is there another email address that can be used here? If not, perhaps we should create a Google Group that includes METplus support team members that can be included in python package info.

[bikegeek]

It looks like we are still getting emails when users (and spammers) send email to the ***@***.*** address...

…

On Wed, Sep 18, 2024 at 3:40 PM George McCabe ***@***.***> wrote: We have technically deprecated the use of the email address ***@***.*** in favor of having users create new GitHub Discussion topics. @JohnHalleyGotway <https://github.com/JohnHalleyGotway>, is there another email address that can be used here? If not, perhaps we should create a Google Group that includes METplus support team members that can be included in python package info. — Reply to this email directly, view it on GitHub <#462 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4UJHSBRG7VIX2RJXBBOB3ZXHXMTAVCNFSM6AAAAABOOOJQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJZGQ2TGMRZGM> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[John-Sharples]

We can just remove the email from pyproject.toml. I don't think it's required... I just copied from the existing setup.py