ambitioninc / ambitioninc/django-dynamic-initial-data
What part of the code is Postgres specific?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
I had a brief look but couldn't see what made this a postgres only app (apart from setup.py of course!)
Incidentally - putting psycopg in install_requires is redundant at best. If this app is postgres specific then any project using it will already have that as a requirement. I've had problems with a similar issue - apps that put Django itself in install_requires.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with setup.py and its install_requires entry for psycopg, then inspect the Django application code for PostgreSQL-specific behavior. A useful outcome would be a clear account of any PostgreSQL requirement and an agreed treatment of the redundant dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, postgresql, python
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100