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 documentation refers to pip install straight.plugin being the canonical method of installing straight.plugin, so I'm going to work on the assumption that it's intended for that method to work. However, the latest version downloaded by that command (1.4.0) is broken, which you acknowledged and fixed in #9. Unfortunately you chose a new version number (1.4.0-post-1) that ensured users will never get the working version with the supplied instructions, since it fails to parse as an accepted version number and gets counted as a "pre-release" (according to pip documentation).
Please could you re-release that version under something sensible that won't leave loads of people downloading a broken version forever, especially since this project no longer seems to have any active development, and therefore may never have a 1.4.1 to eliminate this problem? PEP 440 (and even it's predecessor PEP 386) suggests 1.4.0.post1 as more correct, but even 1.4.0-1, to match your version numbering in the past, would work.
The text was updated successfully, but these errors were encountered:
The documentation refers to
pip install straight.plugin
being the canonical method of installingstraight.plugin
, so I'm going to work on the assumption that it's intended for that method to work. However, the latest version downloaded by that command (1.4.0
) is broken, which you acknowledged and fixed in #9. Unfortunately you chose a new version number (1.4.0-post-1
) that ensured users will never get the working version with the supplied instructions, since it fails to parse as an accepted version number and gets counted as a "pre-release" (according topip
documentation).Please could you re-release that version under something sensible that won't leave loads of people downloading a broken version forever, especially since this project no longer seems to have any active development, and therefore may never have a
1.4.1
to eliminate this problem? PEP 440 (and even it's predecessor PEP 386) suggests1.4.0.post1
as more correct, but even1.4.0-1
, to match your version numbering in the past, would work.The text was updated successfully, but these errors were encountered: