Re: file fields

Thank you for your reply and I try the fixed model but the problem with the view that I use to store the files from templets to the db I followed the django documents as *def *custmoer(request): *if *request.method == *'POST'*: form = CustomerForm(request.POST, request.FILES)

Re: Moving from django 1.3 to 1.9

I agree with all the advice to go a step at a time. Here's a bunch of clues and chatter in github issues about how we upgraded from 1.4 to 1.8, one minor version at a time. https://github.com/FreedomCoop/valuenetwork/issues?q=is%3Aclosed+label%3Aupgrade -- You received this message because

Re: Am I stupid or is there an essential error in Django 1.10 Docs?

https://github.com/django/django/pulls The tutorial has a very logical order, going from the database abstraction up to the template layer and beyond. But feel free to rewrite it and submit it to the project. I never follow tutorials to the letter - for example back when I did it in Django

Re: Am I stupid or is there an essential error in Django 1.10 Docs?

What do you mean by PR? Am Freitag, 27. Januar 2017 18:32:23 UTC+1 schrieb Melvyn Sopacua: > > On Monday 16 January 2017 07:49:00 'Peter Müller' via Django users wrote: > > > > > Also I used the tutorial just that I abstracted the concept since I > > > think the tutorial is more than bad. > >

Re: MultiValueDictKeyError on 'for' loop

On Friday 27 January 2017 02:22:35 Elgan Frost wrote: > but I don't understand why this is causing me the error...? Can anyone > explain what I'm doing wrong here? Is there something wrong with the > way I have declared `drawing_formset`? How can I resolve this error? Your total_forms_count is

Re: Am I stupid or is there an essential error in Django 1.10 Docs?

On Monday 16 January 2017 07:49:00 'Peter Müller' via Django users wrote: > Also I used the tutorial just that I abstracted the concept since I > think the tutorial is more than bad. Awaiting your PRs. -- Melvyn Sopacua -- You received this message because you are subscribed to the Google

Re: Am I stupid or is there an essential error in Django 1.10 Docs?

But if I do a direct import via python's import statement. it will execute the content of the file before loading apps and that raises that error. No matter what you import you *have* to use django's import system. Also it just works fine now. Am Dienstag, 17. Januar 2017 23:05:10 UTC+1 schrieb

Re: Moving from django 1.3 to 1.9

I'd advise you to be aware of third-party libraries. Sometimes they are dropped or can bring some incompatibilities. On 27 January 2017 at 08:42, Andreas Kuhne wrote: > I second this. Having moved from 1.3 to 1.9 in stages - I think this is > the best way to do it.

Re: Django-channels and JSON-RPC

Ok, module is uploaded https://pypi.python.org/pypi/django-channels-jsonrpc/0.1 Feel free to use it. Le vendredi 27 janvier 2017 11:30:15 UTC+1, Fabien Millerand a écrit : > > Thanks Alex. > > I also rectified something that your test brought up. > I am modifying the structure at the moment to

MultiValueDictKeyError on 'for' loop

I have Django site, which I am using to manage various projects and the information about each project. I have models for Projects and Budgets in the database. Each Project can have many Budgets, but a Budget can only be associated with one Project. I am trying to add the functionality to

Re: Moving from django 1.3 to 1.9

I second this. Having moved from 1.3 to 1.9 in stages - I think this is the best way to do it. Upgrade one minor version at a time and it will probably be easiest. Regards, Andréas 2017-01-27 10:55 GMT+01:00 ludovic coues : > You might have an easier time upgrading from one

Re: Django-channels and JSON-RPC

Thanks Alex. I also rectified something that your test brought up. I am modifying the structure at the moment to have a nice PyPI package. I also remove the ability to push to master. Please make changes in a new branch and submit a push request next time ;) But thanks anyway! I hope it will

Re: Moving from django 1.3 to 1.9

You might have an easier time upgrading from one version to the next. So first check if you have some deprecation warning and fix them. Then install django 1.4, check if you have deprecation warnings, fix them. Check things are working as intended. Test really help at this point. Once you are

Moving from django 1.3 to 1.9

Hi there, Sorry for this question, we have created this service 5 years ago and never touched since but now we want to move to a new server, with all updated software and even use python 3.5, I am wondering if there's any kind of "how-to" for it. Any help/suggestion is really appreciated.

Re: Django channels on IIS

Port 8081 - same problem. I run it with administrator permissions. пятница, 27 января 2017 г., 11:15:48 UTC+3 пользователь Jani Tiainen написал: > > Hi, > > Most probably accesses to ports below 1024 requires that you start daphne > from administrator elevated prompt. > > On 27.01.2017 09:52,

Re: Django channels on IIS

Hi, Most probably accesses to ports below 1024 requires that you start daphne from administrator elevated prompt. On 27.01.2017 09:52, Алексей Кузуб wrote: I have IIS, and i ran IIS in front of Daphne which handle SSL. But when i run daphne to listen port which support https in IIS, daphne