Consider splitting pytezos.crypto into a separate pip package

[elric1]

The smaller package would be of use in at least two projects with which I am involved to reduce the size of our generated docker images.

[aliel]

Up

[hoh]

Installing Pytezos currently requires approximately 141 MB of dependencies, including Jupyter and other libraries that are not useful for checking signature and other cryptographic operations.

[droserasprout]

Hi, thanks for bumping this!

Merging the Jupyter kernel into the main repo helped us to establish a single release cycle between those. I think it's the right time to go further and split something like the pytezos-core package out of the main repo.

Do you think pytezos.crypto will be sufficient? May forging/unforging or RPC wrappers also come in handy?

[elric1]

For my purposes, pytezos.crypto is sufficient.

[hoh]

pytezos.crypto would also be sufficient for my usecases.

[aliel]

Hello,
we forked the crypto part available here => https://github.com/aleph-im/aleph-pytezos

[droserasprout]

Sorry about the delay. I'm still unsure about how to implement this one since Poetry - a tool we use for packaging - has no native monorepo support—going to figure it out in the next few days.

[droserasprout]

After some consideration we decided that maintaining a separate package would be too time consuming despite being technically possible. Our latest Docker image is 122MB uncompressed, which isn't perfect, but, well, competitive I think. Closing this issue as wontdo.

Please, don't use pytezos-core 1.0.0rc1 prerelease image and Python package as they are very outdated.