Oh wow!
I didn't expect to enter such difficult terrain ... ;-)
>From PEP-249 I understand that pyformat is encouraged and supported.
I also read throug the discussion on the sig-db mailing list. As far
as I understand you (Veron and many others) are trying to settle on
what will be in the spec
Understand that this will not affect django for the next several releases.
Probably django 2.0. The transition from db-api 2 to db-api 3 will be a
lot like the transition from Python 2 to Python 3. You will have to import
a different module to get the different behavior, and today's api-2
in
Update: NEW PROPOSAL.
After extending and refactoring template.Library, and using block_tag as
described above for almost all the built-in tags, I came to the conclusion
that we can improve the template tag definitions even more. I would
introduce some thing as class based template tags.
Actua
Hi Karol,
On Saturday 18 May 2013 13:26:53 Karol Sikora wrote:
> Hi,
>
> We was talked with Russell on djangocon eu about integrating more rich
> support for working django as rest api provider, focused on dealing with
> one-page web applications.
> The motivations that currently without third pa
On Tuesday, May 21, 2013 5:51:11 AM UTC-7, Jannis Leidel wrote:
> So what I propose to fix this is simple:
>
> - combine the localflavor packages into one Python package again, call it
> django-localflavor
> - give all the individual country maintainers also access to that package
> - have a c
On Sat, May 25, 2013 at 1:00 AM, Shai Berger wrote:
> Hi Karol,
>
> On Saturday 18 May 2013 13:26:53 Karol Sikora wrote:
> > Hi,
> >
> > We was talked with Russell on djangocon eu about integrating more rich
> > support for working django as rest api provider, focused on dealing with
> > one-page
