Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
V
Vigenere-API
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Requirements
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
DAVID Axel
Vigenere-API
Commits
6cd397a5
Commit
6cd397a5
authored
2 years ago
by
DAVID Axel
Browse files
Options
Downloads
Patches
Plain Diff
chore:
Remove pre-commit and move requests in linter
parent
77fe524d
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
pyproject.toml
+3
-9
3 additions, 9 deletions
pyproject.toml
with
3 additions
and
9 deletions
pyproject.toml
+
3
−
9
View file @
6cd397a5
...
...
@@ -42,6 +42,9 @@ pylint = "^2"
mypy
=
{
extras
=
[
"reports"
],
version
=
"^1"
}
vulture
=
"^2"
safety
=
"^2.4.0b1"
# Dependencies requests fixed to 2.19 and upper because safety does not fix the required version
# Version lower than 2.19 has a CVE problem
requests
=
"^2.19"
dodgy
=
"^0"
yamllint
=
"^1"
...
...
@@ -56,15 +59,6 @@ pytest-integration = "^0"
pytest-timer
=
"^0"
[tool.poetry.group.dev.dependencies]
pre-commit
=
"^3"
requests
=
"^2.19"
[tool.poetry.scripts]
#serve = "src:start:start"
[tool.poetry.urls]
"Bug Tracker"
=
"https://etulab.univ-amu.fr/d19006523/vigenere-api/issues"
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment