python3Packages.psycopg2-binary: init at 2.9.9

Pscycopg2-binary is normally used in Python development to avoid having to build psycopg2 from source.
In nixpkgs we always want ot build from source whenever possible, but it can still be useful to provide a psycopg2-binary package.

This "fake" package exists to satisfy a dependency on psycopg2-binary, but still use the build from psycopg2.

cc @misuzu nix-community/pyproject.nix#143

doc/languages-frameworks/python.section.md

@@ -369,8 +369,11 @@ In nixpkgs this is used to package Python packages with split binary/source dist
 ```nix
 mkPythonMetaPackage {
   pname = "pscycopg2-binary";
-  inherit (psycopg2) optional-dependencies version meta;
+  inherit (psycopg2) optional-dependencies version;
   dependencies = [ psycopg2 ];
+  meta = {
+    inherit (psycopg2.meta) description homepage;
+  };
 }
 ```
 

pkgs/development/python-modules/psycopg2-binary/default.nix

@@ -0,0 +1,13 @@
+{
+  mkPythonMetaPackage,
+  psycopg2,
+}:
+mkPythonMetaPackage {
+  pname = "pscycopg2-binary";
+  inherit (psycopg2) version;
+  dependencies = [ psycopg2 ];
+  optional-dependencies = psycopg2.optional-dependencies or { };
+  meta = {
+    inherit (psycopg2.meta) description homepage;
+  };
+}

pkgs/top-level/python-packages.nix

@@ -10952,6 +10952,8 @@ self: super: with self; {
 
   psycopg2cffi = callPackage ../development/python-modules/psycopg2cffi { };
 
+  psycopg2-binary = callPackage ../development/python-modules/psycopg2-binary { };
+
   psygnal = callPackage ../development/python-modules/psygnal { };
 
   ptable = callPackage ../development/python-modules/ptable { };