Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BF: move check for metalad before import of meta_extract #257

Merged
merged 2 commits into from
Jan 17, 2024

Conversation

yarikoptic
Copy link
Member

Otherwise we try to import meta_extract and it fails. Failed the build of datalad-container for debian

I will shortly bundle also run of isort on that file to ensure that pragmas are effective

Otherwise we try to import meta_extract and it fails.  Failed the build
of datalad-container for debian
@yarikoptic yarikoptic added tests Add or improve existing tests CHANGELOG-missing labels Jan 17, 2024
@yarikoptic yarikoptic requested a review from asmacdo January 17, 2024 13:16
Copy link

codeclimate bot commented Jan 17, 2024

Code Climate has analyzed commit be5f9e1 and detected 0 issues on this pull request.

View more on Code Climate.

Copy link
Member

@asmacdo asmacdo left a comment

Choose a reason for hiding this comment

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

one nitpick/question LGTM

Dataset,
clone,
Copy link
Member

Choose a reason for hiding this comment

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

Is there a convention to import classes first? I've always just done strictly alphabetical

Copy link
Member Author

Choose a reason for hiding this comment

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

"not sure". Please find an answer at https://pycqa.github.io/isort/docs/configuration/custom_sections_and_ordering.html somewhere or may be @jwodder could clarify?

Copy link
Member

Choose a reason for hiding this comment

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

isort does sort by case

https://pycqa.github.io/isort/docs/configuration/options.html

Order imports by type, which is determined by case, in addition to alphabetically.

NOTE: type here refers to the implied type from the import name capitalization. isort does not do type introspection for the imports. These "types" are simply: CONSTANT_VARIABLE, CamelCaseClass, variable_or_function. If your project follows PEP8 or a related coding standard and has many imports this is a good default, otherwise you likely will want to turn it off. From the CLI the --dont-order-by-type option will turn this off.

Type: Bool
Default: True
Config default: true
Python & Config File Name: order_by_type
CLI Flags:

--ot

--order-by-type

Copy link

codecov bot commented Jan 17, 2024

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (ce9fe4e) 94.70% compared to head (be5f9e1) 94.70%.

Files Patch % Lines
...ntainer/extractors/tests/test_metalad_container.py 83.33% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #257   +/-   ##
=======================================
  Coverage   94.70%   94.70%           
=======================================
  Files          24       24           
  Lines        1133     1134    +1     
=======================================
+ Hits         1073     1074    +1     
  Misses         60       60           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@yarikoptic yarikoptic added the release Create a release when this pr is merged label Jan 17, 2024
@yarikoptic
Copy link
Member Author

releasing so we simplify update of packages for debian and conda-forge both of which need this now

@yarikoptic yarikoptic closed this Jan 17, 2024
@yarikoptic yarikoptic reopened this Jan 17, 2024
@yarikoptic yarikoptic merged commit 330e4e3 into datalad:master Jan 17, 2024
9 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Create a release when this pr is merged tests Add or improve existing tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants