-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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
diff_cover: init at 1.0.2 #33715
diff_cover: init at 1.0.2 #33715
Conversation
I've also packaged pydocstyle in #31180. Yours seem to enable tests but always including configparser might fail I believe. |
pname = "diff_cover"; | ||
version = "1.0.2"; | ||
|
||
LC_ALL = "en_US.UTF-8"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is only needed for the tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it is. Without setting this variable tests will fail. Where should I put this variable definition?
Without this variable tests fail, if this variable will be visible only during tests execution,
runtime execution may fail too without LC_ALL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The env var can be set in the preCheck
hook. This env var won't be set during runtime anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This package supply some executable files. If I wrap this executables with makeWrapper
and set LC_ALL
in wrapper?
|
||
propagatedBuildInputs = [ jinja2 jinja2_pluralize pygments six inflect ]; | ||
|
||
buildInputs = [ mock nose coverage pycodestyle flake8 pyflakes pylint pydocstyle git ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test requirements go into checkInputs
|
||
LC_ALL = "en_US.UTF-8"; | ||
|
||
src = fetchFromGitHub { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason for not using PyPI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Package from PyPi fails tests when build is doing in sandbox. I told about that to author of diff-cover. He fixed that bug.
Here this conversation about this bug.
Bachmann1234/diff_cover#72
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work! If it is a patch on top of a release, then we fetch the patch with fetchpatch
instead and add it to patches
.
src = fetchFromGitHub { | ||
owner = "Bachmann1234"; | ||
repo = "diff-cover"; | ||
rev = "85c30959c8ed2aa3848f400095a2418f15bb7777"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can refer to a tag here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I refer to the last tag, tests will fail. Maybe it is better refer to this commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
six, inflect, mock, nose, coverage, pycodestyle, flake8, pyflakes, git, | ||
pylint, pydocstyle }: | ||
|
||
buildPythonPackage rec { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this tool need to access Python modules of the environment it is used in, or is it just an external tool?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
( Maybe I didn't understand what you ask. I'm learning english ... :) )
This tool is not supposed to provide python modules for users.
It provide two execution files: diff-cover
, diff-quality
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This tool doesn't need access to environment where it is used in.
|
||
propagatedBuildInputs = [ snowballstemmer configparser ]; | ||
|
||
buildInputs = [ pytest pytestpep8 mock pathlib ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checkInputs
pkgs/top-level/python-packages.nix
Outdated
@@ -22660,6 +22660,13 @@ EOF | |||
voluptuous = callPackage ../development/python-modules/voluptuous { }; | |||
|
|||
pysigset = callPackage ../development/python-modules/pysigset { }; | |||
|
|||
jinja2_pluralize = callPackage ../development/python-modules/jinja2_pluralize { }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Attributes are roughly organized. Surely you can find a better place for these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is criteria of "better place" ?
I don't understand why this place is bad.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The attributes should be ordered by name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be order by derivation name or by attribute name?
I still does not understand what you want because the attribute set doesn't have lexicographical order...
If i put this attribute near line 9493 (near jinja package) will it be ok?
@FRidh , why didnt you merge this request? I did all changes that you required. |
|
Please squash the commits so there is a commit per expression. |
@FRidh I have done your requirements. |
Motivation for this change
new packages for
diff_cover
,pydocstyle
,jinja2_pluralize
diff_cover depends on
pydocstyle
,jinja2_pluralize
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)