Re: [Django] #29164: Problem in Integrating the pyspark with django

[Django]

#29164: Problem in Integrating the pyspark with django
-+-
 Reporter:  Gavaskar |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Packaging|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Pyspark with django  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gavaskar):

 * cc: Gavaskar (added)
 * component:  Uncategorized => Packaging
 * type:  Uncategorized => Cleanup/optimization


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a64fde5b1752ce3d50fdba5d934d85ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29164: Problem in Integrating the pyspark with django

[Django]

#29164: Problem in Integrating the pyspark with django
-+-
 Reporter:  Gavaskar |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  Pyspark with django  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gavaskar):

 * Attachment "problems in integrating the pyspark in django.docx" added.


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ba3a70d6f3fa9481523257a4e77c7ed9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29164: Problem in Integrating the pyspark with django

[Django]

#29164: Problem in Integrating the pyspark with django
-+-
   Reporter:  Gavaskar   |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  1.11
  Uncategorized  |
   Severity:  Normal |   Keywords:  Pyspark with django
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I worked on pyspark with python language in anaconda ,it works fine.But
 when I try to integrate the pyspark with django 1.11.4 . It shows some
 error. (i.e.,) it reads the first line of the file and shows path doesn't
 exists.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.15ae325d31c2f9bcf2edff2c30409d17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

[Django]

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Daniel Miller):

 I implemented generic CTE support for Django: https://github.com/dimagi
 /django-cte

 Would be happy to contribute this to be included with Django. Feedback is
 welcome.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.940c05478c4ad066c30b8b62395a484b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29163: When uploading, if file size is greater than the FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed up.

[Django]

#29163: When uploading, if file size is greater than the
FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed
up.
-+-
 Reporter:  Jibin|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  File |  Version:  2.0
  uploads/storage|
 Severity:  Release blocker  |   Resolution:  duplicate
 Keywords:   | Triage Stage:
  TemporaryFileUploadHandler |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jibin):

 * status:  new => closed
 * resolution:   => duplicate


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.d7ed6eab1199c15d84baff67a23a56c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29163: When uploading, if file size is greater than the FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed up.

[Django]

#29163: When uploading, if file size is greater than the
FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed
up.
-+-
 Reporter:  Jibin|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  File |  Version:  2.0
  uploads/storage|
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
  TemporaryFileUploadHandler |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jibin):

 Yes, it is. Closing the ticket.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.94fe3d390665bc95b678ed8ee3f27bf7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29163: When uploading, if file size is greater than the FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed up.

[Django]

#29163: When uploading, if file size is greater than the
FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed
up.
-+-
 Reporter:  Jibin|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  File |  Version:  2.0
  uploads/storage|
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
  TemporaryFileUploadHandler |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Is it a duplicate of #28540?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.95a175b52aa8246ffacfb586dcb011aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29141: Warning about password truncation with BCryptPasswordHasher incorrect

[Django]

#29141: Warning about password truncation with BCryptPasswordHasher incorrect
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"56a302f338761cdda3cc1116a89687051c7c005a" 56a302f]:
 {{{
 #!CommitTicketReference repository=""
 revision="56a302f338761cdda3cc1116a89687051c7c005a"
 Fixed #29141 -- Corrected BCryptPasswordHasher's docstring about
 truncation.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.455ec0dd5efd4ff8ea959a989c94e361%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28909: Use unpacking generalizations added in Python 3.5

[Django]

#28909: Use unpacking generalizations added in Python 3.5
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  unpacking| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"074a2f7f58cfab807ae72b09e634cad30a895369" 074a2f7f]:
 {{{
 #!CommitTicketReference repository=""
 revision="074a2f7f58cfab807ae72b09e634cad30a895369"
 Refs #28909 -- Simplifed code using unpacking generalizations.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.573c3341911beeefb909fa7c0d23c7c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21963: makemessages still ignores translations in templates with inline comment tags

[Django]

#21963: makemessages still ignores translations in templates with inline comment
tags
-+-
 Reporter:  Ihor Kaharlichenko   |Owner:  Sergey
    |  Kolosov
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  makemessages,| Triage Stage:  Accepted
  template, gettext, xgettext|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 Current patch simply reverts a number of changes from #19552. Including
 adding warnings (i.e. it removes them again), which seems a loss.
 It reverses the logic of a number of test cases, going against decisions
 made in #19552.

 I've suggested on the ticket that we try and reach a consensus on the
 mailing list on the correct behaviour for each type of case. From there a
 resolution (without just reverting the previous work) should be easier.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/098.ca2d94b8c6413f2a9c0abeea9a22a142%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29163: When uploading, if file size is greater than the FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed up.

[Django]

#29163: When uploading, if file size is greater than the
FILE_UPLOAD_MAX_MEMORY_SIZE, the permissions of the file on disk is screwed
up.
-+-
   Reporter: |  Owner:  nobody
  Jibinjohnkj|
   Type: | Status:  new
  Uncategorized  |
  Component:  File   |Version:  2.0
  uploads/storage|
   Severity:  Release|   Keywords:
  blocker|  TemporaryFileUploadHandler
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I have Nginx+Gunicorn server with Django running on Ubuntu 16.04 LTS. I
 have a 'media' folder with appropriate ACL and umask setup. When
 uploading, if file size is less than FILE_UPLOAD_MAX_MEMORY_SIZE  things
 work  as expected.


 {{{
 getfacl sample.ipa
 # file: sample.ipa
 # owner: nobody
 # group: nogroup
 user::rw-
 group::rwx  #effective:-w-
 mask::-w-
 other::r--
 }}}


 But when the file size is larger than FILE_UPLOAD_MAX_MEMORY_SIZE, the
 permissions get screwed up. See the difference in 'mask' and 'other'
 permissions. Since 'other' cannot read the file, Django returns "403
 Forbidden"


 {{{
 getfacl sample.ipa
 # file: sample.ipa
 # owner: nobody
 # group: nogroup
 user::rw-
 group::rwx  #effective:---
 mask::---
 other::---
 }}}

 If you increase FILE_UPLOAD_MAX_MEMORY_SIZE to greater than the actual
 file size, the issue is solved.

 Could be a problem related to TemporaryFileUploadHandler.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/054.b068b310e0781f229b106b0f865ab4f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22449: Colorize output of test results

[Django]

#22449: Colorize output of test results
-+-
 Reporter:  Jake Rothenbuhler|Owner:  Yuri
 |  Shikanov
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.f4e938a1493240842f6774e2e9a49378%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29161: Remove BCryptPasswordHasher from the default PASSWORD_HASHERS

[Django]

#29161: Remove BCryptPasswordHasher from the default PASSWORD_HASHERS
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"5b589a47b9ac2c8bdd13ba837fea37991a1457b9" 5b589a47]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b589a47b9ac2c8bdd13ba837fea37991a1457b9"
 Fixed #29161 -- Removed BCryptPasswordHasher from PASSWORD_HASHERS.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.312ae2c7b5e6bb95fea3ec5717c8d77a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29162: urls issue on hosted server

[Django]

#29162: urls issue on hosted server
---+--
 Reporter:  Chris Shaw |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.10
 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 Tim Graham):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 See TicketClosingReasons/UseSupportChannels for ways to get help. I'm not
 sure if you've provided enough information to determine the problem.

 If you confirm a bug in Django, then it's appropriate to open a ticket
 with details.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.22953b4612dc85a3146e480009b1ea70%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26291: loaddata cannot deserialize fixtures with forward references and natural foreign keys

[Django]

#26291: loaddata cannot deserialize fixtures with forward references and natural
foreign keys
-+-
 Reporter:  Peter Inglesby   |Owner:  Peter
 |  Inglesby
 Type:  New feature  |   Status:  assigned
Component:  Core |  Version:  1.9
  (Serialization)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3d55fd07563b50a72cb39651832e9d6d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29153: Ease customizing the label attrs on a model form field

[Django]

#29153: Ease customizing the label attrs on a model form field
--+--
 Reporter:  ChristophRob  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Forms |  Version:  2.0
 Severity:  Normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by ChristophRob):

 Replying to [comment:3 Tim Graham]:
 > Thanks for the clarifying edits. I guess you're running into the problem
 described on [https://stackoverflow.com/questions/6959178/how-to-set-css-
 class-of-a-label-in-a-django-form-declaration Stack Overflow].
 >
 > I'm not sure if the use case is common enough to add a field attribute
 for this. Usually I style labels using CSS3 selectors. If you can get
 consensus on a proposal on the DevelopersMailingList, we can reopen the
 ticket. Generally, the consensus has been that if you need to make much
 customization to form rendering, you should iterate over the fields rather
 than using `{{ form }}`.

 Thank you Tim, for your response. Yes indeed, thats exactly my problem. As
 i am using bootstrap 3 it is necessary, to set a "control-label" class to
 the label. Especially for errors in form validation. It seems to me that
 in bootstrap 4, the team just gave up, and does not design labels with
 form errors anymore by default. So i am also gonna change to bootstrap 4,
 and sadly no label error design. So i think you are right, to not fix
 this.

 Still it makes me wonder that the customizable label_tag is already half
 implemented.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.7ab42e015d9f0bd453c968ed58a64e53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29162: urls issue on hosted server

[Django]

#29162: urls issue on hosted server
---+--
 Reporter:  cjshaw1976 |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.10
 Severity:  Normal |   Resolution:
 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 cjshaw1976):

 * version:  2.0 => 1.10


Comment:

 Changed the version to 1.10 as the attached images are per 1.10. The issue
 exists in ver 2.0 also.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.c0686fead1aae7b50f44cfc4e4cfe824%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29162: urls issue on hosted server

[Django]

#29162: urls issue on hosted server
---+--
 Reporter:  Chris Shaw |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  2.0
 Severity:  Normal |   Resolution:
 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 Chris Shaw):

 * Attachment "Screen Shot 2018-02-25 at 21.58.07.png" added.

 Screen shot showing exactly the same request works fine as a GET, but
 returns a 404 with a POST.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.cd3e2d3119e6518b1a983aba4fcc6d77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29162: urls issue on hosted server

[Django]

#29162: urls issue on hosted server
---+--
 Reporter:  cjshaw1976 |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  2.0
 Severity:  Normal |   Resolution:
 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 cjshaw1976):

 * Attachment "Screen Shot 2018-02-25 at 21.48.07.png" added.

 Screen shot of URLS. Please note this example is from ver 1.10.x. The same
 problem exists in ver 2.0.x.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.edb79783f629bad4dbf64adf0fd2801b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29162: urls issue on hosted server

[Django]

#29162: urls issue on hosted server
---+--
 Reporter:  Chris Shaw |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  2.0
 Severity:  Normal |   Resolution:
 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 Chris Shaw):

 * Attachment "Screen Shot 2018-02-25 at 21.34.58.png" added.

 Screen shot of error, only display root urls and not admin urls.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.309f3b2ec3cee4bcb440c248ec51ed87%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29162: urls issue on hosted server

[Django]

#29162: urls issue on hosted server
-+
   Reporter:  cjshaw1976 |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  2.0
   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  |
-+
 Good day.

 I have been trying to get my Django 1.10 and 2.0 projects working on a
 paid host. I have set up the python app with version 3.5.

 To begin, all looks good.

 As soon as I try to log into the admin area (or send a post request to any
 app), it returns a 404 error. When processing a POST request, it appears
 to only run though the root urls, and not the app urls.

 The same request done with a GET returns the page, but with a POST returns
 a 404.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.b48108276a0a6d70b73b4833097f3699%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29161: Remove BCryptPasswordHasher from the default PASSWORD_HASHERS

[Django]

#29161: Remove BCryptPasswordHasher from the default PASSWORD_HASHERS
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0062524832912010f1783686673cd2d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.