djangorestframework-jwt: init at 1.11.0

[ghost]

Motivation for this change

I'm packaging this python library because I want to use nix-shell to manage python dependencies for a project.

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Assured whether relevant documentation is up to date
• Fits CONTRIBUTING.md.

---

[dotlambda]

Adding yourself to maintainer-list.nix should be a separate commit.

[dotlambda]

Btw, did you read https://nixos.org/nixpkgs/manual/#python?

[ghost]

@dotlambda Yes, I've read the python manual.

[dotlambda]

Why are you adding django-rest-auth without referencing it in python-packages.nix?

Also, please make sure the commit which adds you to the maintainer list is the first one.

[ghost]

@dotlambda I accidentally added the django-rest-auth module. Can I submit more than 1 module at once?

[dotlambda]

@dotlambda I accidentally added the django-rest-auth module. Can I submit more than 1 module at once?

If it makes sense to, e.g. if these are all required for a certain package you're packaging, you should put these commits in a single PR.

[ghost]

I'll close this and open a second PR later on with all the other modules I'll need.

[dotlambda]

Please ping me when you did so.

[ghost]

@dotlambda I have a package that doesn't include tests in the pypi release, is it a better practice to package the testless pypi or the github release that includes tests?

[dotlambda]

If you plan on actively maintaining it, I think there's no harm in fetching from GitHub. Otherwise, PyPI is preferred because it allows for auto-upgrades. Best would be to file an upstream PR or issue so they include the tests in their PyPI tarball.