Avoid packaging scripts folder

Django Internals
1

Spotted during the last release that the do_django_release.sh script needs a fix to work on MacOS.

As I marched off to the Trac wiki to update it, I paused to wonder if we should be managing our essential scripts inside the django repo itself. You get code review, you avoid fiddling with local git excludes, etc.

Many projects I’ve worked on have a /scripts directory (following the Scripts To Rule Them All zen-of-tooling from GitHub Engineering).

We do indeed have /scripts with one lonely script:

$ tree scripts     
scripts
└── manage_translations.py

1 directory, 1 file

… but we package it (which appears to be an artifact of a time when it had a script called rpm-install.sh).

My plan is to:

  • prune scripts from the manifest
  • add do_django_release.sh

Thoughts? Wise? Mad? Meh?

4 Likes
2

After a “security issue” was reported against manage_translations.py, I asked Claude and he agreed that the scripts directory doesn’t need to be included in the release package. However, the directory was still included after I removed graft scripts from MANIFEST.in, so I didn’t make any progress.

2 Likes
3

Both sound sensible to me.