Disqus - Latest Comments for lincolnloop

Re: Django Logging, The Right Way

Peter Baumgartner — Fri, 12 Mar 2021 15:57:46 -0000

Logging config applies to all submodules, so if you have a project, `myproject` and setup logging for it, any module underneath it will be logged using that configuration. If your apps are not in the same namespace as your project, you'll need to duplicate the `myproject` logger for each app module name.

Re: Single-file Python/Django Deployments

Peter Baumgartner — Mon, 01 Jun 2020 10:07:49 -0000

You're probably hitting the "System Dependencies" caveat. My guess is that you need to install the openldap client library on the target system.

Re: Disabling Error Emails in Django

Peter Baumgartner — Thu, 17 Oct 2019 10:38:19 -0000

As long as you are not using `mail_admins` https://docs.djangoproject.... that should be a viable option too.

Re: Django Logging, The Right Way

Peter Baumgartner — Wed, 04 Sep 2019 15:37:50 -0000

Give this a try, https://gist.github.com/ipm...

Re: Django Logging, The Right Way

Peter Baumgartner — Wed, 04 Sep 2019 13:10:12 -0000

Uncaught exceptions should go to stderr by default. See https://docs.python.org/3/l...

I would double check that they are in-fact uncaught and there isn't something catching them somewhere in the stack. Django's templates have some scenarios where they intentionally catch exceptions (see `silent_variable_failure`).

Re: Django Logging, The Right Way

Peter Baumgartner — Wed, 12 Jun 2019 10:20:28 -0000

Yes

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Mon, 04 Mar 2019 10:41:26 -0000

Different ways to handle this, but if you really want a "true" package, you should run things like collectstatic and compilemessages during the build process. You could then create the package for distribution (deployment).

If you don't have a build pipeline in place or don't want to jump through those hoops, you could just run any necessary commands after installing your package.

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Tue, 28 Aug 2018 17:45:27 -0000

Chances are that you're depending on a feature of Python that inserts the current directory onto the Python path. That is a fragile dependency and one that is likely to burn you at some point in deployment.

Re: Django Logging, The Right Way

Peter Baumgartner — Tue, 21 Aug 2018 10:09:22 -0000

Typically it is combined with a command like tail to only run on a subset of the log file. If running grep took fifteen minutes, I'd consider rotating the logs more often.

Re: Serving Static Files with uWSGI

Peter Baumgartner — Tue, 29 May 2018 13:21:13 -0000

According to their docs, it is. http://uwsgi-docs.readthedo...

Re: Goodbye manage.py

Peter Baumgartner — Mon, 14 May 2018 09:40:33 -0000

Hmm, it should be calling the exact same function. The file that gets placed in bin is just a thin wrapper that calls into your code. Maybe you could put some breakpoints in your code to figure out what is going on. Could be that it is looking for .env in the wrong directory?

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Mon, 14 May 2018 09:37:45 -0000

Yep, if your dependencies are declared in setup.py as well, pip install -e . is all you need. If you are using a requirements file, you can do it in one shot, pip install -e . -r requirements.txt.

Re: Goodbye manage.py

Peter Baumgartner — Fri, 20 Apr 2018 14:07:13 -0000

Hi Shige! 👋
Typically we have a couple settings files (local dev and deployment) and are symlinking them to a common place when the environment is setup. We set DJANGO_SETTINGS_MODULE to point to that.

Lately I've been playing around with the idea of flat configuration files instead of multiple settings files. The jury is still out on that though 🙂https://pypi.org/project/go...

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Thu, 19 Apr 2018 12:56:24 -0000

Here you go! https://lincolnloop.com/blo...

Re: Django Anti-Patterns: Signals

Peter Baumgartner — Mon, 02 Apr 2018 10:22:40 -0000

From the docs:

Note, however, that like Model.full_clean(), a model’s clean() method is not invoked when you call your model’s save() method.

You need to remember to call the validation code manually if you aren't using a ModelForm.

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Thu, 08 Feb 2018 14:51:23 -0000

TIL... thanks!

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Mon, 05 Feb 2018 10:05:20 -0000

If you search the django-users mailing list, you'll find some evidence that users don't like this pattern. I think since Django doesn't create one by default, people assume they shouldn't use one.

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Fri, 02 Feb 2018 12:12:28 -0000

We actually remove the manage.py file and put the function in myproject/__init__.py then use the same technique as you are using. It felt a little off-topic for this post, but watch for more details in a future post.

Re: Using setup.py in Your (Django) Project

Peter Baumgartner — Fri, 02 Feb 2018 10:36:56 -0000

Yes! Building wheels once and distributing them is a great option. I think that can be done in conjunction with pipenv's superior lock file for internal projects for a best-of-both worlds approach. That being said, I agree, having it all supported in one place would be nice.

Re: Django Logging, The Right Way

Peter Baumgartner — Tue, 09 Jan 2018 13:43:55 -0000

Fixed!

Re: Disabling Error Emails in Django

Peter Baumgartner — Wed, 03 Jan 2018 18:33:31 -0000

Good question! I just tried "Option 2" from the post (setting a "mail_admins" handler to logging.NullHandler), but it gets overwritten when Django applies it's default logging. That leaves you back with options 3 or 4.

Re: Django Logging, The Right Way

Peter Baumgartner — Fri, 22 Dec 2017 09:41:40 -0000

Make sure you've followed their Setup instructions and that `manage.py raven test` works.

Re: Django Patterns: Fat Models and `cached_property`

Peter Baumgartner — Wed, 23 Aug 2017 10:22:35 -0000

Here's an example directly from Django, https://github.com/django/d...

Re: Django Patterns: Fat Models and `cached_property`

Peter Baumgartner — Fri, 18 Aug 2017 09:48:03 -0000

You are correct. In the typical Django project a model instance's lifetime is typically the same as a request's lifetime. I can't think of many instances where you would want to instantiate a model at startup and have it persist for the duration of your WSGI process. In that scenario, it's basically static data and, perhaps not data well suited for a Django model.

Re: Django Anti-Patterns: Signals

Peter Baumgartner — Thu, 20 Jul 2017 18:59:32 -0000

This is exactly the same as signals. A failing pre_save signal will prevent committing to the DB. A failing post_save happens after committing to the DB. Without signals it just depends if your code executes before or after the super call.

In general, introducing bugs into your programs is going to cause problems. If you have code that is expected to fail, that's what try/except is for. Using async processes to hide bugs in the code isn't a pattern I'd recommend.