Re: Experimental APIs DEP

On 12/06/2014 07:24 PM, Andrew Godwin wrote: > My notes from the meeting say "experimental API language", so I may have > taken an adjective too literally when I made this. > > Nevertheless, the key thing _I_ want to see is for us to commit to > putting release notes out for some of Django's APIs

Re: Experimental APIs DEP

My notes from the meeting say "experimental API language", so I may have taken an adjective too literally when I made this. Nevertheless, the key thing _I_ want to see is for us to commit to putting release notes out for some of Django's APIs that aren't necessarily considered stable. The 1.7 data

Re: Experimental APIs DEP

On 6 déc. 2014, at 10:05, Carl Meyer wrote: > As the DEP notes, our backwards-compatibility policy already includes a > longstanding carve-out for anything documented within the "internals" > section of the docs. We haven't made much use of this for documenting > actual internal APIs (most of tha

Fellow Report - December 5, 2014

The release for 1.7.2 didn't happen this week as I had hoped. The team is still sorting out how to add new releasers. Maybe next week. Report for week ending December 5, 2014: Triaged --- https://code.djangoproject.com/ticket/2394 - fastcgi with fork method got db error (won’t fix) ht

Re: uuid field short websafe representation

A non-standard, compressed unique value is not a UUID. Also, this forces database backends to store the value in a string datatype and doesn't allow taking advantage of uuid specific datatypes. E.g. Postgresql couldn't use its uuid datatype. Any data can be made safe for any specific usage, e.g. UR

uuid field short websafe representation

Hi, I am glad to see the UUID field coming to 1.8 Bellow is how we do it now in 1.7. The advantages: - it only uses 21 chars (instead of 32) - chars are safe for URLs - uuid is created when default is called I advocate to have the short websafe representation. What do you think? code: >

Re: Django 1.7 migrations don't respect db_table in M2M relation

Please use Django's ticket tracker to report bugs in Django: https://code.djangoproject.com/newticket Thanks! On Saturday, December 6, 2014 8:10:42 AM UTC-5, lza...@ucs.br wrote: > > > Hi, > > If is defined "db_table" in Meta class of a model, that you are using by > through, the migrations cre

Ordering of fields in subclasses of a form

Hi, I've submitted a pull request https://github.com/django/django/pull/3652 for the often requested feature "Easy way to customize ordering of fields on forms that use inheritance". I'd appreciate some feedback https://code.djangoproject.com/ticket/5986#comment:32 cheers, -- You received this me

Django 1.7 migrations don't respect db_table in M2M relation

Hi, If is defined "db_table" in Meta class of a model, that you are using by through, the migrations create the table with original name, dosen't respect the db_table attribute defined on through model. Instead of create table name "myapp_mychoicename" it create "myapp_test_company_related".

Re: Experimental APIs DEP

Hi Andrew, Thanks for putting together this proposal. On 12/05/2014 09:32 PM, Andrew Godwin wrote: > One of the results of discussions at Django Under The Hood was support > for the idea of marking APIs "experimental" - that is, document them and > include them in mainline Django releases, but aw