-
-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
md2gemini: init at 1.8.1 #117917
md2gemini: init at 1.8.1 #117917
Conversation
pkgs/top-level/python-packages.nix
Outdated
mistune_2 = callPackage ../development/python-modules/mistune { | ||
source-info = { | ||
version = "2.0.0a4"; | ||
sha256 = "0i6cblmjl58kdmaa21xm0l1ls0kvjpfy45sf73fw3ws6305f628k"; |
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 it would be clearer if we converted the current default into a generic nix and created a 0.8.nix and a 2.nix file.
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.
Did it same way as postgresql do.
|
||
propagatedBuildInputs = [ mistune_2 cjkwrap wcwidth ]; | ||
checkInputs = [ pytest ]; |
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.
propagatedBuildInputs = [ mistune_2 cjkwrap wcwidth ]; | |
checkInputs = [ pytest ]; |
@@ -0,0 +1,20 @@ | |||
{ lib, buildPythonPackage, fetchPypi, mistune_2, cjkwrap, wcwidth, pytest }: |
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.
{ lib, buildPythonPackage, fetchPypi, mistune_2, cjkwrap, wcwidth, pytest }: | |
{ lib, buildPythonPackage, fetchPypi, mistune_2, cjkwrap, wcwidth, pytestCheckHook }: |
pkgs/top-level/all-packages.nix
Outdated
@@ -668,7 +668,7 @@ in | |||
|
|||
act = callPackage ../development/tools/misc/act { }; | |||
|
|||
actdiag = with python3.pkgs; toPythonApplication actdiag; | |||
actdiag = with python3; toPythonApplication actdiag; |
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.
That causes an eval error.
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.
That does not belong here, removed.
Looks like I applied all suggestions. |
@ofborg eval |
Okay, now @ofborg is happy. |
|
||
meta = with lib; { | ||
description = "The fastest markdown parser in pure Python"; | ||
homepage = "https://github.com/lepture/mistune"; |
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.
Missing maintainer.
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.
It was this way before.
Okay, I added pythonImportsCheck to mistune, but I'd rather not assume maintainership of every indirect dependency I touch. Wh |
The problem is that if your dependencies are not maintained they are potentially in a worse state but it seems like mistune is used in a lot more packages. I think adding the imports check to mistune triggered the mass rebuild. We really want to have one if there are not tests because otherwise the package can silently break. I think the best solution would be to merge this PR into staging because if we split the change out we force a merge conflict which someone would need to resolve. Let me know if thats a problem for you. |
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.
other than that the ordering could be a bit more standard LGTM if rebased to staging
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.
other than that the ordering could be a bit more standard LGTM if rebased to staging
Yes, sure. Let's merge it into staging. |
/rebase staging |
2cdc2b4
to
0cb7479
Compare
Rebased, please reopen the pull request to restart CI |
This version is required for md2gemini program and is incompatible with mistune=0.8.4
0cb7479
to
403481c
Compare
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)