Re: status of 1.8 release blockers

[Raúl Cumplido]

\o/

On Wed, Feb 25, 2015 at 1:08 AM, Tim Graham  wrote:

> Zero blockers as of this writing. If we survive the next 12 hours with no
> new ones, I'll release the beta around then (famous last words).
>
>
> On Monday, February 23, 2015 at 7:29:09 PM UTC-5, Tim Graham wrote:
>>
>> Previous two issues have been fixed, and now we have two new issues:
>>
>> #24391  UUIDField with
>> default=uuid4 triggers validation on otherwise empty inline formsets
>> 
>>
>> #24395  Cannot reference FK
>> relation from inline ModelForm.save()
>> 
>>
>> There is a chance to resolve them both tomorrow and then release the beta.
>>
>> On Saturday, February 21, 2015 at 3:53:51 PM UTC-5, Tim Graham wrote:
>>>
>>> Patches for the two remaining blockers are awaiting review.
>>>
>>> #24381  Cache pickling
>>> exception in 1.8a1 with cross-table filter params
>>> 
>>> #24377  UUIDField as
>>> primary key breaks inline admins
>>> 
>>>
>>> On Friday, February 20, 2015 at 4:48:01 PM UTC-5, Tim Graham wrote:

 The three issues from last time are resolved, but there is a new issue
 I've been working on today. I have a tentative fix, but there is a failing
 test. Assuming nothing else comes up, I might consider releasing the beta
 tomorrow even if I can't solve that by then as it's not really a new issue,
 just magnified by the fact that UUIDField is in core and that it's
 implementation as a primary_key requires default=uuid.uuid4 unlike some
 existing third-party implementations.

 #24377  UUIDField as
 primary key breaks inline admins
 

 On Thursday, February 19, 2015 at 2:45:07 AM UTC-5, Loïc Bistuer wrote:
>
> From my point of view #24351 is ready for a final sanity check and
> merging.
>
> --
> Loïc
>
> > On Feb 19, 2015, at 10:10, Tim Graham  wrote:
> >
> > 3 issues remain. I haven't confirmed with the owners, but it seems
> to me there may be a good chance to wrap them up tomorrow.
> >
> >
> > #24351  RunPython/RunSQL operations in contrib migrations
> and multi-db routers.
> > Owner: Loic
> > Status: In review.
> >
> >
> > #24328 The new Options._get_fields() method needs to be cleaned up
> > Owner: Anssi
> > Status: In review.
> >
> > #24343 UUID foreign key accessor returns inconsistent type
> >
> > Owner: Marc
> > Status: Marc to polish patch.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django developers (Contributions to Django itself)" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send an email to django-develop...@googlegroups.com.
> > To post to this group, send email to django-d...@googlegroups.com.
> > Visit this group at http://groups.google.com/group/django-developers.
>
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/
> 170625d3-1bb5-4b9d-ab74-501fd5dea86b%40googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/7d933ca2-ed55-408b-bdce-551060e24d54%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 

Re: CSRF REASON_NO_REFERER with meta referrer tags

[Raúl Cumplido]

facepalm... Just read that on the contributing guidelines, didn't know that
won't fix bugs where never reopened. So I closed it as won't fix. If the
conversation keeps going I suppose a new bug will be opened.

On Tue, Feb 3, 2015 at 8:56 AM, James Bennett  wrote:

> Please keep discussion going in this mailing-list thread, and keep in mind
> Django's policies regarding re-opening a "wontfix" ticket (which are
> essentially: don't do it).
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAL13Cg-rdh_-N9uhp4oZGZY3GKjHL_xxvEsAFDo3hQjBOmZHUQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD1RbrqPbMY0DwwkjFvOySGuidkMinxSmr75P9aCsRPS7kavpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: CSRF REASON_NO_REFERER with meta referrer tags

[Raúl Cumplido]

Hi Jon,

I've reopened the bug so we have a new discussion. I think the things have
changed slightly in the last two years.

Thanks,
Raul

On Tue, Feb 3, 2015 at 2:29 AM, Karen Tracey  wrote:

> This has bee brought up before, see:
> https://code.djangoproject.com/ticket/16870
>
> I am not aware of any change in this area that would affect the decision
> made in that ticket.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CACS9rafr6f01-9c7vBNprnz1CTJGgOUyZvfSbOw_da0b_4i4%2BQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD1RbrpTAvR_EXmPHkz-vq7JjJGCDJySW7ogrnsvzmi%2BhNS31Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Error message not clear

[Raúl Cumplido]

Hi,

Maybe it's a stupid issue but I think the error message is not clear or I am
missing something about the dummy db.backend. Why if you set an error
database backend the error message is the next one?
Try using django.db.backends.XXX, where XXX is one of:
'dummy', 'mysql', 'oracle', 'postgresql', 'postgresql_psycopg2',
'sqlite3'

If a user sets the dummy one it will get stucked with messages like this
(and will ask help on the django-users list :P):
Error: Django doesn't know which syntax to use for your SQL statements,
because you haven't specified the ENGINE setting for the database.
Edit your settings file and change DATBASES['default']['ENGINE'] to
something like
'django.db.backends.postgresql' or 'django.db.backends.mysql'.

Shouldn't the first error just tell you:
Try using django.db.backends.XXX, where XXX is one of:
'mysql', 'oracle', 'postgresql', 'postgresql_psycopg2', 'sqlite3'

(not dummy)

Just because users (new ones) can expect that the dummy backend is a correct
one. And as I've been looking onto the code it's just used when no backend
is setted. Just to don't give people an incorrect message.

Thanks,

-- 
Raúl Cumplido

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.