You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally they should be submit the patch, or someone elses should submit it with the patch author set to the correct author. Ping also @techalchemy who has been heavily involved in the pipenv vendoring.
The text was updated successfully, but these errors were encountered:
Now I understand the patches effect a bit better, this feels like it isnt a complete patch, as that inline comment after an entry probably needs to be removed with the entry in some cases, and it should be up to the caller whether 'dangling' comments should be kept, so some mechanism needs to be added to allow the caller to control this. But that is just a guess, and I'd appreciate feedback from @sdispater about whether this patch is acceptable as-is .
this patch is authored by me to preserve the comment when an entry is removed. It is required by pipenv in the regressiin cases. However it is not always expected
for a general toml document. Cases are user may want to remove the comments together with the line it is bound to. So I just patch it in pipenv vendor but leave it to original creator how to design it.
pipenv applies a patch to their vendored copy of tomlkit, and it seems that it doesnt exist here yet.
The patch is https://github.com/pypa/pipenv/blob/master/tasks/vendoring/patches/vendor/tomlkit-fix.patch
Parts of that have been merged, but the bit that looks missing is:
Is this an appropriate addition to tomlkit?
It appears the author was @frostming , originally at https://github.com/pypa/pipenv/commits/6df7d8861da841e552049dcde9ff9a0f23edc01e/tasks/vendoring/patches/vendor/tomlkit-dump-inline-table.patch
I dont see any similar patch in https://github.com/sdispater/tomlkit/commits?author=frostming
Ideally they should be submit the patch, or someone elses should submit it with the patch author set to the correct author. Ping also @techalchemy who has been heavily involved in the pipenv vendoring.
The text was updated successfully, but these errors were encountered: