Serhiy Storchaka writes:
> Python integers have arbitrary precision. For serialization and
> interpolation with other programs and libraries we need to
> represent them [...]. [In the case of non-standard precisions,]
> [t]here are private C API functions _PyLong_AsByteArray and
> _PyLong_Fr
Vaideeswaran Ganesan writes:
> Intent is to make a web interaction as if you're working with local
> function. This is very well known design pattern called Proxy.
Sure, but the stdlib is fairly low-level. The question is not whether
this module is useful. I'm sure for some purposes it is ver
Python integers have arbitrary precision. For serialization and
interpolation with other programs and libraries we need to represent
them as fixed-width integers (little- and big-endian, signed and
unsigned). In Python, we can use struct, array, memoryview and ctypes
use for some standard sizes and
It is converting the REST API syntax into language constructs. If such
mapping doesn't exist - I agree with you that we probably should give
flexibility to user. On the other hand, if such mapping exists and I
strongly believe so - seeing several examples in web, we should allow it.
Intent is to
Vaideeswaran Ganesan writes:
> I actually want to avoid get, post, put, 2xx, 4xx codes in the
> client portions of the code.
I think this goal is too high-level for the standard library. I don't
know what you expect on the other side, but in an application I work
on it matters whether you're u
