Django security releases issued: 4.1.7, 4.0.10, and 3.2.18

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2023/feb/14/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django 4.1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/aug/03/django-41-released/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django security releases issued: 4.0.7 and 3.2.15.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/aug/03/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django 4.1 release candidate 1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/jul/19/django-41-rc1/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email

Django 4.1 beta 1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/jun/21/django-41-beta-1-released/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it,

Django bugfix release: 4.0.5

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/jun/01/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django 4.1 alpha 1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/may/18/django-41-alpha-1-released/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it,

Django bugfix release: 4.0.3

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/mar/01/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/jan/04/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django bugfix release: 3.2.8

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/oct/05/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: Django bugfix release: 3.2.6

shouldn’t use computers. > On 2 Aug 2021, at 08:37, Carlton Gibson wrote: > > Details are available on the Django project weblog: > > https://www.djangoproject.com/weblog/2021/aug/01/bugfix-release/ > > -- You received this message because you are subscribed to the Google

Django bugfix release: 3.2.6

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/aug/01/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group.

Django security releases issued: 3.2.4, 3.1.12, and 2.2.24

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/jun/02/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Django security releases issued: 3.2.1, 3.1.9 and 2.2.21

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/may/04/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Django Debug Toolbar security releases issued: 3.2.1, 2.2.1 and 1.11.1.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/apr/14/debug-toolbar-security-releases/ -- You received this message because you are subscribed to the Google

Django 3.2 Released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/apr/06/django-32-released/ -- You received this message because you are subscribed to the Google Groups "Django users" group.

Django 3.2 release candidate 1 released.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/mar/18/django-32-rc1/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Django 3.2 beta 1 released

Details are available on the Django weblog: https://www.djangoproject.com/weblog/2021/feb/19/django-32-beta-1-released/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django security releases issued: 3.1.7, 3.0.13 and 2.2.19

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/feb/19/security-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django 3.2 alpha 1 released.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/jan/19/django-32-alpha-1-released/ -- You received this message because you are subscribed to the Google Groups "Django

Django bug release: 3.1.5

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2021/jan/04/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django bugfix releases issued: 3.1.3, 3.0.11, and 2.2.17

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2020/nov/02/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Django security releases issued: 3.1.1, 3.0.10 and 2.2.16

Today the Django team issued 3.1.1, 3.0.10 and 2.2.16 as part of our security process. These releases address two security issues, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2020/sep/01/security-releases/ -- You received this message

Django bugfix releases: 3.0.5 and 2.2.12.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2020/apr/01/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django security releases issued: 3.0.3, 2.2.10 and 1.11.28

Today the Django team issued 3.0.3, 2.2.10 and 1.11.28 as part of our security process. These releases address a security issue, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2020/feb/03/security-releases/

Django 3.0 Released.

Django 3.0 is now available. https://www.djangoproject.com/weblog/2019/dec/02/django-3-released/ With the release of Django 3.0, Django 2.2 has reached the end of mainstream support. The final minor bug fix release (which

Django security releases issued: 2.2.8 and 2.1.15.

Today the Django team issued 2.2.8 and 2.1.15 as part of our security process. These releases address security issues, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2019/dec/02/security-releases/

Django bugfix releases: 2.2.6, 2.1.13, and 1.11.25

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2019/oct/01/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django 3.0 alpha 1 released

We've made the first release on the way to Django's next major release, Django 3.0! With about two and a half months until the final release (scheduled for December 2nd), we'll need timely testing from the community to ensure an on-time, stable release. Check out the blog post:

Re: Django bug: change uuid field to FK does not create dependency

Hi Viktor, Yes, AlterField should add the dependency. Manually edit the migration for now. In your example, making it: ``` dependencies = [ ('testapp1', '0002_app1_another_app'), ('testapp2', '0001_initial'), ] ``` ... and hopefully we can improve the detection there.

Django security releases issued: 2.2.4, 2.1.11, and 1.11.23.

