Re: Ticket #13910: Generator based rendering (streaming) of templates

Hi all, I picked up on earlier work done for generator based template rendering, > brought it up to master and improved a little on it with tests and a > StreamingTemplateView class. > > I've created the following pull request for consideration: > https://github.com/django/django/pull/1037 > >

Re: MAC adddres field

On Wed, Jun 26, 2013 at 11:47 PM, Patryk Ściborek wrote: > W dniu środa, 26 czerwca 2013 17:26:12 UTC+2 użytkownik Carl Meyer napisał: > > >> Do you have any new information to justify why the existing resolution >> of #2239 should be reconsidered? >> >> I think the existing

Re: [GSoC] Revamping validation framework and merging django-secure once again

Hello! I've deleted old `gsoc2013-verification` branch. Follow the new `gsoc2013-checks` branch [1]. [1] https://github.com/chrismedrela/django/tree/gsoc2013-checks What did I do? I've rewritten field tests living in `django.tests.invalid_models` package [2], inside `tests.py` file [3]. I've

Re: MAC adddres field

On Wed, Jun 26, 2013 at 5:53 PM, Thomas K. Adamcik wrote: > > https://pypi.python.org/pypi/django-netfields is postgres specific and is > probably what you are really looking for. It provides CIDR, INET and MAC > fields, > use netaddr for the python side and also add

Re: MAC adddres field

On Wednesday 26 June 2013, Patryk Ściborek wrote: > W dniu środa, 26 czerwca 2013 17:26:12 UTC+2 użytkownik Carl Meyer napisał: > > Do you have any new information to justify why the existing resolution > > of #2239 should be reconsidered? > > > > I think the existing resolution is correct. This

Re: MAC adddres field

Hi, On Wed, Jun 26, 2013 at 04:27:19PM +0100, Marc Tamlyn wrote: > Personally, I'm not convinced that it should be part of core Django, > especially as only one of the supported databases covers it. > > There seem to be some implementations about in the wild, though they don't > appear to use

Re: MAC adddres field

W dniu środa, 26 czerwca 2013 17:26:12 UTC+2 użytkownik Carl Meyer napisał: > > Do you have any new information to justify why the existing resolution > of #2239 should be reconsidered? > > I think the existing resolution is correct. This seems like a perfect > case for a third-party field

Re: MAC adddres field

Hi Patryk, While I understand your use case, I believe your proposal is lacking an argument as to why this should belong in core instead of in a third-party module. Considering it's restricted to PSQL, I find the maintenance burden hard to justify. Cheers, André Terra On Jun 26, 2013 12:20 PM,

Re: MAC adddres field

Personally, I'm not convinced that it should be part of core Django, especially as only one of the supported databases covers it. There seem to be some implementations about in the wild, though they don't appear to use the PG specific functionality. https://github.com/tubaman/django-macaddress

Re: MAC adddres field

Hi Patryk, On 06/26/2013 09:13 AM, Patryk Ściborek wrote: > I would like to ask you to reconsider addition of field representing MAC > address. There was similar ticket created 7 years ago: > https://code.djangoproject.com/ticket/2239 and it was closed with wontfix. > > I use Django in many

Re: Circularly dependent fixtures fail with Postgres 9.2

Thanks for taking the time to check. Based on Russell's message, I think that's a bug, but I'm not sure why it happens. Could you file a ticket in the tracker, so we don't forget about it? Thank you, -- Aymeric. On 26 juin 2013, at 02:43, Yo-Yo Ma wrote: > It does