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
unasync.py --check will currently happily allow stale files in _sync. It would be simple enough to make the tool treat the destination directory as fully managed and make sure it strictly matches the output of unasyncing _async with no extra files.
At the same time it would probably be good to improve / start using the unasync package so that effort isn't getting repeated.
We would be happy to collaborate here! @johtso If you get one pull request merged in the python-trio org, you'll be invited as a collaborator to approve pull requests, and we'd be happy to allow you making releases too.
I'm going to close this one off for now. No pressing motivation for us to do this given our current workflow.
Am not neccessarily against considering any pull requests switching to unasync.py, but otherwise I don't see any clear need to treat this as an open issue.
unasync.py --check
will currently happily allow stale files in_sync
. It would be simple enough to make the tool treat the destination directory as fully managed and make sure it strictly matches the output of unasyncing_async
with no extra files.At the same time it would probably be good to improve / start using the
unasync
package so that effort isn't getting repeated.See:
python-trio/unasync#66
python-trio/unasync#68
python-trio/unasync#69
The text was updated successfully, but these errors were encountered: