| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Removed keyword Placeholder restriction from this and will issue a separate PR after. Felt like too much is packed into 1 PR. |
Sorry, something went wrong.
|
@dg-pb Is this PR still relevant or have you opened PRs for the different components? If so, can we close this one? |
Sorry, something went wrong.
|
It is still relevant. I could factor "allowing trailing placeholders" into a separate one if it is preferred. |
Sorry, something went wrong.
I have not looked at all the changes in detail, but the PR seems big and that could be a reason this PR has not yet been reviewed. In the description at least 3 changes are mentioned (allowing placeholders, performance, refactor for partialmethod). If possible, I would advice to split the PR into multiple PRs. |
Sorry, something went wrong.
There are 2 really. Performance benefit is a consequence of "allowing trailing placeholders". I don't mind making changes, splitting as desired etc, but I would like these to be called by reviewer. Otherwise, I already have experience by trying to guess what reviewer might prefer, making changes per suggestions of others, etc and when final reviewer comes he desires to be different again and I need to keep changing things more times than necessary. And either way these would need to be considered at the same time. I.e. allowing or not allowing trailing placeholders are both ok. There is a slight advantage for allowing them as it makes it a bit more flexible and explicit. While looking at partial from the POV of using it on methods, the advantages and rationale for allowing them can be seen more clearly putting it on a favourable side (at least this is my conclusion). Also, if I split now, then I have PRs hanging on unmerged code.
It isn't that big. Most of it is Pure Python rewrite of partialmethod and the implementation is much simpler to follow than the previous one. |
Sorry, something went wrong.
|
As this series of partial related PRs started slowly moving, the path became a bit clearer and splitting this into 2 seems to be the best option to me now. Will do that shortly. |
Sorry, something went wrong.
|
@serhiy-storchaka, just a gentle reminder. |
Sorry, something went wrong.
|
@dg-pb, I am reviewing, I just was very busy last days with other issue. |
Sorry, something went wrong.
|
@serhiy-storchaka, I think it would be good to merge this. Otherwise, it will be sitting there for another version. inspect simplification is what I think has most value here. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
@serhiy-storchaka, I think this can be merged regardless of #128644. And maybe we could reopen #128644 so that it has another chance for consideration? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
partialmethod Benchmarks:
Setup