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 are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1-TFYZ7YtyLNwKXyv3F-cru__1666Z6W6k37fGiY03HPA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op18YnQ3Trw7F84Q65HFBrat4aNLL1gpL0MCR5CiN_MStuA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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. -- 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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1-q%2BvSJX%2B57i6rpsHw37kDQ__jdXrw7fCPWg-7dQxfgyQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op18mCH1Gxjt2%2BKmsBjrq1gxE%2BgUUs8NNu_Y9dRG%3Dbij%3DjQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1_5qkcs-44eSM6CxukDnYdq4VmeCYFDvnoFf7EyOTQTxQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1_5sMBNriEKGgRNhKTfsoDFg50nCfio-ZYqgL9d9kLJEg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1-70Sogq3Luf_f-MzgZ9TVT5BwsV9DQjQt-adEu%3DxTGsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1-31f1bimWFsWG9PA8oqu1rRErurkUFnXr6%3D8FyrWfEYg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 want to keep
INSTALLED_APPS, but have a hook for your app to autoconfigure itself when
added maybe something like this:
[django.middleware]
DebugToolbarMiddleware = debug_toolbar.middleware.DebugToolbarMiddleware
Otherwise a freeform callbacks should be more flexible to provision common
stuff apps contribute to such as urls, middlewares, template engines ...
It's true that it doesn't look like you're going to be able to meta program
settings really profoundly, ie. different packages wanting different
defaults, but at least seems it can automate most of the work when
installing an app from the ecosystem into a new django project, that could
at least hook sane defaults, for example django-debug-toolbar's AppConfig
could provision middleware and urlconf and then you would only need to add
debug_toolbar to INSTALLED_APPS.
Does INSTALLED_APPS allow to plugin in a given AppConfig with arguments ?
Ie. in cakephp 3.7 that was just released they don't have a list such as
INSTALLED_APPS, but instead you add apps as such:
# that's all they need to setup the debug toolbar in cakephp
Plugin::load('DebugKit')
# but you could load a plugin without having urls injected as such:
Plugin::load('Cors', ['routes' => false]);
Which would be equivalent to something like:
INSTALLED_APPS.load('debug_toolbar')
INSTALLED_APPS.load('otherapp', urls=False)
It looks like app maintainers really ought to give django-gdaps a shot.
Perhaps Christian, another way would be to contribute gdap support to the
apps you like to use in the ecosystem. Then their maintainers could benefit
from it if they install gdaps and so it can propagate in the ecosystem, and
you can consolidate your patterns.
Best
--
∞
--
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 receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAC6Op1_dMFwwxPwECqc8hk%3DT5HFkcMJjaE3VJ%3Dgo8W_%2B72a5Zg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
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 that both forms work ^^ -- 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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op196pwJs0%2B_uuq4OtLg1E%2B%3D-dPjOUhp7Exk1p-1T5BS7Ww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 in-between the moment settings are parsed and the moment they are loaded into Django ? -- 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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op18yUasg74LVeW9FVQCA%3Dx%2BEnP3KhuDtRh_t8L5UtGkDkg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 into fixing a particular technical issue such as "I want to make an efficient GraphQL server", then even Django works even if it's not necessarily the most fit for X reason. But for "I want to get a web page going with some forms and a database and see where that goes" then Django is definitely enjoyable, and at this point in time where tons of more sophisticated frameworks are born it's clear that Django is still in the game and will be for the next 10 years. So, why not also get more features out of it while we've not been abandoned by all the talented contributors ? It's not because we like Django that we cant haz nice things ;) Great move Andrew and very exciting, keep it up and best luck to you ! -- 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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op19DRYB%2BtUJX-9fG_9EOeo0oqGZayn5SHHBdec9qweq8ng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1-tDvM-raHfOLGCQYFFk7Aoz2CAa%3DY_bXcaj30Y887wzw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 exception that can end up in a 500 error, it would be great if Django could retry so that emails leave when its SMTP is up again, would that maybe weight in priority ? Also, you would probably like to view the queue in the admin, maybe make an unmanaged Model for tasks. So, as simple as Email would look like, I think efforts in it could benefit in a much wider way too. -- 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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op18rkxnz04hVciJs_pHEvmfG2ir_bMafPaYQ7d9HGTJhoQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 > unreliable as the server may die any time. I don't think it's sensible for > Django to try and solve this problem internally, at least not as part of > this async push. > I'm a bit confused here, what benefit are you getting from async emails if you're already retrying emails in the background in production ? Thanks for your kind reply, Have a great day -- ∞ -- 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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op18AA3Q7wguoZn%3D%2BfqHTAquXU0cESxF2i0GYzp%2BjB_ft%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1-1apTUFZq9z5%3DEanpL%2B%2BA9nx9%3D3zS6_C-ZGNtJyBacog%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op19dN2b_PNYgEjqLYa_aawKNWh8BnscrCs-vd7tBQmSpmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
