viper-framework/viper

Upgrading dependencies

Open

#709 opened on Oct 14, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (1,527 stars) (372 forks)batch import
help wanted

Description

Some of our dependencies are very much out of date. While I started upgrading those that are more critical, would be good to test whether there is the opportunity to upgrade most.

cc @Rafiot

Contributor guide

Tech stack
python
Domain
devops
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Python programming basicsDependency management concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue suggests upgrading outdated dependencies in the viper repository. First, identify all outdated dependencies by reviewing requirements.txt or similar files. Then, test each upgrade individually to ensure no breakage, and update the dependency files. Since the issue is vague, it may be necessary to open a discussion to clarify the scope and prioritize which dependencies to upgrade.