# Mach-nix, pip2nix, poetry2nix, or pynixify for Zulip provision

**URL:** https://discourse.nixos.org/t/mach-nix-pip2nix-poetry2nix-or-pynixify-for-zulip-provision/18836
**Category:** Development
**Created:** [April 25, 2022, 6:03am UTC](https://discourse.nixos.org/t/mach-nix-pip2nix-poetry2nix-or-pynixify-for-zulip-provision/18836 "2022-04-25T06:03:10Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![rht](https://discourse.nixos.org/user_avatar/discourse.nixos.org/rht/32/3731_2.png) [@rht](https://discourse.nixos.org/u/rht)
#### Post date: [April 28, 2022, 9:05am UTC](https://discourse.nixos.org/t/mach-nix-pip2nix-poetry2nix-or-pynixify-for-zulip-provision/18836/16 "2022-04-28T09:05:42Z")

</div>

Actually, with `mach-nix`, I can see why the `--hash=...` parsing of requirements.txt is not implemented. I can specify `backoff-stubs==1.10.0`, and `mach-nix` will do the integrity check using the hashes in `pypi-deps-db`, and it will still be reproducible.

---

_[View the full topic](https://discourse.nixos.org/t/mach-nix-pip2nix-poetry2nix-or-pynixify-for-zulip-provision/18836)._