Skip to content

Project dependencies may have API risk issues #1

@PyDR-Tool

Description

@PyDR-Tool

Hi, In milaan9, inappropriate dependency versioning constraints can cause risks.

Below are the dependencies and version constraints that the project is using

python-graphql-client==0.3.0
httpx
feedparser
GitPython
sqlite-utils

The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict.
The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.

After further analysis, in this project,
The version constraint of dependency feedparser can be changed to >=6.0.0b1,<=6.0.10.

The above modification suggestions can reduce the dependency conflicts as much as possible,
and introduce the latest version as much as possible without calling Error in the projects.

The invocation of the current project includes all the following methods.

The calling methods from the feedparser
feedparser.parse
The calling methods from the all methods
readme.open.read
readme.open.write
format
sorted
join
replace_chunk
re.findall
requests.get.sub
feedparser.parse
requests.get
readme.open
entry.split
pathlib.Path
__file__.pathlib.Path.parent.resolve
fetch_blog_entries
re.compile
get_tils

@developer
Could please help me check this issue?
May I pull a request to fix it?
Thank you very much.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions