Support For DRF 3.15 nested SimpleRouter.use_regex_path = False

[Gibsondz]

This PR is to address the following issue:
#342

In order to properly use use_regex_path=False for the simple router you must have DRF 3.15+. If the kwarg is passed and an earlier version of DRF is used it should simply TypeError due to the unexpected kwarg . If this requires a read-me update for notes around Requirements & Compatibility let me know what you would like to see there and I can add it.

The changes are the same as suggested in #342 and are explained in more detail there. The changes are essentially changing how we pre-pend the parent url when use_regex_path=False, allowing it to correctly nest the routes. I also added a unit test validating the changes.

Please let me know if you have any concerns or questions!

[davidjayb]

@alanjds would it be possible to get this merged in?

[alanjds]

Thanks @davidjayb for the ping. This PR is good and totally got out of my radar.

That said, why is the DRF 3.14 support being dropped on CI?
Would be possible to keep the CI for 3.14?

I say that because usually I like to keep support at least for the latest-1 version of stuff.

[alanjds]

During conflict solving, I updated the tox file to test with DRF 3.14 and 3.15, and they both passed.

So I am merging the update and will release a version after some days with this running just on master, letting people to report some unlikely issue.

Again, thanks @Gibsondz a lot for the contribution and @davidjayb for the heads up.

[Gibsondz]

Hey @alanjds thanks for getting this pushed through, was a nice surprise. It was a while ago, but I believe I may have preemptively removed 3.14 from the CI because I thought it would potentially fail when running the new test_non_regex_recursive_nested_simple_router test due to the passed use_regex_path kwarg.

However it seems that is not the case so thanks for reverting that. Cheers!

[stevelacey]

Just came across this PR while running into use_regex_path issues — seems like parent path segments are getting dropped from my nested routes 😵‍💫. Would really appreciate it if a release could be tagged so I can check if this fixes my issue 🙏

[alanjds]

Hi @stevelacey. In meantime I suggest you to install from master of this GitHub, or even point to the specific commit.

From a long time I do need to flex my muscle and learn how to issue dev/beta/preview releases on PyPI, yet I had not bitten this bullet so far.

[stevelacey]

Fair enough 🙃 Installing from master seems to have solved my problems, thanks! 👍