Skip to content

Conversation

@sverhoeven
Copy link
Member

@sverhoeven sverhoeven commented Sep 16, 2025

Checklist before requesting a review

  • I have read the contribution guidelines
  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • All user facing changes have been added to CHANGELOG.md

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

List of related issues or pull requests**

Refs:

Describe the changes made in this pull request

Adds Typing choice and type checker question:

copier-cq copier-tc

Instructions to review the pull request

Install the requirements

cd $(mktemp -d --tmpdir py-tmpl-XXXXXX)
pip install pipx
pipx install copier

Create a new package using the template

copier copy --vcs-ref typing https://github.com/nlesc/python-template test_package

Create a local git repo to push to GitHub to trigger CI actions

git init
git add --all
git commit -m "First commit"
git remote add origin git@github.com:<YOU>/python-template-test.git
git push -u origin main -f
# Create a local environment to test your generated package locally
python -m venv env
source env/bin/activate
python -m pip install --upgrade pip setuptools
python -m pip install '.[dev,publishing]'

@sverhoeven sverhoeven marked this pull request as ready for review September 17, 2025 07:58
Copy link
Contributor

@sjvrijn sjvrijn left a comment

Choose a reason for hiding this comment

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

Thanks for the addition!

One inconsistency I noticed: in the README.dev.md you suggest mypy . while in build.yml, it's just mypy (without the .).

I also get different results on my machine between the two:
image

@sverhoeven
Copy link
Member Author

sverhoeven commented Oct 2, 2025

Thanks for the addition!

One inconsistency I noticed: in the README.dev.md you suggest mypy . while in build.yml, it's just mypy (without the .).

I also get different results on my machine between the two: image

Thanks for reviewing.

I added

later, which made mypy work and I forgot to update the docs, so will do that.

You get different answer between mypy and mypy ., because the second also includes the build dir. I can maybe exclude build/.

sverhoeven and others added 2 commits October 2, 2025 15:46
Co-authored-by: Sander van Rijn <s.vanrijn@esciencecenter.nl>
@sverhoeven sverhoeven requested a review from sjvrijn October 7, 2025 07:08
Copy link
Contributor

@sjvrijn sjvrijn left a comment

Choose a reason for hiding this comment

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

Thanks for updating, LGTM!

@sverhoeven sverhoeven merged commit 07e120e into main Oct 7, 2025
18 checks passed
@sverhoeven sverhoeven deleted the typing branch October 7, 2025 09:47
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.

3 participants