[1.8 to 1.10] Why I had to set trailing slash to false in my DRF urls.py in order to make things work like before the update

Hi, I was running on 1.8, using django mainly for his API with DRF. Everything worked well. Since I went on with 1.10 I have this kind of message when I make a PUT request to my API : You called this URL via POST, but the URL doesn't end in a slash and you have APPEND_SLASH set. Django can't

Re: Retroactively seting up virtualenv

Hi, once you understand what virtualenv does, it should be obvious. And virtualenv is really quite simple. This should help: https://djangodeployment.com/2016/11/01/virtualenv-demystified/ Regards, Antonis Antonis Christofides http://djangodeployment.com On 2017-07-14 18:30, Rich Shepard wrote

Re: Django db backend not FIPS compliant

I am having the same problem. Anyone have a solution other than patch hashlib? On Wednesday, May 31, 2017 at 9:36:20 AM UTC-4, Tim Graham wrote: > > django-developers discussion: > https://groups.google.com/d/msg/django-developers/dlUIPzQgnpM/Mtl7CQbPAQAJ > > On Tuesday, May 30, 2017 at 5:06:23

Re: [1.8 to 1.10] Why I had to set trailing slash to false in my DRF urls.py in order to make things work like before the update

Hi, I think the error message is pretty self explaining. You are using DRF - what are you using for the frontend? Which URLs are being called? By default all django urls should end in a trailing slash - for example : /posts/1/ and if you are calling these from a django template page this is automa

Re: Django db backend not FIPS compliant

All, I have submitted a ticket where i propose the use of the "usedforsecurity=False" flag. Please take a look and comment if you have any thoughts. https://code.djangoproject.com/ticket/28401 On Sunday, July 16, 2017 at 11:22:45 AM UTC-4, Andrew DiPrinzio wrote: > > I am having the same pr