3 ms·

Michał Górny's later post in the thread is worth a read: https://archives.gentoo.org/gentoo-dev/message/167c5156a80d6860e935a2ea92c6b6b5 https://archives.gentoo

Michał Górny's later post in the thread is worth a read: https://archives.gentoo.org/gentoo-dev/message/167c5156a80d6860e935a2ea92c6b6b5 https://archives.gentoo.org/gentoo-dev/message/167c5156a80d6...

lumpa 6y ago
It seems at least portage will be able to remove the dependency on dev-python/cryptography: https://archives.gentoo.org/gentoo-dev/message/73e4a44a8d04709ff33d59eda96030cd https://archives.gentoo.org/gentoo-dev/message/73e4a44a8d047...
theamk 6y ago
The kinda-response from cryptography thread: https://github.com/pyca/cryptography/issues/5771#issuecomment-775119338 https://github.com/pyca/cryptography/issues/5771#issuecommen... >> You can't really expect volunteers to port the whole Rust to other architectures just to get cryptography back. > It sounds like you're saying that your time as a Gentoo and NetBSD maintainer is worth more than the time of cryptography maintainers. They are volunteers as well, y' know. You expect those volunteers to keep their security-focused project dependent on inherently insecure technology because it would make your own job easier. Your goals and requirements might not be matching the goals and plans of the maintainers of cryptography. It might be unfortunate for you but it really is as simple as that.
- hedora 6y ago
  That’s pretty definitive: the cryptography module is developed by volunteers that have neither the time nor inclination to support existing users. The only reasonable options are porting to something else or forking the module. That’s been my experience with everything I’ve written or maintained in python, which is why I no longer consider using it for new projects. It’s too bad. I dusted off some old python 2 scripts today, and (thanks to the frozen in time interpreter/modules) they worked fine.
  - xxpor 6y ago
    Python itself doesn't actually support these architectures! It just happens to work, and well they broke it. IDK what else you'd expect.

lumpa 6y ago

It seems at least portage will be able to remove the dependency on dev-python/cryptography: https://archives.gentoo.org/gentoo-dev/message/73e4a44a8d04709ff33d59eda96030cd https://archives.gentoo.org/gentoo-dev/message/73e4a44a8d047...

theamk 6y ago

The kinda-response from cryptography thread: https://github.com/pyca/cryptography/issues/5771#issuecomment-775119338 https://github.com/pyca/cryptography/issues/5771#issuecommen... >> You can't really expect volunteers to port the whole Rust to other architectures just to get cryptography back. > It sounds like you're saying that your time as a Gentoo and NetBSD maintainer is worth more than the time of cryptography maintainers. They are volunteers as well, y' know. You expect those volunteers to keep their security-focused project dependent on inherently insecure technology because it would make your own job easier. Your goals and requirements might not be matching the goals and plans of the maintainers of cryptography. It might be unfortunate for you but it really is as simple as that.

hedora 6y ago
That’s pretty definitive: the cryptography module is developed by volunteers that have neither the time nor inclination to support existing users. The only reasonable options are porting to something else or forking the module. That’s been my experience with everything I’ve written or maintained in python, which is why I no longer consider using it for new projects. It’s too bad. I dusted off some old python 2 scripts today, and (thanks to the frozen in time interpreter/modules) they worked fine.
- xxpor 6y ago
  Python itself doesn't actually support these architectures! It just happens to work, and well they broke it. IDK what else you'd expect.