pyodide/packages/bcrypt/meta.yaml

package:
  name: bcrypt
  version: 4.1.2
  top-level:
    - bcrypt
source:
  url: https://files.pythonhosted.org/packages/72/07/6a6f2047a9dc9d012b7b977e4041d37d078b76b44b7ee4daf331c1e6fb35/bcrypt-4.1.2.tar.gz
  sha256: 33313a1200a3ae90b75587ceac502b048b840fc69e7f7a0905b5f87fac7a1258
requirements:
  executable:
    - rustup
about:
  home: https://github.com/pyca/bcrypt/
  PyPI: https://pypi.org/project/bcrypt
  summary: Modern password hashing for your software and your servers
  license: Apache License, Version 2.0
Add bcrypt (#3125) 2022-09-20 04:46:43 +00:00			`package:`
			`name: bcrypt`
Update bcrypt to 4.1.2 (#4460) 2024-02-01 20:28:55 +00:00			`version: 4.1.2`
Add bcrypt (#3125) 2022-09-20 04:46:43 +00:00			`top-level:`
			`- bcrypt`
			`source:`
Update bcrypt to 4.1.2 (#4460) 2024-02-01 20:28:55 +00:00			`url: https://files.pythonhosted.org/packages/72/07/6a6f2047a9dc9d012b7b977e4041d37d078b76b44b7ee4daf331c1e6fb35/bcrypt-4.1.2.tar.gz`
			`sha256: 33313a1200a3ae90b75587ceac502b048b840fc69e7f7a0905b5f87fac7a1258`
Add rust toolchain to the pyodide-env docker image (#3441) This adds rust toolchain into our docker image so we don't have to install it every time. make rust command still exists, but I removed it from the docs. So now a user (who wants to build a package that requires rust) is responsible for installing rust toolchain in their build setup, which is reasonable I think. Co-authored-by: josephrocca <1167575+josephrocca@users.noreply.github.com> Co-authored-by: Roman Yurchak <rth.yurchak@gmail.com> Co-authored-by: Hood Chatham <roberthoodchatham@gmail.com> 2023-01-10 04:28:04 +00:00			`requirements:`
			`executable:`
			`- rustup`
Add bcrypt (#3125) 2022-09-20 04:46:43 +00:00			`about:`
			`home: https://github.com/pyca/bcrypt/`
			`PyPI: https://pypi.org/project/bcrypt`
			`summary: Modern password hashing for your software and your servers`
			`license: Apache License, Version 2.0`