Drop support and testing for Django 1.1

Open
#540 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
django, python
Domain
devops, testing

Research direction

Start with test/run lines 232-239 and inspect how the django-ex project is used across the repository and its branches. Determine whether the master branch is still needed; done means obsolete Django 1.1 testing and source are removed or the project is clearly converted into a signpost, with affected tests updated.

Written by the indexing model from the issue text.

Description

In #537, we have removed support for Python 2.7 on EL 7 which means that this test is now useless:

https://github.com/sclorg/s2i-python-container/blob/625f3a614c42202c78d5c8b16cc927a2045b7081/test/run#L232-L239

We can remove it from the sources here but it makes me think about what to do with the django-ex project. If the master branch of django-ex is not used anymore anywhere it might make sense to make it a signpost with links to other branches and remove the obsoleted source code.

What do you think @phracek @pkubatrh @hhorak ?

Dominant language
Shell
Stars
271
Forks
329
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sclorg/s2i-python-container

All issues in sclorg/s2i-python-container

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.