Hey Simon,
Thank you for your feedback! It helps a lot. I shall look into your doubts
right now, and edit my proposal accordingly.
Kind regards
Sanskar
On Tue, Mar 24, 2020 at 3:37 AM charettes wrote:
> Hello Sanskar,
>
> Thank you for your submission, from a quick look it seems to be heading
Understood. Thanks.
On Monday, March 23, 2020 at 5:48:43 PM UTC-4, charettes wrote:
>
> Javier
>
> > I don't see how this solves anything. At the end of the day these "real"
> models, or at the very least, not "fake" models will not have any custom
> queryset/manager/properties/
> method you add
Hello Sanskar,
Thank you for your submission, from a quick look it seems to be heading in
the right direction.
Would it be possible to break the large overview section into more granular
sections where you describe how you roughly plan to tackle each of the
point mention?
I personally have do
Hey Javier!
So currently, during migrations, specifically during the state_forwards and
database_forwards methods, Django renders a fake model and passes it down
to the SchemEditor which is an expensive operation and slows down the
process. The idea is to use ModelStates instead of Models, as thei
Javier
> I don't see how this solves anything. At the end of the day these "real"
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?
I don't think that's the goal of
So in the end, i have to manually close the database connection after my
threads in my threadpool are done executing, even though, django created
them automatically when the threads were first created? This is just plain
bad design.
On Tuesday, June 21, 2016 at 6:04:11 PM UTC+5:30, Aymeric Augu
Hi,
Thank you for sharing that.
I see what you mean. I can definitely benefit from this during the
implementation phase, that is, if I’m given the opportunity to work on this.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributi
I don't see how this solves anything. At the end of the day these "real"
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 UT
Week ending March 22, 2020.
*Triaged:*
https://code.djangoproject.com/ticket/31366 - GEOSGeometry fails on
instance with GEOJson and srid not 4326. (invalid)
https://code.djangoproject.com/ticket/31367 - ImportError error while
importing class from auth/mixin to auth/view. (wontfix)
https://code
Django's parallel test runner works through forking processes, making it
incompatible on Windows by default and incompatible in macOS due to a
recent update. Windows and macOS both support spawn and have it enabled by
default. Databases are cloned for each worker.
To switch from fork to spawn,
You might find https://github.com/lincolnloop/goodconf interesting. I
see some overlap there with what you're doing.
On Mon, Mar 23, 2020 at 9:43 AM Abhirav Dilip Kariya
wrote:
>
> Hi,
>
> Thank your for the suggestion.
>
> I did look at some libraries. However, the libraries I looked into (or
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!
Kin
Hi,
Thank your for the suggestion.
I did look at some libraries. However, the libraries I looked into (or rather,
was able to find) only dealt with single type of secrets store. Like
django-environ only deals with .env files.
Please let me know if you have any libraries in mind.
Thanks
--
I’m not sure if you did this already, but I would also look at how existing
third-party libraries are handling this.
--
Caio
> On Mar 21, 2020, at 02:01, Abhirav Dilip Kariya wrote:
>
> Hello everyone,
>
> I’ve submitted my proposal draft for GSoC for the 'Secrets Manager' idea
> listed
Hi Ahmad,
> On 23 Mar 2020, at 13:23, Ahmad A. Hussein wrote:
>
> I completely agree with what has already been said by everyone here;
> moreover, this is a battery missing from Django in my opinion. It would make
> Django more "batteries-included" if this was part of core rather than third
>
i assign it to me
https://code.djangoproject.com/ticket/18468
i will close this pullRequest caused by imperfection
https://github.com/django/django/pull/12605
I will bring a new PullRequest as soon as possible.
in at least a week
--
You received this message because you are subscribed to
I completely agree with what has already been said by everyone here;
moreover, this is a battery missing from Django in my opinion. It would
make Django more "batteries-included" if this was part of core rather than
third party-libraries. If you need help with documentation, I can
definitely th
17 matches
Mail list logo
