Add Cargo.lock to the repo about cryptg HOT 4 CLOSED

I guess we're technically building "an end-product" and not a library, even if the end-product is a library (for another language). Given it makes sense as per the book on Cargo.toml vs Cargo.lock and it's useful to do, we probably should commit the file.

from cryptg.

Yeah, "no Cargo.lock for libraries" thing is mostly there for the kind of libraries that you'd include in another project, i.e. something that does not produce artifacts by itself. In this case, there is an artifact, namely the Python extension, so I'd say a Cargo.lock makes sense.

from cryptg.

Do you need a new version to be published to PyPi, or is this okay?

from cryptg.

A new version would definitely be preferable, but I'm not really in a hurry, if you've got other changes you want to bundle with that.

from cryptg.