You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pylint GitHub actions of the Artisan project started to fail once pip v24.1 was released. As this did not get fixed by the pip v24.1.1 I reported the issue: pypa/pip#12825
Although your marker package seems not contradict any rules (thus I am not an expert on packaging), if possible, it might be good if you could adjust the yoctopuce package marker to prevent this issue from occuring.
The text was updated successfully, but these errors were encountered:
Hey @MAKOMO 👋 The thing about this bug is that the package marker causing the problem doesn't come from the package being depended on, but from the one that has it as a dependency. In this case, the source of the error is where yoctopuce is listed in Artisan's own requirements.txt file. There isn't really anything that yoctopuce can or should do about this.
Understood. So because the yoctopuce package is the first one being discriminated by sys_platform in our requirements.txt it is the point where pip >24.0 first fails. Thus closing this here and hoping for an upstream fix.
The pylint GitHub actions of the Artisan project started to fail once pip v24.1 was released. As this did not get fixed by the pip v24.1.1 I reported the issue: pypa/pip#12825
The pip team analyzed the issue and found that it goes back to an open upstream issue in pypa/packaging.
The pip team then added some better error logging which the revealed that the culprit is the yoctopuce package.
Although your marker package seems not contradict any rules (thus I am not an expert on packaging), if possible, it might be good if you could adjust the yoctopuce package marker to prevent this issue from occuring.
The text was updated successfully, but these errors were encountered: