Re: [Django] #16546: syncdb should tell you when it's doing something unexpected

[Django]

#16546: syncdb should tell you when it's doing something unexpected
-+-
 Reporter:  RoySmith |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Schema introspection is complicated; we aren't going to bother with it
 just to print a warning.

 The real solution will come from schema migrations. See #5934.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12500: Support for MySQL Connector/Python

[Django]

#12500: Support for MySQL Connector/Python
-+-
 Reporter:  geertjanvdk  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  backend mysql|  Someday/Maybe
  myconnpy   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 I'm not aware of "non-trivial demand" for this backend over the last three
 years. If I've missed it, please reopen.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9523: Restart runserver after translation MO files change

[Django]

#9523: Restart runserver after translation MO files change
--+
 Reporter:  wim@… |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * stage:  Someday/Maybe => Accepted


Comment:

 I think this ticket should be "accepted".

 Malcolm's had two objections: it's low priority, and it isn't obvious to
 implement. But if someone writes a good patch, we'll certainly consider
 it.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10192: Add support for App Engine

[Django]

#10192: Add support for App Engine
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.0
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  app engine   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Google [https://developers.google.com/appengine/articles/django-nonrel
 recommends using django-nonrel] to run Django on AppEngine.

 This ticket is a subset of "support NoSQL backends".

 Based on what I know of the nonrel fork, this is unlikely to happen soon.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8949: A django-stones benchmark

[Django]

#8949: A django-stones benchmark
---+-
 Reporter:  simon  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Uncategorized  |  Version:  1.0
 Severity:  Normal |   Resolution:  fixed
 Keywords:  djangocon  | Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

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


Comment:

 Since the benchmark exists, and since no one has expressed any interest in
 this ticket in a year, I'm going to close it.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5934: Database Migrations

[Django]

#5934: Database Migrations
-+-
 Reporter:  Patrick Altman   |Owner:  nobody
  |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  database db  |  Patch needs improvement:  0
  migration agile evolution  |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Someday/Maybe => Accepted


Comment:

 Andrew announced plans for [https://groups.google.com/d/topic/django-
 developers/6O7eN_OW5Z4/discussion adding schema alteration] in core and a
 migrations management app in contrib.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8173: manage.py startapp should create admin.py file

[Django]

#8173: manage.py startapp should create admin.py file
-+-
 Reporter:  julian24 |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 You can now use [https://docs.djangoproject.com/en/dev/ref/django-admin
 /#django-admin-option---template a custom app templates] for this.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19481: Django exercises for beginners

[Django]

#19481: Django exercises for beginners
---+
 Reporter:  addnab@…   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 For Django Beginners like me, I don't find the tutorials to be enough. It
 will be great if we could try our hand at DIY Django Projects ranging from
 beginner to intermediate to expert. The Projects can be listed after the
 Official Tutorial. Each Project can have the necessary pre-requisites
 documentation to go along with it. It would help get beginners quickly up
 and running with Django faster than ever once they quickly master one
 project at a time. It would be more like exercises.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19468: django doesn't encode request.path correctly in python3

[Django]

#19468: django doesn't encode request.path correctly in python3
-+
 Reporter:  aliva|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by aaugustin):

 I forgot to mention that utf-8 *is* the default, which is consistent with
 the Python changeset you're linking to.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14974: Add support for translation backends other than gettext

[Django]

#14974: Add support for translation backends other than gettext
--+
 Reporter:  marinho   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by ramiro):

 #19480 is a proposal related to this ticket and has a pull request at
 https://github.com/django/django/pull/590

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19468: django doesn't encode request.path correctly in python3

[Django]

#19468: django doesn't encode request.path correctly in python3
-+
 Reporter:  aliva|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by aaugustin):

 May I suggest a different look at these percentages?

 Django is serving two populations of programmers here:
 - the 99.x% who either use utf-8 everywhere or don't even know what an
 encoding is. The debate is moot for them because they have
 `DEFAULT_CHARSET = 'utf-8'`. And anyone who expects non ASCII URLs typed
 in a browser bar to work falls in this category.
 - the 0.y% who want non-utf-8 URLs, for whatever reason. These are people
 who have special needs and who can be assumed to know what they're doing.
 They're probably not writing consumer websites. Their software may never
 be accessed by browsers.
   - Forcing utf-8 decoding states upfront that Django doesn't support this
 use case: it'll fail in 98% of the cases and return wrong results in the
 other 2%.
   - Trying utf-8 decoding, and falling back to `DEFAULT_CHARSET`, will
 work in 98% of the cases and return the wrong result in only 2% of the
 cases. This may be missed in testing and can't be relied upon in
 production. It's a trap and it's useless.

 If you're bent on only supporting utf-8 URLs, please be upfront about it
 and don't make it a trap.

 I'm getting weary of this debate; if I haven't convinced you, do what you
 want. For the record, I don't condone non-deterministic decoding, ie.
 "here's your decoded path — well, maybe, because if it happened to be
 valid utf-8 Django decoded it with utf-8 instead".

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.