Skip to content

Remove install_requires to ensure users are not stuck using outdated dependencies #372

@jacklinke

Description

@jacklinke

Background

Because this package uses install_requires it is almost never usable with recent versions of django (and often same with DRF). Almost no other package I have seen uses this restriction (or at least not so strictly), which forces end-users to use old versions of dependencies.

I ended up just forking and removing the overly-strict limitations in install_requires, but I am sure other folks try to install this package, fail to be able to do so, and abandon it forever.

It looks like there was an intent from @suavesav to deprecate and eventually remove this file, but it must have stalled at some point. @ryochiji previously made some good comments about the approach that should be taken.

Recommendation

Considering the historical pace at which dynamic-rest releases come out, I think we should go further and simply remove this roadblock. (Please don't read that as a dig at the maintainers - I know how time-consuming maintaining a package can be. I only mean to say that if releases do not keep pace with the django/DRF release schedule, having install_requires.txt in place means dynamic-rest will forever require users to install old versions of these dependencies.)

If the maintainers find this approach acceptable, I will gladly submit a PR to help with this effort.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions