Skip to content

Add py-mlflow and its dependencies#34463

Merged
tldahlgren merged 22 commits intospack:developfrom
heerener:add-py-mlflow
Feb 16, 2023
Merged

Add py-mlflow and its dependencies#34463
tldahlgren merged 22 commits intospack:developfrom
heerener:add-py-mlflow

Conversation

@heerener
Copy link
Copy Markdown
Contributor

No description provided.

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 12, 2022

Hi @heerener! I noticed that the following package(s) don't yet have maintainers:

  • py-databricks-cli
  • py-gunicorn
  • py-mlflow
  • py-prometheus-flask-exporter
  • py-querystring-parser

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers = ["heerener"]

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame py-databricks-cli

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

Copy link
Copy Markdown
Contributor

@tldahlgren tldahlgren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ending year for the copyright for each package needs to be corrected (2020->2022). More importantly, there is a typo for py-databricks-cli pypi value.

@tldahlgren tldahlgren self-assigned this Dec 12, 2022
@tldahlgren
Copy link
Copy Markdown
Contributor

You'll also need to replace single quotes with double to pass the black checks.

@adamjstewart adamjstewart self-assigned this Dec 12, 2022
Copy link
Copy Markdown
Member

@adamjstewart adamjstewart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style tests (single quotes instead of double quotes) can be fixed with spack style --fix -t black on the command line or @spackbot fix style on this PR. There's also a way to automatically update the licenses but I don't remember it.

Process review remarks, add missing dependencies, add skinny variant
Co-authored-by: Tamara Dahlgren <[email protected]>
Co-authored-by: Adam J. Stewart <[email protected]>
@heerener
Copy link
Copy Markdown
Contributor Author

@spackbot fix style

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 13, 2022

Let me see if I can fix that for you!

@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Dec 13, 2022

I was able to run spack style --fix for you!

spack style --fix
==> Running style checks on spack
  selected: isort, mypy, black, flake8
==> Modified files
  var/spack/repos/builtin/packages/py-databricks-cli/package.py
  var/spack/repos/builtin/packages/py-gunicorn/package.py
  var/spack/repos/builtin/packages/py-importlib-metadata/package.py
  var/spack/repos/builtin/packages/py-mlflow/package.py
  var/spack/repos/builtin/packages/py-prometheus-flask-exporter/package.py
  var/spack/repos/builtin/packages/py-pyarrow/package.py
  var/spack/repos/builtin/packages/py-querystring-parser/package.py
  var/spack/repos/builtin/packages/py-shap/package.py
  var/spack/repos/builtin/packages/py-waitress/package.py
==> Running isort checks
  isort checks were clean
==> Running mypy checks
lib/spack/llnl/util/lang.py:1064: note: By default the bodies of untyped functions are not checked, consider using --check-untyped-defs  [annotation-unchecked]
lib/spack/spack/util/timer.py:68: note: By default the bodies of untyped functions are not checked, consider using --check-untyped-defs  [annotation-unchecked]
lib/spack/spack/build_environment.py:291: note: By default the bodies of untyped functions are not checked, consider using --check-untyped-defs  [annotation-unchecked]
lib/spack/spack/bootstrap/_common.py:52: note: By default the bodies of untyped functions are not checked, consider using --check-untyped-defs  [annotation-unchecked]
Success: no issues found in 571 source files
  mypy checks were clean
==> Running black checks
reformatted var/spack/repos/builtin/packages/py-gunicorn/package.py
reformatted var/spack/repos/builtin/packages/py-prometheus-flask-exporter/package.py
reformatted var/spack/repos/builtin/packages/py-querystring-parser/package.py
reformatted var/spack/repos/builtin/packages/py-shap/package.py
reformatted var/spack/repos/builtin/packages/py-mlflow/package.py
All done! ✨ 🍰 ✨
5 files reformatted, 4 files left unchanged.
  black checks were clean
==> Running flake8 checks
var/spack/repos/builtin/packages/py-mlflow/package.py:21: [E501] line too long (112 > 99 characters)
var/spack/repos/builtin/packages/py-shap/package.py:10: [E501] line too long (119 > 99 characters)
  flake8 found errors
Keep in mind that I cannot fix your flake8 or mypy errors, so if you have any you'll need to fix them and update the pull request. If I was able to push to your branch, if you make further changes you will need to pull from your updated branch before pushing again.

I've updated the branch with style fixes.

adamjstewart
adamjstewart previously approved these changes Jan 3, 2023
It appears there are some issues when using `pip install` instead of
`python setup.py` - this setup_build_environment should fix that.
@thomas-bouvier
Copy link
Copy Markdown
Member

For reference, I was working on adding package [email protected] there #35068 but stumbled upon difficulties related to the +parquet variant.

@adamjstewart
Copy link
Copy Markdown
Member

Need to resolve merge conflicts

