question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Review requirements

See original GitHub issue

Conan has been including dependencies from time to time in new releases. Version 0.22.2 has the following list of requirements:

PyJWT>=1.4.0, <1.5.0
requests>=2.7.0, <2.14.0
colorama>=0.3.3, <0.4.0
PyYAML>=3.11, <3.13.0
patch==1.16
fasteners>=0.14.1
six>=1.10.0
node-semver==0.1.1
distro>=1.0.2, <1.1.0
pylint==1.6.5
future==0.16.0

PyJWT has a new release, 1.5.0. Is 1.5.0 supported? Why PyJWT requirement was specific about major version, and why fastners not? Why patch, node-semver, pylint and future are so specific about the supported version?

Distros like Slackware and Arch Linux are creating packages of conan requirements.

https://slackbuilds.org/repository/14.2/development/conan/?search=conan
https://aur.archlinux.org/packages/conan/

These requirements can also be a dependence of other distro packages. So, It is very important to maintain the requirements updated and track compatibility. For example, currently pylint version in Slackware database is 1.5.2 https://slackbuilds.org/repository/14.2/development/pylint/. Is this version supported? About a newer pylint, version 1.7.1?

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
lasotecommented, May 31, 2017

Thanks @tivek, feel free to open a PR with the changes that you consider reasonable, you can comment on it the reasons for each case. I’m sure we can relax/update/downgrade some requirements without any problem.

0reactions
lasotecommented, Jul 4, 2017

Hi all,

I’ve been reviewing why node-semver, six, patch and others are fixed versions, and they are actually the latest published version (no more versions have been published).

For the PyJWT and the requests, we have relaxed the constrictions, if ANY upgrade is needed please report in a new issue and we will be glad of review/update them.

It feels arbitrary to relax the dependencies that are pretty stalled on pypi.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Conduct a Requirements Review - Bridging the Gap
A requirements review or walk-through is a meeting where you gather all of your stakeholders together and walk-through the requirements documentation, ...
Read more >
What is a Requirements Review: Definition, Process & Tools
A requirements review is a manual process that involves people from both client and contractor organizations. They check the requirements document for anomalies ......
Read more >
Mastering the Requirements Review Process - QRA Corp
A requirements review is a structured process where anyone from key stakeholders to user groups and the project team walk through the requirements...
Read more >
Requirements reviews
A requirements review is a manual process that involves people from both client and contractor organisations. They check the requirements document for ...
Read more >
How to Conduct a Requirements Review for Business Analysis
A requirements review is a structured audit within the business analysis process where participants ask questions, make suggestions, and improve ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found