Merge pull request nix-community#405 from qowoz/python-updatescript

doc: remove pypi, add updateScript

doc/batch-updates.md

@@ -46,8 +46,8 @@ subcommand.
 
   There also exist alternative sources of updates, these include:
 
-   - PyPI, the Python Package Index:
-     [nixpkgs-update-pypi-releases](https://github.com/jonringer/nixpkgs-update-pypi-releases)
+   - package updateScript:
+      [passthru.updateScript](https://nixos.org/manual/nixpkgs/unstable/#var-passthru-updateScript)
    - GitHub releases:
      [nixpkgs-update-github-releases](https://github.com/synthetica9/nixpkgs-update-github-releases)
 

doc/introduction.md

@@ -17,5 +17,5 @@ It is the code used by the GitHub bot
 [@r-ryantm](https://github.com/r-ryantm) to automatically update
 nixpkgs. It uses package repository information from
 [Repology.org](https://repology.org/repository/nix_unstable), the
-GitHub releases API, and PyPI to generate a lists of outdated
+GitHub releases API, and the package passthru.updateScript to generate a lists of outdated
 packages.

doc/nixpkgs-maintainer-faq.md

@@ -20,7 +20,7 @@ r-ryantm gets its new version information from three sources:
 
 * Repology - information from Repology is delayed because it only updates when there is an unstable channel release
 * GitHub releases
-* PyPi releases
+* package passthru.updateScript
 
 If none of these sources says the package is out of date, it will not attempt to update it.