why don't we leave the complexity of 'pip-sync' behind and make a fresh subclass that knows nothing about pip-sync and doesn't need to replace many methods in a complicated way
I'm honestly so proud of this approach, the only horrible thing is that the object replaces its own __class__ on the fly. But I'm pretty sure this will just work with no problems.
juftin
commented
9 months ago
Alternative to #30 - mostly untested for now, early code.
Please look at it commit by commit. In particular this commit shows the very core of the idea: https://github.com/oprypin/hatch-pip-compile/commit/1d5f100de5d6f57338d9a1dcf11f00484d501153
why don't we leave the complexity of 'pip-sync' behind and make a fresh subclass that knows nothing about pip-sync and doesn't need to replace many methods in a complicated way
I'm honestly so proud of this approach, the only horrible thing is that the object replaces its own
__class__on the fly. But I'm pretty sure this will just work with no problems.