I'm having a similar issue as https://github.com/tmux/tmux/issues/2594.
I use tmux + ssh to connect to a remote server from two different laptops, a macbook where I run iTerm2 with the tmux integration (tmux -CC), and another one a Chromebook where I run tmux normally, without -CC.
I don't run the two tmux clients at the same time, I only use either one or the other.
Every time I use iTerm2, even after detaching the latter, when I reopen the session from the other laptop, the window-size tmux option is set "manual" instead of being unset and defaulting to "latest", which means the windows have fixed size (the same size as was last set inside iTerm on the other mac laptop). This is very annoying. The only way to fix it at the moment is to manually do tmux set-option -u window-size for each tmux window, to unset the option that iTerm2 has set.
Initially I was using the latest stable tmux 3.3a from homebrew, then I tried to install the latest --HEAD, the versions shows as next-3.4. I installed the same on both client and remote server. But it still doesn't work.
It's strange because on the linked tmux issue (https://github.com/tmux/tmux/issues/2594), the author of iTerm2 says that this bug should have been fixed with this commit: https://github.com/gnachman/iTerm2/commit/c708876b6f8d106a9573984462368a1388f570e5 But it doesn't seem to work for me.
brew install --HEAD tmux at commit 9ef854f)~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window)
com.googlecode.iterm2.plist
The size of the panes still seems to be determined by -CC window.
After detaching iTerm2, tmux show immediately allow the window size to snap to the currently-connected client.
The current protobuf version available from PyPI is v3.11.1. This MR adds support for building wheels for that version.
Cosimo Lupo (ead81f42) at 20 Dec 12:48
Add version info for 3.11.1
thanks, makes sense. I gather it isn't currently possible to enumerate all metadata files?
It would be nice to be able to get the dist-info or egg-info metadata directory path for a given python package name.
For example, py2app would need to know where this metadata is on the filesystem in order to copy it inside the generated .app bundle
https://bitbucket.org/ronaldoussoren/py2app/issues/256/fs-module-not-fully-working-from-app
Currently one could do that with importlib_metadata via the Distribution._path attribute, however the leading underscore suggests that that is not part of the api.
Could/should it be made public (read-only perhaps)?