AI analysis of django.core.mail fail_silently usage in real world projects:
(If you're reading these, I suggest starting with Gemini's.)
Research for https://forum.djangoproject.com/t/deprecating-or-changing-how-django-core-mail-handles-fail-silently/44278
| import functools | |
| import inspect | |
| import warnings | |
| def deprecate_posargs(category): | |
| """ | |
| Function/method decorator to deprecate some or all positional arguments. | |
| The decorated function will map any positional arguments after the `*` | |
| to the corresponding keyword arguments, but issue a deprecation warning. |
| blueprint: | |
| name: Zooz ZEN34 | |
| description: Automations helper for the Zooz ZEN34 S2 Switch using the Zwave | |
| JS integration. | |
| domain: automation | |
| input: | |
| zooz_zen34: | |
| name: Zooz ZEN34 | |
| description: The ZEN34 Switch to interact with. | |
| selector: |
This is an addon for [Dexie][] v3+ that adds a new db.trackedTransaction() method,
using DBCore middleware.
trackedTransaction() is called just like transaction(), but takes an additional
report function that is called with a list of TrackedChange records once the
transaction is ready to commit (but before it actually commits).
See additional docs in the module declaration, and examples in the test file.
| # Monkeypatch botocore.awsrequest.AWSRequest.body to improve performance by caching result. | |
| # Usage: import this file once, at some point before making boto3 requests | |
| # See https://github.com/boto/botocore/issues/1561 | |
| import six | |
| from botocore.awsrequest import AWSRequest | |
| # Monkeypatch AWSRequest.body to improve performance by caching result. | |
| # - AWSRequest.body is accessed multiple times during request signing. |
| # This is an AWS Lambda function to help isolate apparent botocore performance issues | |
| # when posting API requests with large parameters (e.g., SES.SendRawEmail with an 8MB | |
| # RawMessage). See https://github.com/boto/botocore/issues/1561. | |
| # | |
| # Recommended Lambda config: | |
| # Runtime: Python 3.6 | |
| # Handler: lambda_function.run_test | |
| # Environment variables: SES_FROM = "your-validated-ses-sender@example.com" | |
| # (if not set, SES will complain, but the timings should still be valid) | |
| # Memory: 256 MB |
| # *Untested* implementation of a Django email backend that checks | |
| # several ESP status APIs to see which are working, and uses the first | |
| # available one to send. | |
| # | |
| # This caches the ESP API status check results for one hour (by default). | |
| # You can subscribe to webhook notifications on the ESP status pages | |
| # to force status re-checks after ESPs update their status pages. | |
| # | |
| # See https://github.com/anymail/django-anymail/issues/31 for discussion. | |
| # |
| # Detect differences between pytz and dateutil.tz.gettz, | |
| # by comparing the vobject VTIMEZONEs for each. | |
| # | |
| # (Might actually be finding problems in vobject's | |
| # timezone rule detection.) | |
| # | |
| # Requirements:: | |
| # pip install pytz dateutil vobject | |
| import dateutil.tz |
My company, like many, has recently switched away from using Mandrill for our transactional email.
We'd been using Mandrill's [click-tracking][mandrill-click-tracking] feature, and became worried about what would happen to all those old emailed links after we cancel our Mandrill account.
Why should we care about links in emails sent a month or more ago?
| // Preserve and restore window state in localStorage. | |
| // Adapted for Electron from nw.js: | |
| // https://github.com/nwjs/nw.js/wiki/Preserve-window-state-between-sessions | |
| // | |
| // As written, it only handles a single-window app. | |
| // | |
| // This code is meant to run in the renderer process. | |
| // To use, load from index.html (or whatever file you loadUrl into your BrowserWindow): | |
| // <script src="winstate.js"></script> |