date:20130902

Re: [Django] #21018: Make the implications of order in INSTALLED_APPS more consistent

2013-09-02 Thread Django

Comment (by marfire):

''If'' this is something that should be changed, I would tend to agree
with Carl. It's a simple change (one line of code?), and shouldn't hinder
any of the work in #3591, so why not do it right away? Especially since
this behavior hasn't been, but should be, and is about to be, documented,
it would be nice to be able to say the right thing.

If the question of ''whether'' or not to change it is complicated and
needs to be considered in light of the work being done in #3591, then I
suppose it makes sense to merge it into that issue.

--
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.29e05517dbdf826b20cb887081d2163d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21023: Your documentation is poor at best.

2013-09-02 Thread Django

#21023: Your documentation is poor at best.
-+-
 Reporter:  lam2015@…|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  URL  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by ramiro:

Old description:

> Here is how you do it:
>
> URLS:
>
> from django.conf.urls import patterns, url
>
> urlpatterns = patterns('',
> url(r'^articles/(\d{4})/$', 'news.views.year_archive'),
> url(r'^articles/(\d{4})/(\d{2})/$', 'news.views.month_archive'),
> url(r'^articles/(\d{4})/(\d{2})/(\d+)/$',
> 'news.views.article_detail'),
> )
>
> You go line by line and say r = raw. This means no escape characters, the
> compiler processes what it sees.
> Next: ^ from Regular expressions means the beginning of the line
> beginning with the word articles?
> The slash is:
> Then you put parenthesis because?: GET IT?
> then there is another slash
>
> AND SO ON ONE STEP at a time
>
> THIS IS HOW YOU EXPLAIN THINGS. Make believe the person reading it doesnt
> know anything about Regular expressions. These are not standard Regex..
> not like Perl

New description:

 Here is how you do it:

 URLS:
 {{{
 from django.conf.urls import patterns, url

 urlpatterns = patterns('',
 url(r'^articles/(\d{4})/$', 'news.views.year_archive'),
 url(r'^articles/(\d{4})/(\d{2})/$', 'news.views.month_archive'),
 url(r'^articles/(\d{4})/(\d{2})/(\d+)/$',
 'news.views.article_detail'),
 )
 }}}
 You go line by line and say r = raw. This means no escape characters, the
 compiler processes what it sees.
 Next: `^` from Regular expressions means the beginning of the line
 beginning with the word articles?
 The slash is:
 Then you put parenthesis because?: GET IT?
 then there is another slash

 AND SO ON ONE STEP at a time

 THIS IS HOW YOU EXPLAIN THINGS. Make believe the person reading it doesnt
 know anything about Regular expressions. These are not standard Regex..
 not like Perl

--

-- 
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/078.ad802e8530d92dc27ddcbecd74785622%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21023: Your documentation is poor at best.

2013-09-02 Thread Django

#21023: Your documentation is poor at best.
-+-
 Reporter:  lam2015@…|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  URL  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mjtamlyn):

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


Comment:

 The tutorial aims to strike a balance between newbie developers and new to
 django developers. It is explicitly not a *python* tutorial, and a
 detailed analysis of the structure of a python regex is not helpful in
 this context.

 The current version of the docs has a number of links for understanding
 regexes better already.
 https://docs.djangoproject.com/en/1.5/intro/tutorial03/#url-argument-regex

-- 
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/078.03d02ca46e546773eb1463b2cda4cccd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21023: Your documentation is poor at best.

2013-09-02 Thread Django

#21023: Your documentation is poor at best.
-+-
 Reporter:  lam2015@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  URL  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lam2015@…):

 * 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/078.fcb3f3b6590f54c9af0e46cf5e610946%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21023: Your documentation is poor at best.

2013-09-02 Thread Django

#21023: Your documentation is poor at best.
---+--
 Reporter:  lam2015@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  URL| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
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/078.bc1a77553320214316a5ef19366ac7ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21023: Your documentation is poor at best.

2013-09-02 Thread Django