adamjstewart
adamjstewart previously approved these changes Jan 30, 2023
@heerener
Copy link
Copy Markdown
Contributor Author

heerener commented Feb 3, 2023

I noticed that the licenses were still set to 2022.
@tldahlgren , github tells me you still have one open change request, but I'm not sure what it is / how to mark it as resolved.

@thomas-bouvier
Copy link
Copy Markdown
Member

thomas-bouvier commented Feb 7, 2023

@spackbot run pipeline

Copy link
Copy Markdown
Contributor

@tldahlgren tldahlgren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-confirmed all affected version sha256.

@tldahlgren
Copy link
Copy Markdown
Contributor

I noticed that the licenses were still set to 2022.
@tldahlgren , github tells me you still have one open change request, but I'm not sure what it is / how to mark it as resolved.

Last I heard Spack may be getting rid of the copyright year so this doesn't have to be changed every year.

Looks like @adamjstewart addressed the change request issue and has since approved the PR.

@tldahlgren tldahlgren merged commit bfe06f6 into spack:develop Feb 16, 2023
@heerener heerener deleted the add-py-mlflow branch February 17, 2023 08:41
techxdave pushed a commit to Tech-XCorp/spack that referenced this pull request Feb 17, 2023
* Add py-mlflow and its dependencies
* mlflow: fix syntax error in package.py
* py-mlflow: cleanup
  Process review remarks, add missing dependencies, add skinny variant
* Apply suggestions from code review
* Fix flake8 issues
* More formatting fixes
* Fix py-waitress dependency version
* py-mlflow: platform-specific dependency
* Update var/spack/repos/builtin/packages/py-mlflow/package.py
* Update var/spack/repos/builtin/packages/py-mlflow/package.py
* Process review remarks
* Fix typo in dependency version
* py-shap: fix dependencies
* py-arrow: fix dependencies
* py-slicer: remove py-setuptools explicit version
* py-pyarrow: dataset variant and pass options through environment
  It appears there are some issues when using `pip install` instead of
  `python setup.py` - this setup_build_environment should fix that.
* py-pyarrow: review remark
* Decouple setup_build_environment from install_options
* py-pyarrow: style
* Bump licenses to 2023

---------

Co-authored-by: Tamara Dahlgren <[email protected]>
Co-authored-by: Adam J. Stewart <[email protected]>
Co-authored-by: Matthias Wolf <[email protected]>
koysean pushed a commit to koysean/spack that referenced this pull request Feb 20, 2023
* Add py-mlflow and its dependencies
* mlflow: fix syntax error in package.py
* py-mlflow: cleanup
  Process review remarks, add missing dependencies, add skinny variant
* Apply suggestions from code review
* Fix flake8 issues
* More formatting fixes
* Fix py-waitress dependency version
* py-mlflow: platform-specific dependency
* Update var/spack/repos/builtin/packages/py-mlflow/package.py
* Update var/spack/repos/builtin/packages/py-mlflow/package.py
* Process review remarks
* Fix typo in dependency version
* py-shap: fix dependencies
* py-arrow: fix dependencies
* py-slicer: remove py-setuptools explicit version
* py-pyarrow: dataset variant and pass options through environment
  It appears there are some issues when using `pip install` instead of
  `python setup.py` - this setup_build_environment should fix that.
* py-pyarrow: review remark
* Decouple setup_build_environment from install_options
* py-pyarrow: style
* Bump licenses to 2023

---------

Co-authored-by: Tamara Dahlgren <[email protected]>
Co-authored-by: Adam J. Stewart <[email protected]>
Co-authored-by: Matthias Wolf <[email protected]>
jmcarcell pushed a commit to key4hep/spack that referenced this pull request Apr 13, 2023
* Add py-mlflow and its dependencies
* mlflow: fix syntax error in package.py
* py-mlflow: cleanup
  Process review remarks, add missing dependencies, add skinny variant
* Apply suggestions from code review
* Fix flake8 issues
* More formatting fixes
* Fix py-waitress dependency version
* py-mlflow: platform-specific dependency
* Update var/spack/repos/builtin/packages/py-mlflow/package.py
* Update var/spack/repos/builtin/packages/py-mlflow/package.py
* Process review remarks
* Fix typo in dependency version
* py-shap: fix dependencies
* py-arrow: fix dependencies
* py-slicer: remove py-setuptools explicit version
* py-pyarrow: dataset variant and pass options through environment
  It appears there are some issues when using `pip install` instead of
  `python setup.py` - this setup_build_environment should fix that.
* py-pyarrow: review remark
* Decouple setup_build_environment from install_options
* py-pyarrow: style
* Bump licenses to 2023

---------

Co-authored-by: Tamara Dahlgren <[email protected]>
Co-authored-by: Adam J. Stewart <[email protected]>
Co-authored-by: Matthias Wolf <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants