Re: [django.contrib.postgres] Would this be accepted and how hard would it be to do?

Correct - our XMLField was just a TextField with our own parsing on top of it, so given all the DDOS problems related to "billion laughs" etc, it was just too dangerous to include any more. As Marc notes, in this case, we'd be looking at an implementation of XMLField that is provided by someone

[ANNOUNCE] Django Security advisory: simple_tag does not do auto-escaping

The Django team has just published a short security advisory about usage of the simple_tag template tag helper. You should audit your own code. https://www.djangoproject.com/weblog/2015/jun/29/simple_tag-security-advisory/ -- You received this message because you are subscribed to the Google

Re: virtual fields and the migration framework

Thank you very much for the suggestions. So after using: cls._meta.add_field(self, virtual=True) instead of: cls._meta.add_field(self) cls._meta.virtual_fields.append(self) The VirtualField implementation of django-hstore is much cleaner and does not conflict with the migration framework. I

Re: django.channels: "async" for Django

Hi Andrew, i have been taking a look at your work because I find it interesting and I also think that django should have some core mechanism for integrating websockets. I was wondering, have you also tried one of the other popular django websocket apps? Have you found any interesting one that

Re: [django.contrib.postgres] Would this be accepted and how hard would it be to do?

In that case the ability to support it would depend on the support in psycopg2 and how safe we consider their implementation. Marc On 29 Jun 2015 16:01, "Collin Anderson" wrote: > I think XMLField was removed because the security of xml parsing and > validating is hard to

Re: [django.contrib.postgres] Would this be accepted and how hard would it be to do?

I think XMLField was removed because the security of xml parsing and validating is hard to get right. On Sunday, June 28, 2015 at 7:51:22 PM UTC-4, Russell Keith-Magee wrote: > > > On Mon, Jun 29, 2015 at 7:32 AM, Josh Smeaton > wrote: > >> I'm not quite up to date on XML

Re: Adding new model. ContentType error with field "name"

Hi, Please don't cross post to django-users and django-developers. This mailing list is for the development of Django itself. I'll answer your question on django-users. Thanks! On Monday, June 29, 2015 at 5:05:41 AM UTC-4, ClosiusBeg wrote: > > Hi All! > > I caught a error when I move from

Adding new model. ContentType error with field "name"

Hi All! I caught a error when I move from Dajngo 1.7 to 1.8. I wanted to add new model, for example: class Test(models.Model): class Meta(): db_table = 'test' userID = models.ForeignKey(User) minAge = models.PositiveSmallIntegerField(default=0) maxAge =