#21023: Your documentation is poor at best.
---+
 Reporter:  lam2015@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:  URL
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Here is how you do it:

 URLS:

 from django.conf.urls import patterns, url

 urlpatterns = patterns('',
 url(r'^articles/(\d{4})/$', 'news.views.year_archive'),
 url(r'^articles/(\d{4})/(\d{2})/$', 'news.views.month_archive'),
 url(r'^articles/(\d{4})/(\d{2})/(\d+)/$',
 'news.views.article_detail'),
 )

 You go line by line and say r = raw. This means no escape characters, the
 compiler processes what it sees.
 Next: ^ from Regular expressions means the beginning of the line beginning
 with the word articles?
 The slash is:
 Then you put parenthesis because?: GET IT?
 then there is another slash

 AND SO ON ONE STEP at a time

 THIS IS HOW YOU EXPLAIN THINGS. Make believe the person reading it doesnt
 know anything about Regular expressions. These are not standard Regex..
 not like Perl

-- 
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/063.66b212ee4d27389dab597f543cc76e3c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21003: BaseGeometryWidget is not idempotent

2013-09-02 Thread Django

#21003: BaseGeometryWidget is not idempotent
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by claudep):

 Here's a slightly different patch. I didn't like that we had to
 reconstruct a Geometry object at two different places in the same file.
 And I prefer to test the srid after having created the object, because you
 never know if the client has provided a value containing a parsable srid
 through a clever thing. Criticism 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.84486aafd95cd5dad6cefe5195795fcf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21018: Make the implications of order in INSTALLED_APPS more consistent

2013-09-02 Thread Django

#21018: Make the implications of order in INSTALLED_APPS more consistent
--+--
 Reporter:  marfire   |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:  duplicate
 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 mitar):

 * cc: mmitar@… (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/065.5a1773c28007933f0d5c0b20a53a2c26%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21003: BaseGeometryWidget is not idempotent

2013-09-02 Thread Django

#21003: BaseGeometryWidget is not idempotent
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by leplatrem):

 Since SRID is ignored while parsing GeoJSON ("crs" attribute), this bug
 prevents from using other serialization format than e/wkt.

 Indeed, data coming from widget is read without assigning srid during
 deserialization. If the serialized format cannot carry it, the resulting
 geometry has no srid. Which fails at first transform() operation...

-- 
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.f82b188f9c89b17a8bfbf6bc6d757764%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20876: Polls in polls

2013-09-02 Thread Django

#20876: Polls in polls
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit


Comment:

 I agree that this is an issue. I think that the best solution is to follow
 the example of the `Choice`model, so that our two models at
 https://docs.djangoproject.com/en/1.5/intro/tutorial01/#creating-models
 will look like:

 {{{
 class Question(models.Model):
 question_text = models.CharField(max_length=200)
 pub_date = models.DateTimeField('date published')

 class Choice(models.Model):
 poll = models.ForeignKey(Question)
 choice_text = models.CharField(max_length=200)
 votes = models.IntegerField(default=0)
 }}}

-- 
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.c1a638a1158e929346ffecd7f417165d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20970: Related fields docs improvements

2013-09-02 Thread Django

#20970: Related fields docs improvements
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit


Comment:

 So improvements still in order include:

 *  a mention of direct association, that is e.entry_set = some_list, which
 is often the fastest way to update a relationship.
 * a note that all the methods discussed - `add`, `create`, `remove`,
 `clear` - apply database changes immediately

-- 
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.3bfc67799479c2fe2d87879a4adadcf3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20975: Fix incorrect markup of committers list (and possibly other docs lists)

2013-09-02 Thread Django

#20975: Fix incorrect markup of committers list (and possibly other docs lists)
--+
 Reporter:  EvilDMP   |Owner:  EvilDMP
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit


-- 
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.0e3812f218a32bc20fe5513bd3b3a125%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21018: Make the implications of order in INSTALLED_APPS more consistent

2013-09-02 Thread Django

Comment (by carljm):

Is it useful to close every ticket related to `INSTALLED_APPS` handling as
a duplicate of #3591? #3591 is already a massive bite to chew, which is a
large part of why the work on that ticket has not been merged yet (and
AFAICT it's not entirely clear if or when it will be.) If anything, #3591
could really benefit from a reduction and clarification of scope, not a
creeping scope that encompasses everything about apps.

Fixing this ticket, if we decide to fix it, is a simple code change; I
don't see how it requires or benefits from being lumped in with #3591.
It's certainly not in any way a duplicate of the original motivating
feature request in #3591. If it happens to be also fixed by a hypothetical
eventual fix for #3591, great, but it's a separate issue.

All else being equal, "more smaller tickets handled independently" is
superior to "fewer big tickets".

--
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.43eb3d2be5d902f232a122b3f533142c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21007: Support for add new fields on proxy model inheritance

2013-09-02 Thread Django

* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0

Comment:

Hi; thanks for submitting this feature request. I don't understand the
feature you are requesting, though. Django does support adding new fields
on non-proxy inherited models, but the point of proxy model inheritance is
that there is no additional database table for the proxy model, it's
purely a Python-level subclass. So where would the data for these added
fields be stored? If you want to add fields to your subclass, use regular
(concrete) model inheritance, not proxy inheritance.

Feel free to reopen if you can clarify how the requested feature would
work, and how "proxy model inheritance with support for adding new fields"
would be different from normal (non-proxy) model inheritance.

--
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/081.0c4705b2c3574ce4c5dcc0c58919ced5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21003: BaseGeometryWidget is not idempotent

2013-09-02 Thread Django

#21003: BaseGeometryWidget is not idempotent
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by leplatrem):

 * has_patch:  0 => 1


-- 
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.6c689e1987eeb4744b960ddc4770c32b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20517: Jython support is not as complete as indicated

2013-09-02 Thread Django

* keywords: Jython => Jython, afraid-to-commit

Comment:

I would like to reserve this ticket for first-time committers who take
part in the [http://www.djangocon.us/schedule/presentation/7/ Don't be
afraid to commit tutorial] and the sprints at [http://djangocon.us/
DjangoCon US 2013] in September.

However, if you want to tackle this ticket before then, please
'''don't'''
hesitate. Feel free to re-assign it to yourself and do whatever you like
to 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 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/073.e63736dbb882c88027ffa83edb32d8e7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21009: Add a versionchanged note that returning cleaned_data is no longer required in clean()

2013-09-02 Thread Django

#21009: Add a versionchanged note that returning cleaned_data is no longer 
required
in clean()
--+
 Reporter:  anonymous |Owner:  EvilDMP
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by EvilDMP):

 * status:  new => assigned
 * keywords:   => afraid-to-commit
 * owner:  nobody => EvilDMP
 * easy:  0 => 1


Comment:

 I would like to reserve this ticket for first-time committers who take
  part in the [http://www.djangocon.us/schedule/presentation/7/ Don't be
  afraid to commit tutorial] and the sprints at  [http://djangocon.us/
  DjangoCon US 2013] in September.

  However, if you want to tackle this ticket before then, please
 '''don't'''
  hesitate. Feel free to re-assign it to yourself and do whatever you like
  to 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 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.e20288ba458c4e8a8b1e9ba825974303%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21022: Ensure URL naming is always preferred everywhere in the docs

2013-09-02 Thread Django

#21022: Ensure URL naming is always preferred everywhere in the docs
--+
 Reporter:  mjtamlyn  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by EvilDMP):

 * keywords:   => afraid-to-commit


Comment:

 I would like to reserve this ticket for first-time committers who take
  part in the [http://www.djangocon.us/schedule/presentation/7/ Don't be
  afraid to commit tutorial] and the sprints at  [http://djangocon.us/
  DjangoCon US 2013] in September.

  However, if you want to tackle this ticket before then, please
 '''don't'''
  hesitate. Feel free to re-assign it to yourself and do whatever you like
  to 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 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.87f459acb0301a6975717f4ab4867b75%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21022: Ensure URL naming is always preferred everywhere in the docs

2013-09-02 Thread Django

#21022: Ensure URL naming is always preferred everywhere in the docs
+
   Reporter:  mjtamlyn  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 This is when documenting reverse, get_absolute_url, the urls file itself
 etc. It should be made clear that you don't *have* to, but this should be
 the first documented solution

-- 
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.b16e73ba34720740e4ed055a5e886f1a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10964: Admin for group doesn't allow to easily add users to the group

2013-09-02 Thread Django

#10964: Admin for group doesn't allow to easily add users to the group
-+-
 Reporter:  gruszczy |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, groups,   | Triage Stage:  Accepted
  reverse M2M|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by Koen Biermans ):

 * keywords:  admin, groups => admin, groups, reverse M2M
 * needs_docs:  1 => 0
 * component:  contrib.auth => Forms
 * needs_tests:  1 => 0


Comment:

 WIP still here: https://github.com/planop/django/tree/ticket_10964

 Excluded non-nullable foreignkeys, because you would be unable to remove
 an item via the multiplechoicefield, which would be very surprising and
 does not make sense.

-- 
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.c6feed846eebde7d8433fe31498234d9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #3591: add support for custom app_label and verbose_name

2013-09-02 Thread Django

#3591: add support for custom app_label and verbose_name
--+
 Reporter:  jkocherhans   |Owner:  adrian
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+

Comment (by russellm):

 #21018 raised an interesting point about ordering in INSTALLED_APPS that
 should be tracked as part of this issue.

-- 
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.9265237ff6aec80e3dfe319c003a2d0b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21018: Make the implications of order in INSTALLED_APPS more consistent

2013-09-02 Thread Django

#21018: Make the implications of order in INSTALLED_APPS more consistent
--+--
 Reporter:  marfire   |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:  duplicate
 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 russellm):

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


Comment:

 Although it isn't obvious, this looks to me to be a duplicate of #3591
 (or, at the very least, an issue that should be considered as part of that
 work). This ticket is the placeholder for the "app refactor", which
 resolves a bunch of issues related to the startup sequence and application
 loading.

-- 
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.dce65e803430f558a30b0c7c4b5fb834%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12756: dumpdata error message should note pyyaml requirement

2013-09-02 Thread Django

* status: closed => new
* resolution: wontfix =>
* component: Documentation => Core (Serialization)
* easy: 0 => 1

Comment:

Yeah - I agree with the original request as well. We're swallowing an
ImportError, and reporting it as a "missing backend" error. The two errors
are distinct, and should be reported as such. It's not about special
casing YAML - it's about modifying our error reporting in the general case
so that if a backend has an import dependency, we accurately report the
underlying problem.

--
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/075.273469a56100ce60be2dc0fce6c586bd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 0c5786: [1.6.x] Fixed gis test to run on non gis-enabled s...

2013-09-02 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 0c5786890875f2adbcfddd0056dc2b87a768aa1e
  
https://github.com/django/django/commit/0c5786890875f2adbcfddd0056dc2b87a768aa1e
  Author: Claude Paroz 
  Date:   2013-09-02 (Mon, 02 Sep 2013)

  Changed paths:
M django/contrib/gis/tests/test_geoforms.py

  Log Message:
  ---
  [1.6.x] Fixed gis test to run on non gis-enabled settings

Refs #20998.
Backport of 973502c0 from master.



-- 
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/52248535732a1_6d871239d481033f0%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20998: Form GIS widgets render() lack of modularity

2013-09-02 Thread Django

#20998: Form GIS widgets render() lack of modularity
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  refactor | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"0c5786890875f2adbcfddd0056dc2b87a768aa1e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0c5786890875f2adbcfddd0056dc2b87a768aa1e"
 [1.6.x] Fixed gis test to run on non gis-enabled settings

 Refs #20998.
 Backport of 973502c0 from master.
 }}}

-- 
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.245d45b413c3b466110db4350851450c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21021: Default geom_type attribute for GeometryWidget should be "Geometry", not "Unknown"

2013-09-02 Thread Django

#21021: Default geom_type attribute for GeometryWidget should be "Geometry", not
"Unknown"
--+
 Reporter:  leplatrem |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  GIS   |Version:  1.6-beta-1
 Severity:  Normal|   Keywords:  minor
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The default value for geom_type is "Unknown" whereas we expect it to be
 "Geometry".

 Indeed, by default we rely on GDAL to set the geom_type attribute, and it
 returns an unexpected value :

 {{{
 >>> from django.contrib.gis import gdal
 >>> str(gdal.OGRGeomType('GEOMETRY'))
 'Unknown'
 }}}

 In fields, we override explicitly his value, so the problem is hidden.
 
https://github.com/django/django/blob/1.6b2/django/contrib/gis/forms/fields.py#L42



 But IMHO the widget should behave nicely with default values, for example
 instantiated like this :

 {{{

 class BigMapWidget(BaseGeometryWidget):
 map_height = 1200


 class GeomForm(forms.Form):

 def __init__(self, *args, **kwargs):
  super(GeomForm, self).__init__(*args, **kwargs)
  self.fields['geom'].widget = BigMapWidget()

 }}}


 Of course, this problem **only** applies to **generic Geometry** field
 types, and those are commonly used.

-- 
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/052.6621196963b21863247a9644cb307c17%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 973502: Fixed gis test to run on non gis-enabled settings

2013-09-02 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 973502c04704aac4742e2d996cb758acd5035d46
  
https://github.com/django/django/commit/973502c04704aac4742e2d996cb758acd5035d46
  Author: Claude Paroz 
  Date:   2013-09-02 (Mon, 02 Sep 2013)

  Changed paths:
M django/contrib/gis/tests/test_geoforms.py

  Log Message:
  ---
  Fixed gis test to run on non gis-enabled settings

Refs #20998.



-- 
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/522481a5b543_6d0267bd5849886%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20998: Form GIS widgets render() lack of modularity

2013-09-02 Thread Django

#20998: Form GIS widgets render() lack of modularity
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  refactor | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"973502c04704aac4742e2d996cb758acd5035d46"]:
 {{{
 #!CommitTicketReference repository=""
 revision="973502c04704aac4742e2d996cb758acd5035d46"
 Fixed gis test to run on non gis-enabled settings

 Refs #20998.
 }}}

-- 
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.8ce67b0f9f4ca88d7265f8ef6d440266%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21019: force_text fails on class object with unicode instance method

2013-09-02 Thread Django

#21019: force_text fails on class object with __unicode__ instance method
+--
 Reporter:  drtyrsa |Owner:  drtyrsa
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  1.5
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  force_text  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by drtyrsa):

 What are valid use cases for `smart_text` then? As I understand it takes
 some object and returns its str (unicode) representation. Why can not this
 object be class itself?

 I am using it to log the args of the function (some args can be models
 classes). Isn't it valid use case?

-- 
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.7b3d47eb2259ff3ed9bb396dafd17d02%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6707: Another implementation for ReverseManyRelatedObjectsDescriptor.set method

2013-09-02 Thread Django

#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
-+-
 Reporter:  favo |Owner:  sfllaw
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by rickvanderzwet):

 * cc: info@… (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/080.fe379276701b28351d023c9b747f5ea8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20998: Form GIS widgets render() lack of modularity

2013-09-02 Thread Django

#20998: Form GIS widgets render() lack of modularity
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  refactor | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"4e3794dd1fbc689dcbcc455f3458539d630a1ff3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="4e3794dd1fbc689dcbcc455f3458539d630a1ff3"
 [1.6.x] Fixed #20998 -- Allow custom (de)serialization for GIS widgets

 Thanks Mathieu Leplatre for the report and the initial patch.
 Backport of 102f26c92 from master.
 }}}

-- 
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.259bb23d30b294607a18ebb42d11ed9a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4e3794: [1.6.x] Fixed #20998 -- Allow custom (de)serializa...

2013-09-02 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 4e3794dd1fbc689dcbcc455f3458539d630a1ff3
  
https://github.com/django/django/commit/4e3794dd1fbc689dcbcc455f3458539d630a1ff3
  Author: Claude Paroz 
  Date:   2013-09-02 (Mon, 02 Sep 2013)

  Changed paths:
M django/contrib/gis/forms/widgets.py
M django/contrib/gis/templates/gis/openlayers.html
M django/contrib/gis/tests/test_geoforms.py
M docs/ref/contrib/gis/forms-api.txt

  Log Message:
  ---
  [1.6.x] Fixed #20998 -- Allow custom (de)serialization for GIS widgets

Thanks Mathieu Leplatre for the report and the initial patch.
Backport of 102f26c92 from master.



-- 
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/52247850d34e2_299779bd5097115%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 102f26: Fixed #20998 -- Allow custom (de)serialization for...

2013-09-02 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 102f26c92923d0e5e80de9b473f2343f76b04aa8
  
https://github.com/django/django/commit/102f26c92923d0e5e80de9b473f2343f76b04aa8
  Author: Claude Paroz 
  Date:   2013-09-02 (Mon, 02 Sep 2013)

  Changed paths:
M django/contrib/gis/forms/widgets.py
M django/contrib/gis/templates/gis/openlayers.html
M django/contrib/gis/tests/test_geoforms.py
M docs/ref/contrib/gis/forms-api.txt

  Log Message:
  ---
  Fixed #20998 -- Allow custom (de)serialization for GIS widgets

Thanks Mathieu Leplatre for the report and the initial patch.



-- 
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/5224774accd8_376adabd58391aa%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20998: Form GIS widgets render() lack of modularity

2013-09-02 Thread Django

#20998: Form GIS widgets render() lack of modularity
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  refactor | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"102f26c92923d0e5e80de9b473f2343f76b04aa8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="102f26c92923d0e5e80de9b473f2343f76b04aa8"
 Fixed #20998 -- Allow custom (de)serialization for GIS widgets

 Thanks Mathieu Leplatre for the report and the initial patch.
 }}}

-- 
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.d98abd8b57ea0a9d29ee9779c9ddd7f7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21019: force_text fails on class object with unicode instance method

2013-09-02 Thread Django

#21019: force_text fails on class object with __unicode__ instance method
+--
 Reporter:  drtyrsa |Owner:  drtyrsa
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  1.5
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  force_text  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by claudep):

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


Comment:

 I think that calling `force_text` on the class itself is not a valid use
 case, unless you can demonstrate the opposite.

-- 
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.fa4f0b05bb1a9dda841f6d161fd5b578%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 429209: Updated the bundled version of six to 1.4.0.

2013-09-02 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4292097078279226cb725c2921011fb14634b9af
  
https://github.com/django/django/commit/4292097078279226cb725c2921011fb14634b9af
  Author: Aymeric Augustin 
  Date:   2013-09-02 (Mon, 02 Sep 2013)

  Changed paths:
M django/utils/six.py

  Log Message:
  ---
  Updated the bundled version of six to 1.4.0.


  Commit: 365c3e8b73eab825a8ecd0cf8046e1a0824ccd45
  
https://github.com/django/django/commit/365c3e8b73eab825a8ecd0cf8046e1a0824ccd45
  Author: Aymeric Augustin 
  Date:   2013-09-02 (Mon, 02 Sep 2013)

  Changed paths:
M django/contrib/auth/management/__init__.py
M django/contrib/auth/tests/test_basic.py
M django/core/mail/message.py
M django/db/backends/mysql/base.py
M django/db/backends/oracle/base.py
M django/db/backends/sqlite3/base.py
M django/db/models/base.py
M django/http/cookie.py
M django/template/loaders/app_directories.py
M django/template/loaders/eggs.py
M django/utils/_os.py
M django/utils/encoding.py
M django/utils/feedgenerator.py
M django/utils/functional.py
M django/utils/http.py
M django/utils/text.py
M docs/topics/python3.txt
M tests/base/models.py
M tests/basic/tests.py
M tests/defaultfilters/tests.py
M tests/httpwrappers/tests.py
M tests/i18n/tests.py
M tests/signing/tests.py
M tests/test_utils/doctest_output.py
M tests/utils_tests/test_datastructures.py
M tests/utils_tests/test_http.py
M tests/utils_tests/test_simplelazyobject.py

  Log Message:
  ---
  Replaced "not PY3" by "PY2", new in six 1.4.0.


  Commit: 868b4c921c3c129085842aafc1857fccdd04f529
  
https://github.com/django/django/commit/868b4c921c3c129085842aafc1857fccdd04f529
  Author: Aymeric Augustin 
  Date:   2013-09-02 (Mon, 02 Sep 2013)

  Changed paths:
M django/contrib/gis/db/models/sql/compiler.py
M django/db/backends/mysql/compiler.py
M django/db/backends/oracle/compiler.py

  Log Message:
  ---
  Used six.moves.zip_longest, new in six 1.4.0.


Compare: https://github.com/django/django/compare/41feab3654ac...868b4c921c3c

-- 
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/5224721c5f5f3_5bad1407d5092336%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21003: BaseGeometryWidget is not idempotent

2013-09-02 Thread Django

#21003: BaseGeometryWidget is not idempotent
-+-
 Reporter:  leplatrem|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  GIS  |  1.6-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by leplatrem):

 Hum, unless I don't get it, it's wrong.

 In your proposition, you assign the database field srid to the data coming
 for the widget, whereas you should be using the widget's srid !

 Something like this :

 ::

 if not data.srid:
 data.srid = self.widget.map_srid


 If you want to see another approach, for example, in django-leaflet, I did
 that to fix that problem:
 https://github.com/makinacorpus/django-
 
leaflet/blob/add_leaflet_form_widget_and_admin/leaflet/templates/leaflet/widget.html#L34
 Which is a consequence of the lack of modularity mentionned in #20998:
 because in this particular case, what is transmitted between the field and
 and the widgets is EWKT !

-- 
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.c8505fdf667564e0c9cf5a26a1624ba7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21020: Allow Migrations to use parent classes migration profile

2013-09-02 Thread Django

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

Comment:

`django.db.migrations` is not just South pulled in. It's actually a
rewrite of the entire concept to make it better.

Fields now require a `deconstruct` method to be used in migrations. As
this is a simple method, it is automatically transferred onto subclasses.
See the release notes for the current skeleton docs:
https://docs.djangoproject.com/en/dev/releases/1.7/#new-method-on-field-
subclasses

--
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.8ab866484dfbb7847f23590d2e51%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21017: code error in v1.5 tutorial 5

2013-09-02 Thread Django

#21017: code error in v1.5 tutorial 5
---+
 Reporter:  rzjint1@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.5
 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 mjtamlyn):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 This seems to also apply to 1.6 and master

-- 
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/076.b8109b05d4c39bde2d2004259141f9e0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21020: Allow Migrations to use parent classes migration profile

2013-09-02 Thread Django

#21020: Allow Migrations to use parent classes migration profile
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I'm unsure as to how Django is implementing South internally, but one
 thing that has always caused me pain is when I need to create myself a
 SubClass of Charfield and suddenly require to redefine all of the south
 migration profile. It would be better to be able to point to your parent
 class for the migration profile.

 Example of desired ability:


 {{{
 class CharField2(CharField):

 .
 .

 class Meta:
 migration = super(CharField, self)._meta.migration
 }}}

-- 
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/052.5e8eea10bb3b8ca915c57862e808f400%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21020: Allow Migrations to use parent classes migration profile

2013-09-02 Thread Django

#21020: Allow Migrations to use parent classes migration profile
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Giggaflop):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
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.4d4c4bce4db4353cdb2d6531fbc448c5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21012: Provide shared "caches" dict to avoid creating multiple cache class instances.

2013-09-02 Thread Django

#21012: Provide shared "caches" dict to avoid creating multiple cache class
instances.
--+
 Reporter:  FunkyBob  |Owner:  FunkyBob
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Cache system)   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 I'm sorry, I haven't followed the entire discussion. Could someone explain
 to me why the cache connections aren't thread-local like the database
 connections? Otherwise this looks like a good idea.

-- 
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.ed9a9a098946d09fbcd6b3ed82808e95%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21019: force_text fails on class object with unicode instance method

2013-09-02 Thread Django

#21019: force_text fails on class object with __unicode__ instance method
+--
 Reporter:  drtyrsa |Owner:  drtyrsa
 Type:  Bug |   Status:  assigned
Component:  Utilities   |  Version:  1.5
 Severity:  Normal  |   Resolution:
 Keywords:  force_text  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by drtyrsa):

 * owner:  nobody => drtyrsa
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 https://code.djangoproject.com/ticket/21019

-- 
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.1d649fc0679e42026db42c1b73e5aadd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21019: force_text fails on class object with unicode instance method

2013-09-02 Thread Django

#21019: force_text fails on class object with __unicode__ instance method
+--
 Reporter:  drtyrsa |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  Version:  1.5
 Severity:  Normal  |   Resolution:
 Keywords:  force_text  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by drtyrsa):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 https://code.djangoproject.com/ticket/21019

-- 
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.b520e5df53dbcc3fd5bb98ba312e478f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21019: force_text fails on class object with unicode instance method

2013-09-02 Thread Django

#21019: force_text fails on class object with __unicode__ instance method
+--
 Reporter:  drtyrsa |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  Version:  1.5
 Severity:  Normal  |   Resolution:
 Keywords:  force_text  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by drtyrsa):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 https://github.com/django/django/pull/1543

-- 
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.704c7d0ec60127e4a3a5d2df1a8133b5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21019: force_text fails on class object with unicode instance method

2013-09-02 Thread Django

#21019: force_text fails on class object with __unicode__ instance method
+--
 Reporter:  drtyrsa |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Utilities   |  Version:  1.5
 Severity:  Normal  |   Resolution:
 Keywords:  force_text  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by drtyrsa):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 https://github.com/django/django/pull/1543

-- 
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.05ef54f1a99c6fed86a8d64f9727da5d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21019: force_text fails on class object with unicode instance method

2013-09-02 Thread Django

#21019: force_text fails on class object with __unicode__ instance method
+
 Reporter:  drtyrsa |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Utilities   |Version:  1.5
 Severity:  Normal  |   Keywords:  force_text
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+
 {{{
 In [10]: class A(object):
 def __unicode__(self):
 pass
:

 In [11]: force_text(A)
 ---
 TypeError Traceback (most recent call
 last)
  in ()
 > 1 force_text(A)

 .../django/utils/encoding.pyc in force_text(s, encoding, strings_only,
 errors)
  97 if not isinstance(s, six.string_types):
  98 if hasattr(s, '__unicode__'):
 ---> 99 s = s.__unicode__()
 100 else:
 101 if six.PY3:

 TypeError: unbound method __unicode__() must be called with A instance as
 first argument (got nothing 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 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/050.5dca4fa608c7835b87772cc554ab0d2c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16502: CreateView useless error message when template_name is not specified

2013-09-02 Thread Django

#16502: CreateView useless error message when template_name is not specified
-+-
 Reporter:  silverghost3@…   |Owner:  krak3n
 Type:  Bug  |   Status:  new
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  CreateView "generic  | Triage Stage:  Accepted
  view"  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by magicharshit):

 Replying to [comment:22 timo]:

-- 
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/080.578d6f8378e641b026802805e4046b08%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20978: Cannot migrate if on_delete=models.SET_NULL

2013-09-02 Thread Django

#20978: Cannot migrate if on_delete=models.SET_NULL
+
 Reporter:  MarkusH |Owner:  loic84
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 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 loic84):

 * owner:   => loic84
 * status:  new => assigned


Comment:

 Updated the PR with a generic solution for closures.

-- 
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.4864e6a7f17ffbbc2004d6e3c316cad0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

49 matches

Mail list logo