Re: Django ORM Internals

Hi Mahdi, I would suggest reading the code and test code in the tests/ directory for the ORM. There might also be some videos from Django Under The Hood conferences, found some here: https://www.google.com/search?q=Django+Under+The+Hood+orm&tbm=vid Best -- You received this message because yo

Re: Django Async DEP

Nevermind my question you will get a lot more out of the workers, that Django 3.0 is going to be really blazing fast like channels that calls for a celebration xD -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" gr

Re: Django Async DEP

Hi Andrew, On Thu, May 9, 2019 at 10:04 PM Andrew Godwin wrote: > > If you want guaranteed email delivery, that's a task for something like > Celery or a third-party API; any method of sending emails in the background > in the same process, be it threads or async coroutines, is going to be > unr

Re: Django Async DEP

In one project I really enjoyed using channels just as a background worker instead of celery, and the DEP does not talk much in the Email section: use the async variant, can be tackled separately, low priority. For now the ORM works, but if sending an email fails (ie. SMTP down) it will raise an e

Re: Django Async DEP

Oops too fast, if it's possible to split the DEP and delay the ORM as advised by Patrick it could make it a lot easier to distribute the work, I don't know really sry. Have a great day ! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributio

Re: Django Async DEP

Hi Patryk, I'm not sure but for me the "What is Django" section answers the question. For me Django is full of philosophy that seeds a great ecosystem of apps of all sorts with a growing user base nonetheless, and a bunch of brilliant hackers to look up to and inspire for more. Of course if you're

Re: injecting settings

Maybe you would want to install an app without having their urls injected then you're going to need to do things like INSTALLED_APPS = [ someapp.AppConfig(urls=False) ] Of course this is going to make complicate the settings system, but why not hook a callback in AppConfig that is executed i

Re: injecting settings

In the example Config.ready() calls for a dict update() which will probably work for a while, before changing the update() call in the example with more elaborated code. System checks shoud catch cases where configuration is invalid at all. Not sure how much you can pull from entry points, if you

Re: injecting settings

ERRATA in the code above, a mistake I make really often, instead of: DebugToolbarMiddleware = debug_toolbar.middleware.DebugToolbarMiddleware Should be: DebugToolbarMiddleware = debug_toolbar.middleware:DebugToolbarMiddleware In one python module I rely on this (cli2), I ended just making so th

Re: injecting settings

Great idea Christian, actually some frameworks have this kind of feature, such as CakePHP, in which apps can also inject urls and middlewares for example. This would be a huge step forward for the ecosystem (and when apps can share node modules you're done haha !). -- You received this message b

Re: Deferring "Sign the CLA"

Just found Python's CLA page that offers a smooth experience with Adobe Sign. https://www.python.org/psf/contrib/contrib-form/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group

Re: Deferring "Sign the CLA"

On Wed, May 1, 2019 at 2:56 PM Florian Apolloner wrote: > Redhat had lawyers go over that… > If you want I can ask YourLabs lawyer, he's an ASF contributor and is the expert on that matter in my little country. Let me know -- ∞ -- You received this message because you are subscribed to the

Re: Proposal to format Django using black

Also note that even for people that don't use an IDE, they might like when GitHub's blame feature work, so that would also be a pro for rewriting the git history rather than creating a new commit for the code rewrite. -- You received this message because you are subscribed to the Google Groups "

Re: Proposal to format Django using black

If you don't want to break git blame then I suppose you could create a branch to replay each commit with black. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiv

Re: Deferring "Sign the CLA"

Also signing the GPG signed CLA to the cla@ email might be less hassle for the board to receive and for most of current contributors to do, for example i couldn't sign in docusign for a few months without apparent reason using a gmail account, but maybe I'm the only person that was affected by that

Re: Deferring "Sign the CLA"

Maybe accept gpg signatures for the cla document in a repo users make pull request too from now on and it's done. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop rece

Re: Deferring "Sign the CLA"

Hi Carlton, Just wondering what's your plan ? combining peopledoc/django-docusign to automate CLA signing process with a gitub bot or something ? Looking forward to learn moar about it, I'm sure Djangonauts holds a fair lot of dematirializators. Best -- You received this message because you ar