Opened 16 years ago
Closed 16 years ago
#10173 closed (wontfix)
Add a setting to set up pg binaries for test_runner
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | GIS | Version: | 1.0 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Context: postgres/postgis.
For gis testing, when test database is created, pg commands are executed:
- createlang (options) plpgsql
- psql (options) -f <postgis files>
It would be great if both pg binary pathes could be set in settings, for example:
POSTGRES_PSQL_PATH = '/path/to/psql' POSTGRES_CREATELANG_PATH = '/path/to/createlang'
Attachments (1)
Change History (3)
by , 16 years ago
Attachment: | django_pg_bin_test_runner.diff added |
---|
comment:1 by , 16 years ago
Can't this be solved externally to Django by setting the PATH
envvar?. It seems to me that if Django should incorporate one additional setting to store the full path for every external command executed by a helper script we will end with a huge number of such settings.
comment:2 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Yeah, this is becoming settings overload. It's a sysadmin issue: making sure the right binaries can be found.
if these binaries really are all over the place on different distros, or not on standard paths normally, then the more traditional solution would be an environment variable to declare which binary should be run. That can then be set in the users environment. Wontfixing the current approach. Seems a bit too specialised and not really the right approach.
Patch for described changes