4 ms·

The flask-login package should have limited its dependencies to flask<3.0, that's what major versions are for.

• miguelgrinberg 3y ago
  So consider what happens when you try to learn Flask in a world like the one you describe. You pip install Flask, and you get 3.0. Next chapter asks you to install Flask-Login, and now you are forced to downgrade Flask. What you are saying makes sense when there are important reasons to break compatiblity. But I expect the Flask side to love their users a bit more and not break their code for trivial reasons.
  • JimDabell 3y ago
    > You pip install Flask, and you get 3.0 The learning material should specify a major version so this doesn’t happen.
  • lcnPylGDnU4H9OF 3y ago
    > trivial reasons This is a bit like a No True Scotsman argument. It says that there are reasons for what happened but they didn't have a Good Reason. Why are their reasons so particularly trivial? > try to learn Flask in a world like the one you describe This seems moot if the Flask maintainers are using semantic versioning correctly. I'd probably look into it and think that Flask-Login maintainers should have limited their Flask version if they were going to step away from maintenance. If someone else wants to pick it up they can fork it or try to get in touch with the old maintainers to get access to the central repo.
  • ilyt 3y ago
    framework developer isn't responsible for random tutorials going out of date because abandoned plugin wasn't updated in 2+ years