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
WIP: Python packages cleanup #30919
WIP: Python packages cleanup #30919
Conversation
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.
Can you cc the maintainers of the packages that are involved.
@@ -1,7 +1,12 @@ | |||
{stdenv, fetchurl, python27Packages, file }: | |||
{ stdenv, fetchurl, python27Packages, file, pkgs }: |
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.
Don't use pypi2nix
in 5666dff703372a9aaa0ec5fe03a2edd713f9f4ee.
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 did not use pypi2nix for any of this.
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.
Right, I see. In any case, functions should preferably have exact arguments instead of package sets.
, pkgs }: | ||
|
||
let | ||
beautifulsoup = pythonPackages.callPackage ./beautifulsoup.nix { |
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.
Forgot to include this 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.
Yes I did. Will update.
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.
bitstring isn't dead, it just needs URL update (and version bump).
UPDATE: Other non-dead packages (just need update): demjson, pyodbc, robotsuite.
@bjornfor I know a bunch of the packages are not dead but since no one is maintaining them in nixpkgs I figure that they do more harm than good. I started this by doing a I see no point in keeping around packages that no one has the intention of maintaining. |
c3407f4
to
0211bde
Compare
I have updated bitstring, demjson, pyodbc, robotsuite in master (0b93dbe and parents). Please rebase. |
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've updated bitstring, demjson, pyodbc, robotsuite in master, so you can drop them from this PR.
@bjornfor Please also split them out from |
@adisbladis: Done (489cdc2 and 3 parents). |
Thank you @bjornfor |
0211bde
to
2747260
Compare
@bjornfor Thanks :) Packages dropped from PR. |
Harm to whom? Nixpkgs users or maintainers? |
@bjornfor I have a few reasons for this.
|
@adisbladis I mostly agree with you, but I do want to add the following. Many of us that have been using Nixpkgs for some time are listed as maintainers for a lot of packages. That's mostly because we have (or had) a need for that package, and simply want to be warned when they are touched. Ideally, each of us would maintain fewer packages, but as is I think obvious, we just do not have that many maintainers, but still we have a need of the packages. |
8885eb6
to
37f5dc0
Compare
The alternative is not having the package at all. (I'd rather have old package than no package.)
Good point.
(That doesn't explain how it's harmful to maintainers. I think it's harmful when there are packages that require maintenance, but nobody really cares about the packages anymore. Then it is better to remove, instead of "forcing" people to spend energy on things that don't matter.) No, I cannot claim that I maintain all my packages, if that means always having the latest version (unfortunately). I could remove myself as maintainer and/or remove all "my" packages if they lack maintainers, but I don't see that as a good solution either.
But the alternative would be not having any dependency packages to begin with. Isn't it better to update a few old packages when needed than having to write all expressions from scratch? To sum up, I think it's good that nixpkgs receives some "clean-up" from time to time (thanks!), but we must also find a balance in how eager we are when cleaning/removing stuff. Being too eager or too lazy is both bad. |
Since |
@@ -0,0 +1,25 @@ | |||
{ lib | |||
, pkgs | |||
, pythonPackages |
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's better to have explicit dependencies, so please replace "pkgs" and "pythonPackages" with specific packages. (Unless there is a new style going on in nixpkgs python packaging that I've missed.)
From upstream: This functionality provided by this module is now part of mechanize. I don't intend to make further standalone releases of ClientForm.
…dependent packages
…ackages into salut-a-toi derivation
…on by any packages
37f5dc0
to
98024e2
Compare
I only noticed this PR when it was merged: it was not ready.
|
@orivej Ideally we have expressions, and preferably of the latest versions, but that requires maintainers. We just don't have enough people maintaining all of the expressions. |
Motivation for this change
pythonPackages
is a mess and needs lots of cleanup and removal of unused unmaintained packages.This is an attempt at starting the effort of cleaning things up.
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)cc @domenkozar @bjornfor @lovek323 @nlewo @cillianderoiste