Hi, I am a computer engineering undergraduate with great skills in Java
and basic skills in Python and JavaScript and I am a beginner to the open
source world, I'd like to contribute to this project to get comfortable
with Python as well as the open source world. I am going through the
contrib
>
> Understand when I say that what you are proposing is a very, very big
> change. Django's ORM is heavily coupled to runtime information and the app
> layer, and I tried for many years to decouple them and ran into all sorts
> of issues as a result. Importing the fields from the source code
>
>
>
> The advantages comes from db type independency, this is true, but in the
> other side you're including the app layer dependency.
>
> Let's imagine that one of builtin field will change it's definition.
> Running migrations on two different Django versions will produce two
> different output
>
>
> Some of these are problems, yes, but you have to understand they are
> tradeoffs and the alternative is, in my opinion, worse.
>
>
Yes, I understand. But maybe there is another / better alternative.
Let's simplify a little and talk about a python deps first.
> > I believe that there exis
Hi Marcin,
Some of these are problems, yes, but you have to understand they are
tradeoffs and the alternative is, in my opinion, worse.
> I believe that there exist some solution, which drops app layer
dependency ands allow using custom fields
I would love to see what this would be. I spent a de
IMHO I think it's more consistent with the definition of certain filters
make the system somehow "lazy" and only evaluate filter variables only when
are used.
El jueves, 22 de junio de 2017, 12:15:53 (UTC-3), Tim Graham escribió:
>
> My question is why is it problematic to put "notreal/notreal2"
Hi.
At the begining please forgive my engilsh - i'm not a native speaker.
I wrote here and in other places my thoughts about db migrations few times,
and probably Tim remembers me so well.
My opinion was not changed, but I realized that I cannot leave Django
ecosystem for a long time.
In that c
Raising this across in aio-libs for a bit of exploratory
discussion... https://groups.google.com/forum/#!topic/aio-libs/7rJ8Pb1y7aA
> I'm not sure where I sit on it - on one hand <...> on the other hand <...>
Same really, yes. :)
--
You received this message because you are subscribed to the G
>
>
> > If we end up with one format for channel names and messages that is
> spread across two consumption forms (in-process async and cross-process
> channel layers), I think that would still be a useful enough standard and
> make a lot more people happy.
>
> Yes. I'm not sure if there aren't al