Today the Django team issued 2.2.4, 2.1.11, and 1.11.23 as part of our security process. These releases address security issues, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2019/aug/01/security-releases/ -- You received this message because

Django security releases issued: 2.2.2, 2.1.9 and 1.11.21

Today the Django team issued 2.2.2, 2.1.9, and 1.11.21 as part of our security process. These releases address security issues, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2019/jun/03/security-releases/ -- You received this message because

Re: Django 2.2 released.

Oops, typo there: > ...Django 2.0... That should say "Django 2.1 will receive security and data loss fixes until December 2019". C. On Monday, 1 April 2019 15:19:43 UTC+2, Carlton Gibson wrote: > > Django 2.2, the next long-term support release, is now av

Django 2.2 released.

Django 2.2, the next long-term support release, is now available: https://www.djangoproject.com/weblog/2019/apr/01/django-22-released/ With the release of Django 2.2, Django 2.1 has reached the end of mainstream support. The

Django bugfix release 2.1.8

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2019/apr/01/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django 2.2 release candidate 1 released

We've made the final (hopefully) release on the way to Django's next major release, Django 2.2! Check out the blog post: https://www.djangoproject.com/weblog/2019/mar/18/django-22-rc1/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Django bugfix release 2.0.13.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2019/feb/12/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Django bugfix releases: 2.1.7, 2.0.12 and 1.11.20

Updated releases correcting a packaging issue from this morning are now available for the 2.1, 2.0 and 1.11 release branches. https://www.djangoproject.com/weblog/2019/feb/11/bugfix-releases/ -- You received this message

Django 2.2 beta 1 released

We've made the second release on the way to Django's next major release, Django 2.2! With less than two months until the final release, we'll need timely testing from the community to ensure a stable release. Check out the blog post:

Django security releases issued: 2.1.6, 2.0.11, and 1.11.19

Today the Django team issued 2.1.6, 2.0.11, and 1.11.19 as part of our security process. These releases address a security issue, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2019/feb/11/security-releases/ -- You received this message

Re: Overriding settings in Django when used by the models

Hi Uri. Does it work if you make `User.settings` a property, that fetches the values dynamically, rather than assigning them once at import time? Something like: @property def settings(self): return django_settings.USER_SETTINGS -- You received this message because you are subscribed

Django 2.2 alpha 1 released

We've made the first release on the way to Django's next major release, Django 2.2! With about two and a half months until the final release (scheduled for April 1), we'll need timely testing from the community to ensure an on time, stable release. Check out the blog post:

Django bugfix releases 1.11.17 and 2.1.4.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/dec/03/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django bugfix release: 2.1.3

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/nov/01/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django security release issued: 2.1.2

Today the Django team issued 2.1.2 as part of our security process. This release address a security issue, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2018/oct/01/security-release/

Django bugfix releases 1.11.16 and 2.0.9

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/oct/01/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Django bugfix release: 2.1.1

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/aug/31/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django bugfix releases: 2.0.7 and 1.11.14

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/jul/02/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

Django bugfix release: 2.0.6

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/jun/01/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an

"Error creating new content types" with multiple DB router

Hi, Using multiple DBs, with most models in the "default" db but models for a single app being stored in a second DB, I've more or less copied the example from the docs for a custom database router. (My example is

Re: Error when checking owner in REST API CreateAPIView

Hi Daniel, The call to get_object won't work, since Create views don't yet have an object to fetch. The correct approach is override perform_create and pass the user to your serialiser's save method. There's a section in the tutorial that covers this exact use case:

Re: django graphs

On 6 Oct 2010, at 14:42, ashy wrote: > I am basically looking for a dynamic line graph, where in the points > on the x axis and the points on the graph are clickable. Also, I want > it to be integrated with the django app I am working. The YUI Charts library is pretty good.

Re: convert list into a comma separated string

