Skip to content

Substitute setup.py with pyproject.toml#41

Merged
ammarcsj merged 30 commits into
masterfrom
substitute_setup_py
Feb 14, 2025
Merged

Substitute setup.py with pyproject.toml#41
ammarcsj merged 30 commits into
masterfrom
substitute_setup_py

Conversation

@ammarcsj
Copy link
Copy Markdown
Member

in progress

@ammarcsj ammarcsj changed the base branch from master to add_bump_version_workflow February 12, 2025 15:04
Comment thread pyproject.toml Outdated

[project.urls]

"Paper" = "https://doi.org/10.1016/j.mcpro.2023.100581"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

maybe comment our for now ;-)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

👍

Comment thread pyproject.toml
optional-dependencies = { stable = { file = ["requirements/requirements.txt",
] }, gui = { file = [ "requirements/requirements_gui_loose.txt",
] }, gui-stable = { file = [ "requirements/requirements_gui.txt",
] }, tests = { file = [ "requirements/requirements_tests.txt",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

requirements_tests.txt does not exists.. the idea is that this collects all dependencies that are used for testing, e.g. pytest (and that alphaquant[..., tests] is used for testing rather than alphaquant[..., development]) .. currently this is done here run_unittests.sh

either add that file of remove it from here

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

👍 overlooked this, added requirements_tests.txt, however, where is it set which environment is used? Should I adapt it in the run_unittests.sh?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@@ -0,0 +1,131 @@
"""Test that the strict and loose requirements files are aligned."""
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

did you check that this test is run in the CI?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Hmm I did not see it run in CI in directlfq, I thought the alphashared does that for the release. Would you recommend having a dedicated CI test for this?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it's a matter of pytest discovery,
currently you have in run_tests.sh

cd unit_tests
python -m pytest -v
cd ..

which renders the pytests folder 'invisible' for pytest ..

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

could just move test_req..py to unit_tests?

Comment thread requirements/requirements.txt Outdated
@@ -16,5 +16,4 @@ openpyxl==3.1.5
scikit-learn==1.5.2
alphabase==1.4.0
matplotlib-venn==1.1.1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

looks like some of these could go to requirements_gui.txt?

Base automatically changed from add_bump_version_workflow to master February 14, 2025 11:02
@ammarcsj ammarcsj marked this pull request as ready for review February 14, 2025 11:03
@ammarcsj ammarcsj merged commit 4dc9786 into master Feb 14, 2025
@ammarcsj ammarcsj deleted the substitute_setup_py branch February 14, 2025 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants