That's what we've done in Django 1.7 for Form/ModelForm (#19617, #8620), and I
completely agree that it should be possible to shadow fields from abstract
models. The docs even suggest that this may be possible in the future; quoting
the relevant section: "this [shadowing] is not permitted for at
Hi,
I also think so, that overriding a field should not need any special protection.
But how would you deal with inherited managers on the class that might refer to
some overridden field that has changed?
--
You received this message because you are subscribed to the Google Groups
"Django dev
OK, since ticket was market as accepted, should *all* aggregates functions
from http://www.postgresql.org/docs/9.4/static/functions-aggregate.html be
implemented ? I'm asking to prevent doing unnecessary work.
воскресенье, 8 февраля 2015 г., 1:11:08 UTC+2 пользователь Andriy
Sokolovskiy (coldm
Please use this mailing list to communicate your ideas and questions
regarding GSoC.
As I wrote in another thread, "Your odds of acceptance are greatly enhanced
if you have a track record of producing good patches (and it will also help
you write a better proposal, I think)."
On Saturday, Febr
I opened a ticket for it.
https://code.djangoproject.com/ticket/24301
суббота, 7 февраля 2015 г., 18:51:34 UTC+2 пользователь Michael Manfre
написал:
>
> It's reasonable to support backend specific aggregate functions. The
> database backend API contains
> BaseDatabaseOperations.check_expressio
A good place to start is reading the contributing documentation:
https://docs.djangoproject.com/en/dev/internals/contributing/
The next step is to find a ticket in the area you are interested in and
then either:
1) review the existing patch if there is one,
2) improve an existing patch if it has
Hi,
I am an GSOC - 2015 Applicant. I am currently in my 3rd year B.Tech
(Computer Science). I want to contribute to Django. It would be really
helpful, if you could help me get started.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contribut
On 7 févr. 2015, at 15:09, Fabio Caritas Barrionuevo da Luz
wrote:
> Parallel is different than concurrent
Of course. I’m concerned with parallelism here because that’s what gives the
performance improvement. Of course I have to make concurrency safe.
> did you come to look at the package "te
It's reasonable to support backend specific aggregate functions. The
database backend API contains
BaseDatabaseOperations.check_expression_support for this exact reason. Feel
free to create the ticket.
Regards,
Michael Manfre
On Sat, Feb 7, 2015 at 9:00 AM, Andriy Sokolovskiy (coldmind) <
sokand.
>
> Hello Russell,
>
Thankyou for your response. I will try to fix a few easy bugs first
as you suggested and then go for adding bulk_update or improving
bulk_create.
I am interested in doing a gsoc project under this organization
if given the opportunity. I would like to st
Parallel is different than concurrent, did you come to look at the package
"testtools", I think it implements something similar to what you want to do
https://github.com/testing-cabal/testtools/blob/master/testtools/testsuite.py#L38-L198
http://stackoverflow.com/a/17059844/2975300
Em sexta-fei
So, since django has contrib.postgres, maybe it would be reasonable to add
postgres-specific aggregate functions to this module?
If it is good idea, I'm gonna create ticket and implement this.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Cont
On 7 févr. 2015, at 01:02, Russell Keith-Magee wrote:
> I've thought about (but never done anything) about this problem in the past -
> my thought for this problem was to use multiple test databases, so you have
> isolation. Yes this means you need to do more manual setup (createdb
> test_data
13 matches
Mail list logo