On 4 Oct 2010, at 12:41, ashy wrote: > I am writing a django function in which I have a following list: > li = ['a','b','c'] > I want to create a string from the list which should look like > str = 'a,b,c' ','.join(li) Regards, Carlton -- You received this message because you are subscribed

Re: Django Tutorial

On 4 Oct 2010, at 10:10, parameswar wrote: > Hi, i am a newbie to the django framework. I would like to know the > best book which can guide me in django. A very basic book shall be > helpful ! I recommed Django: The Definitive Guide (get the "Updated for 1.1" version) Regards, Carlton --

Re: Configuring URLs for different views

On 1 Oct 2010, at 15:07, simon_saffer wrote: > In the web site I'm creating many of the pages will not be database > driven. > I am trying to set up my urls.py so that all pages that all extend the > base.html template > can be rendered in the same way. I'm sure that I shouldn't need a > unique

Re: url not going to view

On 30 Sep 2010, at 16:38, Bradley Hintze wrote: > OH, they're regular expressions, right? Ok, I need to try to > understand RE but they still escape any meaning for me somehow. Yeah, I think that's a meme. I can't really offer any advice beyond: - Just learn enough to get the URLs you need

Re: url not going to view

hat is the significance of the '$' (or what does it mean) in the URLs >> as pointed out in previous messages? >> >> On Thu, Sep 30, 2010 at 11:15 AM, Carlton Gibson >> <carlton.gib...@gmail.com> wrote: >>> Its the plural of $. >>> >>> On 30 S

Re: url not going to view

Its the plural of $. On 30 Sep 2010, at 16:02, Bradley Hintze wrote: > Why $s, if you don't mind me asking? > > On Thu, Sep 30, 2010 at 10:55 AM, Carlton Gibson > <carlton.gib...@gmail.com> wrote: >> >> On 30 Sep 2010, at 15:42, Bradley Hintze wrote:

Re: url not going to view

On 30 Sep 2010, at 15:42, Bradley Hintze wrote: > urlpatterns = patterns('', >(r'^', home_view), >(r'^here/', here), ># Example: > ) your first pattern matches all URLs which have a beginning, which is all URLs. You need to add the $s at the end: urlpatterns = patterns('',

Re: Tabular output

I think it's not a problem. I just ran this via the (HTML5) validator and it didn't complain: cell1 cell2 cell1 Regards, Carlton On 30 Sep 2010, at 13:49, Martin Tiršel wrote: > Thanks, this looks better,

Re: iPhone posting FILEs = "Invalid content length"

On 30 Sep 2010, at 11:55, Danny Bos wrote: > Basically I've got an iPhone app sending a POST to a django app, it > contains one FILE. > Every now and then (very sporadically, about 1 in 5) one fails and I > get the below message. > Exception Value: > Invalid content length: 0 > Any ideas? This

Re: Unit testing in django without using test client

Hi Girish, On 17 Sep 2010, at 06:28, girish shabadimath wrote: > thanks for d reply,,,but im new to python n django,,,dint do ne python unit > testing before,,can u plz give me some links or hints to start with... IN that case I'd recommend this book:

Re: have to use older versions of django/python

HI Wendy, On 15 Sep 2010, at 23:10, Wendy wrote: > I am pretty new to all this though, so if anyone has any tips that > will save me from tearing my hair out, correct order of doing things, > etc. I'd really appreciate it. Any advice would be appreciated. Once you've got your Python version

Re: question about the "default" Manager

On 15 Sep 2010, at 14:28, Rev. Johnny Healey wrote: > According to the django docs: "If you use custom Manager objects, take > note that the first Manager Django encounters (in the order in which > they're defined in the model) has a special status. Django interprets > the first Manager defined

Re: Optional foreign key with django?

On 9 Sep 2010, at 12:04, bagheera wrote: >> On Sep 8, 11:14 pm, maroxe wrote: >>> Hi, In my models I want to have an optional field to a foreign key. I >>> tried this: >>> >>> field = models.ForeignKey(MyModel, null=True, blank=True, >>> default=None) >>> >>> But i am