Development Server Ignores IP-address Parameter

For some reason, my Django Development Server ignores the IP:Port parameter when I start it. No matter what I enter for that parameter, it always uses 127.0.0.1:8000. I think (but am not sure) this started happening when I upgraded from Django-1.7 to Django-1.8.2. I am running on Slackware

Re: Two Things: (1)-ModelChoiceField with a searchbox and (2)-Related Dropboxes

Another option would be JQuery Autocomplete: https://github.com/devbridge/jQuery-Autocomplete I have used both, JQuery Autocomplete is simpler to get going but Select2 is more flexible. François > On Jul 15, 2015, at 7:27 PM, Dan Tagg wrote: > > Select2

Re: Two Things: (1)-ModelChoiceField with a searchbox and (2)-Related Dropboxes

Select2 can do this https://select2.github.io. Other alternatives are available too. Dan On 13 Jul 2015 4:27 pm, "Miguel Pereira Legal" wrote: > I have this two questions: > > I am trying to write a small stock management system, and I am finding > problems in the Form.

Re: Two Things: (1)-ModelChoiceField with a searchbox and (2)-Related Dropboxes

El 13/07/15 10:09, Miguel Pereira Legal escribió: I have this two questions: I am trying to write a small stock management system, and I am finding problems in the Form. See, when an item goes out I have a dropbox (ChoiceField) to choose the item that is going out, but this dropbox gets too

Re: Playing with API- DjangoProject Part 1

Best advice is to read the overview page, and then follow the tutorial link. After you've completed the tutorial, you should have a good understanding of where to go and what you can do with Django: https://docs.djangoproject.com/en/1.8/intro/overview/ -James On Jul 15, 2015 9:51 AM, "Auj

Re: Playing with API- DjangoProject Part 1

Hi all please let me know if you know how to fix following [7/15, 21:54] h@rish!: solivr@harish-Inspiron-5421:~$ sudo apt-get update [sudo] password for solivr: Sorry, try again. [sudo] password for solivr: Sorry, try again. [sudo] password for solivr: [7/15, 21:55] h@rish!: solivr is not in the

Re: "RuntimeError: Error creating new content types."

I just fixed this issue by entering into my database directly, showed all rows on "django_migrations", I saw that I did migrated before the contenttypes (probably when I did a regression to django 1.4 for some tests). By deleting the rows with contenttypes on it, deleting the contenttypes

Re: "RuntimeError: Error creating new content types."

Hey Devang, No, we did not fake any migrations =( On Tuesday, June 23, 2015 at 12:58:46 AM UTC+2, Devang Mundhra wrote: > > Chris- > By any chance, did you fake any of the migrations. That was the problem I > had faced- it wasn't a Django problem, it was a problem with my migration. > > On Mon,

Re: Playing with API- DjangoProject Part 1

Thank you for your help James. I have deleted the the folder the contained the framework and will be starting from scratch. I completed 'learn python the hard way' along with a few more beginner level courses for python. I'm sure you read or get this question daily, but what would you recommend

Re: 1.7 to 1.8 upgrade: test suite failing

A minimal project to reproduce the issue would be helpful. On Wednesday, July 15, 2015 at 5:41:49 AM UTC-4, tom.sz...@eporta.com wrote: > > Unfortunately, adding the super() calls didn't help. > > On Tuesday, July 14, 2015 at 12:47:02 PM UTC+1, Tim Graham wrote: >> >> Please try adding the

Re: preserve data when migrating ForeignKey to ManyToManyField

> Den 14/07/2015 kl. 23.32 skrev A Lee : > > I'd like to change a ForeignKey field into a ManyToManyField, preserving > existing data by creating entries in the many-to-many through table. Running > makemigrations after changing the model class creates a migration that

Re: Celery to process task and modify the model fields

On Tue, Jul 14, 2015 at 9:15 PM, Robin Lery wrote: > Yes. That time you were the one to guide me. I was looking at other projects > after that. > > I am just confused on how to get the video.mp4_720 to be the converted > video. Will you please help. > This is explained in

Re: 1.7 to 1.8 upgrade: test suite failing

Unfortunately, adding the super() calls didn't help. On Tuesday, July 14, 2015 at 12:47:02 PM UTC+1, Tim Graham wrote: > > Please try adding the super() calls. > > On Tuesday, July 14, 2015 at 5:44:09 AM UTC-4, tom.sz...@eporta.com wrote: >> >> Hi, yes. Some of my test classes do use setUpClass()