[Django] #32188: Pipenv latest version of Django is 3.0.11 rather than 3.1.*
Django
-----------------------------------------+------------------------
Reporter: joweenflores | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
I was creating a new Django App when I encountered a weird error:
{{{
return database_name == ':memory:' or 'mode=memory' in database_name
TypeError: argument of type 'WindowsPath' is not iterable
}}}
when migrating. I traced back and known that this was an issue in <=3.0.11
so I checked the Django version installed it was 3.0.11. I ran
{{{
pipenv updated --outdated
}}}
on my previous Django 3.1.3 app and got this:
{{{
Package 'Django' out-of-date: '==3.1.3' installed, '==3.0.11' available.
}}}
creating an app via
{{{
pipenv install django
}}}
defaults to installing the previous 3.0.11 version. I'm not sure where
should I report this so just posting it here FYI.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/32188>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: Joween Flores | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.1
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by Joween Flores:
Old description:
> I was creating a new Django App when I encountered a weird error:
> {{{
> return database_name == ':memory:' or 'mode=memory' in database_name
> TypeError: argument of type 'WindowsPath' is not iterable
> }}}
> when migrating. I traced back and known that this was an issue in
> <=3.0.11 so I checked the Django version installed it was 3.0.11. I ran
> {{{
> pipenv updated --outdated
> }}}
> on my previous Django 3.1.3 app and got this:
> {{{
> Package 'Django' out-of-date: '==3.1.3' installed, '==3.0.11' available.
> }}}
> creating an app via
> {{{
> pipenv install django
> }}}
> defaults to installing the previous 3.0.11 version. I'm not sure where
> should I report this so just posting it here FYI.
>
> Thanks!
New description:
I was creating a new Django App when I encountered a weird error:
{{{
return database_name == ':memory:' or 'mode=memory' in database_name
TypeError: argument of type 'WindowsPath' is not iterable
}}}
when migrating. I traced back and known that this was an issue in <=3.0.11
so I checked the Django version installed it was 3.0.11. I ran
{{{
pipenv updated --outdated
}}}
on my previous Django 3.1.3 app and got this:
{{{
Package 'Django' out-of-date: '==3.1.3' installed, '==3.0.11' available.
}}}
creating an app via
{{{
pipenv install django
}}}
defaults to installing the previous 3.0.11 version.
For now the workaround installing the specific version older than 3.1 by:
{{{
pipenv install 'django[argon2]>=3.1.*'
}}}
I'm not sure where should I report this so just posting it here FYI.
Thanks!
--
--
Ticket URL: <https://code.djangoproject.com/ticket/32188#comment:1>
Django
Reporter: Joween Flores | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.1
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by Joween Flores:
Old description:
> I was creating a new Django App when I encountered a weird error:
> {{{
> return database_name == ':memory:' or 'mode=memory' in database_name
> TypeError: argument of type 'WindowsPath' is not iterable
> }}}
> when migrating. I traced back and known that this was an issue in
> <=3.0.11 so I checked the Django version installed it was 3.0.11. I ran
> {{{
> pipenv updated --outdated
> }}}
> on my previous Django 3.1.3 app and got this:
> {{{
> Package 'Django' out-of-date: '==3.1.3' installed, '==3.0.11' available.
> }}}
> creating an app via
> {{{
> pipenv install django
> }}}
> defaults to installing the previous 3.0.11 version.
>
> For now the workaround installing the specific version older than 3.1 by:
>
> {{{
> pipenv install 'django[argon2]>=3.1.*'
> }}}
>
> I'm not sure where should I report this so just posting it here FYI.
>
> Thanks!
New description:
I was creating a new Django App when I encountered a weird error:
{{{
return database_name == ':memory:' or 'mode=memory' in database_name
TypeError: argument of type 'WindowsPath' is not iterable
}}}
when migrating. I traced back and known that this was an issue in <=3.0.11
so I checked the Django version installed it was 3.0.11. I ran
{{{
pipenv updated --outdated
}}}
on my previous Django 3.1.3 app and got this:
{{{
Package 'Django' out-of-date: '==3.1.3' installed, '==3.0.11' available.
}}}
creating an app via
{{{
pipenv install django
}}}
defaults to installing the previous 3.0.11 version.
For now the workaround installing the specific version older than 3.1 by:
{{{
pipenv install 'django>=3.1.*'
}}}
or with argon-package:
{{{
pipenv install 'django[argon2]>=3.1.*'
}}}
I'm not sure where should I report this so just posting it here FYI.
Thanks!
--
--
Ticket URL: <https://code.djangoproject.com/ticket/32188#comment:2>
Django
Reporter: Joween Flores | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
Hi. I think the appropriate place for this would be the pipenv issue
tracker. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/32188#comment:3>