Re: Django version 4.2.5 not path in Windows 10

hat Django is correctly installed on your system. You >> can do this by opening a command prompt and running the following command: >> python -m django --version >> >> 2. Add Django to the PATH: >> To access Django globally from the command line, you need to add the

Re: Django version 4.2.5 not path in Windows 10

ave not solved it, I believe this will work. > > 1. Verify Django Installation: > First, make sure that Django is correctly installed on your system. You > can do this by opening a command prompt and running the following command: > python -m django --version > > 2. Add Django

Re: Django version 4.2.5 not path in Windows 10

If you have not solved it, I believe this will work. 1. Verify Django Installation: First, make sure that Django is correctly installed on your system. You can do this by opening a command prompt and running the following command: python -m django --version 2. Add Django to the PATH: To access

Django version 4.2.5 not path in Windows 10

Hello Sorry, Django version 4.2.5 is installed in Windows 10, but the path is not available. How can I fix this, please help me. I just started, but I still haven't passed the path stage, please help me -- You received this message because you are subscribed to the Google Groups "Django

Re: Installed Django 4.1 but version is 2.2

I am running on a containerised virtual environment completely isolated to the system. when I run django --version, it shows me the version 4.1, but when I check the code, it is not the code for 4.1 but the code for 2.2 On Tuesday, 21 March 2023 at 11:20:46 UTC Andréas Kühne wrote: > I

Re: Installed Django 4.1 but version is 2.2

I am guessing this is because you are running your systems installed django-admin for setting up the project and not in a virtualenvironment? Before running django-admin startproject mysite, make sure that you have created a virtualenvironment and install the version of django that you want

Installed Django 4.1 but version is 2.2

in django 4 and in django 2 and the code generated is equal to the django 2 I also ran: python -m django --version which returns: 4.1.7 Python version is 3.11 Anyone else have this issue? -- You received this message because you are subscribed to the Google Groups "Django users&q

Re: save_model doesn't run on Django version 4

One thing I'm not sure of it, how to tell if a particular Admin page is triggering a particular Admin instance. On Tuesday, September 13, 2022 at 11:27:54 AM UTC-5 Mike Kilmer wrote: > After having upgraded from Django 3 to 4 the save_model() method isn't > running, though the form it imports

save_model doesn't run on Django version 4

After having upgraded from Django 3 to 4 the save_model() method isn't running, though the form it imports does. ``` class MyCoolMapAdmin(SuperUserChangeOnlyMixIn, FilterByOwnerAdmin): form = MyCoolModelForm print("this prints on app initialization") def save_model(self,

hello everyone please can someone help me with my problem is very important please Environment: Request Method: GET Request URL: http://127.0.0.1:8000/user/ Django Version: 4.0.4 Python Version: 3

ogle.com/d/msgid/django-users/afc98569-1c64-4322-a533-d62a1a297115n%40googlegroups.com. Environment: Request Method: GET Request URL: http://127.0.0.1:8000/user/ Django Version: 4.0.4 Python Version: 3.10.4 Installed Applications: ['django.contrib.admin', 'django.co

