Extracting common functionality in Django management commands

Question

What is the generally accepted way for isolating functionality that is shared between multiple management commands in a given app? For example, I have some payload building code that is used across multiple management commands that access a third-party API. Is the proper location app_name/manangement/helpers.py which would then be imported in a management command with from ..helpers import build_api_payload?

I don't want to put it at the root of the app (we typically use app_name/helpers.py for shared functionality), since it pulls in dev dependencies that wouldn't exist in production, and is never really used outside the management command anyways.

Chris · Accepted Answer · 2016-02-18 22:27:02Z

1

I went with app_name/manangement/helpers.py. No issues.

answered Feb 18, 2016 at 22:27

Chris

3414 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Extracting common functionality in Django management commands

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related