Hello everyone
I'm working on this PR
(https://link.getmailspring.com/link/c4c0c208-5094-4f28-a50b-cad7854e5...@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Fdjango%2Fdjango%2Fpull%2F13559=ZGphbmdvLWRldmVsb3BlcnNAZ29vZ2xlZ3JvdXBzLmNvbQ%3D%3D)
which didn't pass the CI checks (which is
Hey everyone,
I am not sure if this is the best place to put this, so kindly let me know if I
need to shift this somewhere else.
I am working on a patch
Just my 2 cents on this discussion as a junior contributor. I am very fond
of how inclusive and progressive the Django community is.
With that said, I believe that we shall definitely try to stop using the
term blacklist for “bad/unwanted” things. If this change makes even only a
few contributors,
Hey everyone,
I didn’t get selected for GSoC, but I would like to sincerely thank this
community for guiding me and helping me get involved in open source.
Especially, Simon and Carlton for solving my doubts about the ORM.
I hope to improve myself and will definitely try again next year. I still
://gist.github.com/aryan9600/b1c2eaf445006c17e02e7677cf1098d5
Thanks
Kind Regards
Sanskar
On Sun, Mar 29, 2020 at 12:23 PM Sanskar Jaiswal <
jaiswal.sanskar...@gmail.com> wrote:
> Hey Simon,
>
> Thank you for this clarification, I shall make some changes to my proposal
> accordingly.
> Aga
ll be able to easily get access to related db types.
>
> Note that you'll likely need to maintain both a forward and backward
> relation map because for operations alterations of fields referenced by
> foreign keys.
>
> Simon
>
> Le vendredi 27 mars 2020 03:29:11 UTC-4, Sanskar
; D
>
> On Sun, 29 Mar 2020 at 07:58, Sanskar Jaiswal <
> jaiswal.sanskar...@gmail.com> wrote:
>
>> Hey Simon,
>>
>> Could you kindly reply?
>>
>> Thanks
>> Kind regards
>> Sanskar
>>
>> On Fri, 27 Mar 2020 at 12:58, Sanska
Hey Simon,
Could you kindly reply?
Thanks
Kind regards
Sanskar
On Fri, 27 Mar 2020 at 12:58, Sanskar Jaiswal
wrote:
> Hey Simon,
>
> While I certainly see the benefits of this, I still fail to understand how
> this would help ModelState get access to related db_types,
>
> [0]
> https://github.com/django/django/blob/421622548060499881df9966b7a352bce63901cd/django/db/migrations/operations/models.py#L80-L87
> [1]
> https://github.com/django/django/blob/421622548060499881df9966b7a352bce63901cd/django/db/migrations/state.py#L91-L95
>
> Le jeudi 26 mars 2020 16:01:0
of what you have in mind and how things would
> interact together would be appreciated. This is a quite a complex problem
> to solve so a solid initial plan and understanding of the problem will make
> a huge difference down the road.
>
> Cheers,
> Simon
>
> Le mercredi 2
out the Operation.state_forwards logic? I guess it
> would make it easier to test state alterations in isolation but I don't
> think it's necessary for this already large project.
>
> Cheers,
> Simon
>
> Le mercredi 25 mars 2020 06:05:22 UTC-4, Sanskar Jaiswal a écrit :
>>
>
Hey Simon
Just so that I am more clear, is it favourable to move all logic that
ModelOperations and FieldOperations implement right now to ProjectState and
ModelState?
Kind regards
Sanskar
On Tue, 24 Mar 2020 at 04:20, Sanskar Jaiswal
wrote:
> Hey Simon,
>
> Thank you for your
te,
> **other_fields_and_flags) signatures and provide helpers to help
> third-party backends migrate (e.g. a method decorator that renders mode)
> then embedding logic for both paths in the schema editor and adding schema
> specific logic to Operation.database_forwards.
>
> Simon
>
uot;
> models, or at the very least, not "fake" models will not have any custom
> queryset/manager/properties/method you add to it. Can you explain what it
> is you're trying to accomplish?
>
>
> On Monday, March 23, 2020 at 12:59:55 PM UTC-4, Sanskar Jaiswal wrote:
>>
>>
Hey everyone,
Here is my proposal for GSoC. My project is based upon making use of
ModelState during the migrated phase of the project, rather than rendering
fake Models.
https://gist.github.com/aryan9600/b1c2eaf445006c17e02e7677cf1098d5
Feedback and criticism is highly appreciated.
Thanks!
Hey everyone,
I would like to get feedback from the community, on whether providing support
for MongoDB out of the box would be nice idea. I know that Djongo, takes care
of that, but I believe having support in the framework itself, rather than
importing a library, would result in a more
I too am interested in GSoC. I made 2 PRs around 3 days ago, which are
still being reviewed. I am still trying to work on more PRs, but I am
having a hard time choosing a component, as I feel like my proposal should
be centered around the component I am most familiar with. Should I post my
moving on to this? Also
could anyone kindly guide me in the right direction in order to go through
all the necessary things for me to work on 2fa?
Thanking you
Sanskar Jaiswal
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to D
18 matches
Mail list logo