Quit the server with CTRL-BREAK. code 400, message Bad request version ('ÚÚ\x13\x01\x13\x02\x13\x03À+À/

Hi , I keep having this error whenever i run the python manage.py runserver Django version 3.2.7, using settings 'crm.settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CTRL-BREAK. code 400, message Bad request version ('ÚÚ\x13\x01\x13\x02\x13\x03À+À/À,À0̨̩À

Re: Production deployments and Version Control for DJango projects

Hi, After some review we decided to go with Jenkins for continuous integration and deployment. Our development server was deployed on Ubuntu 18.x with Postgres DB and Python 3 virtual environment, DJango and GIT. Now we are planning to setup Jenkins server on the same dev. server so that we

Re: urls 1.11 use task how to use 3.0.6 version

You can now easily write your URL patterns like this. from django.urls import path urlpatterns = [ path("", someview, name="somename") ] On Mon, Jun 15, 2020 at 5:52 PM Kayode Oladipo wrote: > Use the path( ) method. > > from django.urls import path > > path('',...) > > On Mon, Jun 15,

Re: urls 1.11 use task how to use 3.0.6 version

Use the path( ) method. from django.urls import path path('',...) On Mon, Jun 15, 2020, 2:21 PM Adya Mit wrote: > (?P\d+)/$ django > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving

urls 1.11 use task how to use 3.0.6 version

(?P\d+)/$ django -- 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 to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit

Import error on version 3.1a1

Hi guys, Am getting the below error when we I tried updating to 3.1a1 from 3.0.6 from rest_framework import filters as rest_filters File "/home/jules/.cache/pypoetry/virtualenvs/plum-TXT4_AUl-py3.8/lib/python3.8/site-packages/rest_framework/filters.py", line 11, in from

Import error on version 3.1a1

Hi guys, Am getting the below error when we I tried updating to 3.1a1 from 3.0.6 from .router import router File "/home/jules/plum/plum/router.py", line 4, in from plum.plum_task.views_api import TaskViewSet, TaskStatusViewSet File "/home/jules/plum/plum/plum_task/views_api.py",

Re: Cuando estoy descargango al version 3.0.5 de django , me dice fatal error al comenzar, A que se debe y como solucionar para instalar esa versión ?

Antes de instalar Django, debe instalar la máquina virtual, ¿ya lo hizo? Em segunda-feira, 20 de abril de 2020 09:43:01 UTC-3, german salcedo aragon escreveu: > > Sale fatal error , al instalar django versión 3.0.5. > Ayuda y decirme porque sale ese aviso. > Gracias. > -- You received this

Cuando estoy descargango al version 3.0.5 de django , me dice fatal error al comenzar, A que se debe y como solucionar para instalar esa versión ?

Sale fatal error , al instalar django versión 3.0.5. Ayuda y decirme porque sale ese aviso. Gracias. -- 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 to

Re: Production deployments and Version Control for DJango projects

Hi , Try Jenkins also for Continuous Integration (CI) Regards Jegatheeswaran sundaravadivel On Sun, 19 Apr 2020 at 22:23, Ram wrote: > Thank you, all. We started with GIT hub and planning to add > ansible-playbook later in our development phase. > > Best regards > ~Ram > > On Sat, Feb 15, 2020

Re: Production deployments and Version Control for DJango projects

Thank you, all. We started with GIT hub and planning to add ansible-playbook later in our development phase. Best regards ~Ram On Sat, Feb 15, 2020 at 2:55 AM Kasper Laudrup wrote: > Hi Aldian, > > On 15/02/2020 05.57, Aldian Fazrihady wrote: > > Try ansible-playbook > > > > That's exactly

Re: Production deployments and Version Control for DJango projects

Hi Aldian, On 15/02/2020 05.57, Aldian Fazrihady wrote: Try ansible-playbook That's exactly what Ansible was designed for, so I agree that this would be the obvious route to go. No reason not to use git for source control and then Ansible to automate the deployment. Kind regards,

Re: Production deployments and Version Control for DJango projects

Hi Sam, On 15/02/2020 05.58, Sam Hefer wrote: Bitbucket is great if you don’t like Git env. It has a great interface. Bitbucket is more or less a web frontend to git, so it can hardly be regarded as an alternative to git. But I agree that the git command line interface isn't exactly the

Re: Production deployments and Version Control for DJango projects

ed procedure and tools to automate the > deployment and manage the version control. I know GIT is one option but do > you guys any other open source tools for souce code management. > > Best Regards, > ~Ram > > -- > You received this message because you are subscribed to the G

Re: Production deployments and Version Control for DJango projects

rovide me documented procedure and tools to automate the > deployment and manage the version control. I know GIT is one option but do > you guys any other open source tools for souce code management. > > Best Regards, > ~Ram > -- > You received this message because yo

Production deployments and Version Control for DJango projects

and tools for source code management and both dev & production servers deployments. Could someone provide me documented procedure and tools to automate the deployment and manage the version control. I know GIT is one option but do you guys any other open source tools for souce code management.

Re: Django Version to be used on for Windows Server 2016 and MS SQL 2016

; I am not sure about the compatibility and version of Django to use on > Windows Server 2016 with IIS 10 and I want the Django to be integrated > seamlessly with MS SQL server 2016 so any module or library suggestion > for the same. > > Say I wish to run the Django application on Jyth

Re: Django Version to be used on for Windows Server 2016 and MS SQL 2016

. *Maybe , you will get your answer.* *Thanks * *RJ * On Mon, Sep 2, 2019 at 7:09 PM Mahaveerchand Jain < mahaveerchand.j...@gmail.com> wrote: > Dear All, > > I have Windows Server 2016 , IIS 10 and the Database is MS SQL 2016. > > I am not sure about the compatibility a

Django Version to be used on for Windows Server 2016 and MS SQL 2016

Dear All, I have Windows Server 2016 , IIS 10 and the Database is MS SQL 2016. I am not sure about the compatibility and version of Django to use on Windows Server 2016 with IIS 10 and I want the Django to be integrated seamlessly with MS SQL server 2016 so any module or library

Re: Local django server - login fails with new safari version

. I tried that but I still have the same error. > > On Thursday, 8 August 2019 17:54:00 UTC+1, Stephen McGonigal wrote: >> >> I've updated my MacBook to the latest Mojave 10.14.6 version. Since that >> update I'm not able to login into my locally installed django webserver >

Re: Local django server - login fails with new safari version

Thanks Balu. I tried that but I still have the same error. On Thursday, 8 August 2019 17:54:00 UTC+1, Stephen McGonigal wrote: > > I've updated my MacBook to the latest Mojave 10.14.6 version. Since that > update I'm not able to login into my locally installed django webserver >

Re: Local django server - login fails with new safari version

Please clear your cache and try again On Thu, Aug 8, 2019 at 10:23 PM Stephen McGonigal < mcgonigalstep...@gmail.com> wrote: > I've updated my MacBook to the latest Mojave 10.14.6 version. Since that > update I'm not able to login into my locally installed django webserver > using

Local django server - login fails with new safari version

I've updated my MacBook to the latest Mojave 10.14.6 version. Since that update I'm not able to login into my locally installed django webserver using Safari anymore. I always get the error message "Invalid CSRF token". With Chrome it's working. -- You received this message b

Re: sqlite update on CentOS 7 for latest django version

s nothing to do with > running "migrate", being in a virtual environment, or settings.py. > > Jani - I tried compiling the latest Python manually - it was actually > super easy - but even with the latest Python, importing _sqlite3 and > checking the version, I still see the ol

Re: sqlite update on CentOS 7 for latest django version

he latest Python, importing _sqlite3 and checking the version, I still see the old version. I don't think sqlite is built into Python anymore - I think sqlite is some sort of library that Python uses. It seems not to be /usr/bin/sqlite3. I think that's just the binary that lets you interact with an

Re: sqlite update on CentOS 7 for latest django version

Hi. I think Python has built in version so you might need to build custom version of python. Pyenv is pretty neat tool to handle custom python builds. ke 17. heinäk. 2019 klo 21.36 Tal kirjoitti: > Or is Python's sqlite built into Python, not depending on /usr/bin/sqlite3 > at all? >

Re: sqlite update on CentOS 7 for latest django version

ng sqlite3 or db file extension. On Wednesday, July 17, 2019 at 2:14:54 PM UTC-4, Tal wrote: > > When using the latest django from PyPI in CentOS 7, running "./manage.py > runserver" gives an error about sqlite being too old. > Since there's no newer sqlite version in the CentOS r

Re: sqlite update on CentOS 7 for latest django version

Or is Python's sqlite built into Python, not depending on /usr/bin/sqlite3 at all? Would I have to recompile Python for a newer version of sqlite that django can use? PS. I know I can downgrade django. I'm wondering how complex it is to compile a new version of sqlite for it to use

sqlite update on CentOS 7 for latest django version

When using the latest django from PyPI in CentOS 7, running "./manage.py runserver" gives an error about sqlite being too old. Since there's no newer sqlite version in the CentOS repos, I tried building sqlite from scratch: curl -L https://www.sqlite.org/2019/sqlite-amalgamation-3290

django/apache/ubuntu server18.04 openssl not found after package upgrade / libssl.so.1.1: version `OPENSSL_1_1_1' not found

fairly common - though I didn´t manage to fix it till now, it never really bothered. Though after the package upgrade it raises a new error message (which will raise itself again for 3 times) below - the one with "ImportError: /usr/lib/x86_64-linux-gnu/libssl.so.1.1: version `OPENSSL_1_1_1"

Re: upgrading the pip version in dockerized django container

wrote: > > I am trying to upgrade pip version in docker > > > snj@snj-ThinkPad-T440p:~/school$ sudo docker-compose run web pip install > --upgrade pip > Starting school_db_1 ... done > Collecting pip > Downloading > https://files.p

upgrading the pip version in dockerized django container

I am trying to upgrade pip version in docker snj@snj-ThinkPad-T440p:~/school$ sudo docker-compose run web pip install --upgrade pip Starting school_db_1 ... done Collecting pip Downloading https://files.pythonhosted.org/packages/d8/f3

Re: “python -m django --version” 1.11.18 Cannot update to 2.1

d keep them > up-to-date. > > The if you want to take a more manual approach, you could download a gzip > file from the Django Project web site and install the most recent 2.1 > version there. > > What I would suggest is that, when you get a better understanding of > Django a

Re: “python -m django --version” 1.11.18 Cannot update to 2.1

download a gzip file from the Django Project web site and install the most recent 2.1 version there. What I would suggest is that, when you get a better understanding of Django and Python, you can start using virtualenvwrapper to set up your development environment(s). There is a slight learning curve

“python -m django --version” 1.11.18 Cannot update to 2.1

I'm new to Python and Django, I watched a tutorial that requires me to have Django 2.1. When I type in "python -m django --version" - my Ubuntu terminal says 1.11.18 But, when I type "django-admin --version" - terminal says 2.1 This didn't bother me until I reached part 6

Re: How can download the offline version of Django Rest Framework

You can install djangorestframework package using pip. Just read the documents from djangorestframework.com On Wed, Feb 6, 2019, 12:11 AM I am not always online but I like to work with the Django Rest Framework. > How can I get it offline. > > -- > You received this message because you are

How can download the offline version of Django Rest Framework

I am not always online but I like to work with the Django Rest Framework. How can I get it offline. -- 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 to

Re: how to fix this problem using 2.1.3 version

okay thank you lets me trying On Mon, Nov 26, 2018 at 6:35 AM Yavin Aalto Arba wrote: > It's kinda all over the place. > > 1. conventions: > urlpatterns is a list not a tuple > 2. > 'restaurants.views', without include? what's this for? > > 3. You did not close the parenthesis correctly in the

Re: how to fix this problem using 2.1.3 version

On Mon, Nov 26, 2018 at 04:34:42PM +0200, Yavin Aalto Arba wrote: > It's kinda all over the place. > > 1. conventions: > urlpatterns is a list not a tuple > 2. > 'restaurants.views', without include? what's this for? > > 3. You did not close the parenthesis correctly in the second item, here's

Re: how to fix this problem using 2.1.3 version

It's kinda all over the place. 1. conventions: urlpatterns is a list not a tuple 2. 'restaurants.views', without include? what's this for? 3. You did not close the parenthesis correctly in the second item, here's how its supposed to be written: path('',ListView.as_view(model=Food,

Re: how to fix this problem using 2.1.3 version

even if i close it is not working On Mon, Nov 26, 2018 at 5:54 AM Michal Petrucha < michal.petru...@konk.org> wrote: > On Mon, Nov 26, 2018 at 02:48:25PM -0800, Abba Haruna wrote: > > # from django.conf.urls import patterns, url > > from django.conf.urls.static import static > > from

Re: how to fix this problem using 2.1.3 version

On Mon, Nov 26, 2018 at 02:48:25PM -0800, Abba Haruna wrote: > # from django.conf.urls import patterns, url > from django.conf.urls.static import static > from django.views.generic import ListView > from restaurants.models import Food > from django.conf import settings > > urlpatterns =

Re: how to fix this problem using 2.1.3 version

# from django.conf.urls import patterns, url from django.conf.urls.static import static from django.views.generic import ListView from restaurants.models import Food from django.conf import settings urlpatterns = ('restaurants.views', path('',ListView.as_view(model=Food,

Re: how to fix this problem using 2.1.3 version

Yes lets me show you the code On Mon, Nov 26, 2018 at 5:47 AM Yavin Aalto Arba wrote: > did you import settings? > > On Mon, 26 Nov 2018 at 15:34, Abba Haruna wrote: > >> if settings.DEBUG: >> # urlpatterns += patterns('', >> # ('media/(?P.*)', >> # 'django.views.static.serve', >> #

Re: how to fix this problem using 2.1.3 version

did you import settings? On Mon, 26 Nov 2018 at 15:34, Abba Haruna wrote: > if settings.DEBUG: > # urlpatterns += patterns('', > # ('media/(?P.*)', > # 'django.views.static.serve', > # {'document_root': settings.MEDIA_ROOT})) > > > > this is the result > > File

how to fix this problem using 2.1.3 version

if settings.DEBUG: # urlpatterns += patterns('', # ('media/(?P.*)', # 'django.views.static.serve', # {'document_root': settings.MEDIA_ROOT})) this is the result File "C:\Users\Abba\Desktop\rest_picker\restaurants\urls.py", line 22 if settings.DEBUG: ^

Re: Running a single version of my Django app but with two databases: one for dev and one for prod

On Mon, Sep 24, 2018 at 03:18:46PM -0700, jim_rain wrote: > Hi, > > I'm developing a Django app, it's hosted on an EC2 instance so I'm using > wsgi, even in development. I would like to create a production and a > development version where really the only things tha

Re: Running a single version of my Django app but with two databases: one for dev and one for prod

to be honest, this seems like much more effort than its worth. -- 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 to django-users+unsubscr...@googlegroups.com. To

Re: Running a single version of my Django app but with two databases: one for dev and one for prod

> wsgi, even in development. I would like to create a production and a > development version where really the only things that are different are the > two databases. I want the code to be the same on both. I figured I could > just have two settings files and two wsgi.py f

Point-in-Time version history with Django with propose and commit or reject

Dear Django users. I am looking into the so-called Point-In-Time architecture for databases with version history. See e.g. https://www.red-gate.com/simple-talk/sql/database-administration/database-design-a-point-in-time-architecture/ One reason I like PTA is that a version history for my

Running a single version of my Django app but with two databases: one for dev and one for prod

Hi, I'm developing a Django app, it's hosted on an EC2 instance so I'm using wsgi, even in development. I would like to create a production and a development version where really the only things that are different are the two databases. I want the code to be the same on both. I figured I

Re: Using Subdomains in Version 2.1.7

rver >> >> I get the error >> >> ModuleNotFoundError: No module named 'django.core.urlresolvers' >> >> What would be the problem? >> >> django-admin version => 2.1.7 >> OS platform => Kali Linux >> > -- > You received this message becaus

Re: Using Subdomains in Version 2.1.7

re of installing subdomains according to > https://django-subdomains.readthedocs.io/en/latest/ but when I try > python3 manage.py runserver > > I get the error > > ModuleNotFoundError: No module named 'django.core.urlresolvers' > > What would be the problem? > > djang

Using Subdomains in Version 2.1.7

'django.core.urlresolvers' What would be the problem? django-admin version => 2.1.7 OS platform => Kali Linux -- 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

Re: Concerning CVE-2018-14574: is there a open redirect possibility in CommonMiddleware of version 1.9.5

r your supported versions policy, Django 1.10 and > older are no longer supported. > But can you indicated me if there is an open redirect possibility in > CommonMiddleware of version 1.9.5. > If not affected, I want to avoid to have to find ressources (money and > people) to p

Concerning CVE-2018-14574: is there a open redirect possibility in CommonMiddleware of version 1.9.5

I understand that per your supported versions policy, Django 1.10 and older are no longer supported. But can you indicated me if there is an open redirect possibility in CommonMiddleware of version 1.9.5. If not affected, I want to avoid to have to find ressources (money and people) to perform

Re: python -m django --version

hi Basavaraj, you can use the command $ python -V for more commands you can use $ python --help I hope this helps you *Franklin Sarmiento* *Full-stack developer* *skype: franklin.s.dev* *Twitter: @franklinitiel* *linkedin: Franklin

Re: python -m django --version

basic python command line arg. you can see it when executing `python --help` in the terminal. -m mod : run library module as a script (terminates option list) -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and

python -m django --version

Hi What is usage of -m command in this command line "python -m django --version". Regards, Basav -- 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

Re: Not able to connect to SQL Server 2012 from current version of DJango and Python

the dev for that library has specified that this is not compatible with django 2.1. so your options are to either find another connector library compatible with 2.1 or downgrade to using 2.0.x https://github.com/michiya/django-pyodbc-azure/blob/azure-2.0/setup.py#L29 > -- You received this

Not able to connect to SQL Server 2012 from current version of DJango and Python

Hi All, I am trying to connect to SQL server 2012 using Pyodbc and DJango framework but the version of Django is 2.1. Now, when I try to connect using below code when I only have Pyodbc installed then the below code doesnot run. DATABASES = { 'default': { # 'ENGINE': '{ODBC Driver 11

Re: DJANGO Migrations from older version : South db

original models.py files just run "python manage.py > makemigrations" and then "python manage.py migrate". > > On Wednesday, 02 May, 2018 05:11 PM, Ank wrote: > > Dear All, > > I would like to do some migrations that are compatible with older django &g

Re: DJANGO Migrations from older version : South db

If you have the original models.py files just run "python manage.py makemigrations" and then "python manage.py migrate". On Wednesday, 02 May, 2018 05:11 PM, Ank wrote: Dear All, I would like to do some migrations that are compatible with older django version using

DJANGO Migrations from older version : South db

Dear All, I would like to do some migrations that are compatible with older django version using southdb to the newer version. How can these files be updated.iḿ attaching one of the file that is needed to be migrated. Any help will be appreciated Best Ank -- You received this message

Re: Django Version update for my project

Hi - see my comments below. 2018-03-30 8:44 GMT+02:00 Haroon Ahmed <haroon...@gmail.com>: > Hi, > > I want to update my Django version from Django 1.9.8 to Django 2.0.3 > because it is mentioned in the Django 1.9.8 official document that this > version has secur

Django Version update for my project

Hi, I want to update my Django version from Django 1.9.8 to Django 2.0.3 because it is mentioned in the Django 1.9.8 official document that this version has security issues. https://docs.djangoproject.com/en/1.9/internals/release-process/#backwards-compatibility-policy 'This document

redirect() doesn't work with a mock object in version 2

Hello, When I try to call the django.shortcuts.redirect function with a Mock() object from unittest.mock, it results in error. I've found that, the problem happens in iri_to_uri function in django.utils.encoding. It used to use force_bytes in earlier versions of django. Any idea how to use a

Re: the version 2.0.1 login function refuses to take arguments... Login(request user)

On Thursday, January 25, 2018 at 4:50:10 AM UTC, Ozzy Walsh wrote: > > It would be helpful if you included the code associated with this as well. > > On Thursday, January 25, 2018 at 12:37:24 AM UTC, simon munuve wrote: >> >> Check the attached file ... >> > The actual code. Nobody can tell how

Re: the version 2.0.1 login function refuses to take arguments... Login(request user)

It would be helpful if you included the code associated with this as well. On Thursday, January 25, 2018 at 12:37:24 AM UTC, simon munuve wrote: > > Check the attached file ... > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe

the version 2.0.1 login function refuses to take arguments... Login(request user)

Check the attached file ... -- 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 to django-users+unsubscr...@googlegroups.com. To post to this group, send email to

Re: Django rest framework Version

Hi, Out of curiosity, is there anything wrong with the latest version ? Regards, Xavier. > Le 9 janv. 2018 à 04:59, Rakhee Menon <menonrakhe...@gmail.com> a écrit : > > Hey!!! > Please can anyone tell whats the stable version of django rest framework to > be used for

Re: Django rest framework Version

Hi, Just get the latest version of DRF (currently 3.7.7) - as long as the version of django you are running is supported by the DRF version. Regards, Andréas 2018-01-09 4:59 GMT+01:00 Rakhee Menon <menonrakhe...@gmail.com>: > Hey!!! > Please can anyone tell whats the stable versi

Django rest framework Version

Hey!!! Please can anyone tell whats the stable version of django rest framework to be used for production. Thanks in Advance. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving e

Re: 404 for some matching urls too (Version 2)

On Dec 31, 2017 7:26 AM, "Sundararajan Seshadri" wrote: Thanks for the support and responses. The error was due to an interesting line of code. I had a middleware where I used: match = resolve(request.get_full_path()) and this was causing the error I

Re: 404 for some matching urls too (Version 2)

Seshadri wrote: > > I do not know the mistake I am likely to be committing. In Django Version > 2, I have a feeling that URL matching fails whenever there are query > variables. > > When I try to log into Admin module, the login screen comes. But when a > 'next' query va

Re: 404 for some matching urls too (Version 2)

admin/ [name='index'] admin/ login/ [name='login'] admin/ logout/ [name='logout'] admin/ password_change/ [name='password_change'] admin/ password_change/done/ [name='password_change_done'] admin/ jsi18n/ [name='jsi18n'] admin/ r/// [name='view_on_site'] .. (corresponds to the tables defined)

Re: 404 for some matching urls too (Version 2)

Please post your urls.py, this looks strange: admin/ [name='index'] > admin/ login/ [name='login'] > admin/ logout/ [name='logout'] > admin/ r/// [name='view_on_site'] > admin/ ^(?Prsi|auth)/$ [name='app_list'] > login/ [name='login'] > logout/ [name='logout'] > authissue [name='authissue'] > --

404 for some matching urls too (Version 2)

I do not know the mistake I am likely to be committing. In Django Version 2, I have a feeling that URL matching fails whenever there are query variables. When I try to log into Admin module, the login screen comes. But when a 'next' query variable is attached, I get a 404. Similarly when I

Re: How do I know what version a patch is included in?

Thanks, I think I understand... On Wednesday, December 20, 2017 at 6:32:52 PM UTC, Andrew Buchan wrote: > > I'm being affected by this bug: > https://code.djangoproject.com/ticket/28562 which was fixed 4 months ago. > > Somewhere on the ticket page it says: > > Version:

Re: How do I know what version a patch is included in?

Hi. Tickets do always have a reference to changeset (commit) where that ticket is fixed. All bugs are always fixed in master (dev version of django). Then depending on a case fix maybe backported to some previous version. In this particular case last commen contais changeset that contains

Re: How do I know what version a patch is included in?

I'm sorry, but I still don't see how you determined that. I can follow the merge request, and the commit, but I can find anything that links to a version from either of those, though this is getting into the arena of git. I know it's in 2.0 now, but am concerned that I wasn't able to find that out

Re: How do I know what version a patch is included in?

it's not very obvious that issue is fixed in 2.0+ 20.12.2017 8.33 ip. "Andrew Buchan" <andyha...@gmail.com> kirjoitti: I'm being affected by this bug: https://code.djangoproject.com/ticket/28562 which was fixed 4 months ago. Somewhere on the ticket page it says: Version: 1.1

How do I know what version a patch is included in?

I'm being affected by this bug: https://code.djangoproject.com/ticket/28562 which was fixed 4 months ago. Somewhere on the ticket page it says: Version: 1.11 → master Which is the only reference to version I found anywhere on the page, so I assumed this meant the fix was in 1.11 I've just

Re: Saving webp image near jpg version

Actually, you need to use any background library ( like https://github.com/arteria/django-background-tasks/ ) for processing large-time operations such as image processing. On Friday, 17 November 2017 15:24:25 UTC+2, Дмитрий Горобец wrote: > > I want to save webp image near jpg v

Saving webp image near jpg version

I want to save webp image near jpg version. Now I'm doing it this way: class ProductImage(models.Model): product = models.ForeignKey( to=Product, related_name='images', on_delete=models.CASCADE, ) image = models.ImageField( upload_to

RE: Error in django 1.8.7 version with python 2.7.12

It looks like you’re running it in Python 3, not Python 2.7.12. I would start looking there. From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Ankush Chauhan Sent: Friday, November 10, 2017 4:35 AM To: Django users Subject: Error in django 1.8.7 version

Error in django 1.8.7 version with python 2.7.12

I am getting the following trackback error message when I run command(python manage.py runserver) on ubuntu OS: Traceback (most recent call last): File "manage.py", line 10, in execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

ib_bootstrap.SourceFileLoader, >> DefaultProvider) >> AttributeError: module 'importlib._bootstrap' has no attribute >> 'SourceFileLoader' >> --- >> >> >> and i tried to upgrade the pip3 and still the same error. >> >> Please help to

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

teError: module 'importlib._bootstrap' has no attribute > 'SourceFileLoader' > --- > > > and i tried to upgrade the pip3 and still the same error. > > Please help to figure it out. > > Thanks > > Ross > > > > On Sunday, August 13, 2017 at 8:1

Re: regarding virtualenv and python version 3.5 or 3.4 or other versions

se help to figure it out. Thanks Ross On Sunday, August 13, 2017 at 8:11:57 AM UTC-7, Avraham Serour wrote: > > I suggest using 3.6, which is the current stable release > if your machine or the server doesn't have this version installed you may > compile it yourself and create the

  1   2   3   4   5   6   7   8   >