> At the same place where you already found python-list, or here:
>
> https://mail.python.org/mailman/listinfo/python-ideas
Yeah, I've found it after a simple search.. I thought it was like an hidden
place for just some python's guru lol!
Thank you! :)
--
https://mail.python.org/mailman/listi
cescu...@gmail.com wrote:
>> Go to python-ideas for a lengthy discussion ;)
> Where can I find it?
At the same place where you already found python-list, or here:
https://mail.python.org/mailman/listinfo/python-ideas
--
https://mail.python.org/mailman/listinfo/python-list
Hello Burak, thank you for the reply.
> FWIW, Spyne can to the exact same thing -- i.e. serialize an object
> given its definition to whatever format you want. (currently xml, json,
> yaml and msgpack are supported).
My aim is to propose a built-in method to accomplish this common and simple
task
hey,
On 11/30/15 14:35, cescu...@gmail.com wrote:
>
> Hello everyone and thank you for your interest!
>
> The Peter's code is very similar to what I think the default JSON encoder
> should be.
>
> The advantage of the method that I propose is that you should not care
> anymore about which encode
Hello everyone and thank you for your interest!
The Peter's code is very similar to what I think the default JSON encoder
should be.
The advantage of the method that I propose is that you should not care anymore
about which encoder you're going to use even in case of different class
instance
Hi,
I think his goal is not to load the data back into python, but to use
it to provide some
kind of REST-Style interface. An example would be, if you have a class
instance of
a record of a movie, that it could be simply encoded and send over the
wire to display.
Without necessarily recreating the
On Sun, 29 Nov 2015 07:05:30 -0800, cescus92 wrote:
> In this day I stumbled upon a very simple task: I had a list of
> instances of a custom class and I had to convert i into a JSON.
That's all well and good, but firstly you need to both dumps and loads to
work properly with json, and secondly
cescu...@gmail.com wrote:
> Hello everyone!
>
> I'm writing here since I've read on the Pyhton's documentation that this
> is the most common path that a new proposal should follow. I'd be really
> glad if this proposal could become a PEP if I see a good response from the
> community or, in the w
