Define port for LiveServerTestCase in 1.11?

Hi, Is it possible to define the port for LiveServerTestCase in Django 1.11? Google requires a static address for OAuth authentication. from docs : *Changed in Django 1.11:* In older versions,

Define port for LiveServerTestCase in 1.11?

Hi, Is it possible to define the port for LiveServerTestCase in Django 1.11? Google requires a static address for OAuth authentication. from docs : Changed in Django 1.11: In older versions, Django tried a

Admin css question for 1.10.7

I'm just (slowly) advancing from 1.8 to 1.11 and stopping for a short while at 1.10. I notice that help-text doesn't line up under the left edge of DecimalField fields the way it does for TextFields and most others. Is this a deliberate design decision? Thanks Mike -- PLEASE NOTE OUR NEW

DjangoCon Europe 2017

Hi everyone, DjangoCon Europe 2017 is over a month, to remember it, I collected one twitter moment for each day: https://twitter.com/i/moments/849039187319943168 https://twitter.com/i/moments/849401309333794816 https://twitter.com/i/moments/849752697578430464

Re: sqlite3 database encrytion for Django.

On 2017-05-05 11:51, agajesh...@atompower.com wrote: > I want to encrypt my sqlite3 database such that it cannot be > accessed without a key. I came across "sqlcipher" tool which > provides encryption for sqlite3 database, but I couldn't find > enough support to make it work from django. > > It

How to fix i18n fallback , from variant xx-YY to xx and from xx to en the translatino is not available.

Well, official documentation says clearly it should fall-back (ex: fr-fr to fr then to en) but my case raises 404 error. Source: https://django.readthedocs.io/en/1.5.x/topics/i18n/translation.html If a base language is available but the sublanguage specified is not, > Django uses the base

Re: makemigration detect error

Hello, I know somewhat about this situation. I was a beginner some months ago :-) the situation is : you change something in a model (add a non-nullable field) when you send « makemigrations" the ORM needs to get a value for the new fields just because it’s non-nullable before modifying

Django bugfix release: 1.11.1

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2017/may/06/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

Re: makemigration detect error

You are adding a non-null field to a table, so the existing rows from that table need a value to put in it to enforce the non-null rule. If you select 1, you type that value, and it is used for all previously existing rows in the table. On 5/6/17, Er. Rv Ranga wrote: >

makemigration detect error

python manage.py makemigrations blog You are trying to add a non-nullable field 'body' to post without a default; we can't do that (the database needs something to populate existing rows). Please select a fix: 1) Provide a one-off default now (will be set on all existing rows with a null