Consolidation with pypi-timemachine?

[pelson]

Hi!

Hope you don't mind me opening this, but I notice that this project seems to aim for very similar functionality to https://github.com/astrofrog/pypi-timemachine, and I was wondering if there was an interest to consolidate the two projects? For a long time, pypi-timemachine was stuck on pypi.org, and based on the (non PEP-691 JSON API), but I recently adapted pypi-timemachine to use https://github.com/simple-repository which means that it is now PEP-503 based (either html or JSON) and can work on any index (technically, including the local filesystem).

Whilst I'm not the original author of pypi-timemachine, I'm pretty sure there would be interest in collaborating to bring together these two very similar tools (I also note that @edgarrmondragon has contributed to both project 😄). Is this something that is of interest to you also?

Since this is an issue with a potential on-going action (hopefully! 😄), I propose that we close this issue once you've had a read and a chance to respond 👍

[notatallshaw]

Oh great to hear that pypi-timemachine is now using standard APIs! I wasn't aware of the update.

The reason I created this project is I was having performance issues with pypi-timemachine and needed something for my project: https://github.com/notatallshaw/Pip-Resolution-Scenarios-and-Benchmarks

I'm not quite sure merging makes sense, I ended up adding a couple of hooks that are specific to my needs.

For me it might make more sense to get the functionality I need baked directly into pip, e.g. by pushing pypa/pip#12717 over the finish line.