Pywin32
Pywin32 support for sublime (win32api etc)
Details
Installs
- Total 11K
- Win 11K
- Mac 5
- Linux 0
Jul 27 | Jul 26 | Jul 25 | Jul 24 | Jul 23 | Jul 22 | Jul 21 | Jul 20 | Jul 19 | Jul 18 | Jul 17 | Jul 16 | Jul 15 | Jul 14 | Jul 13 | Jul 12 | Jul 11 | Jul 10 | Jul 9 | Jul 8 | Jul 7 | Jul 6 | Jul 5 | Jul 4 | Jul 3 | Jul 2 | Jul 1 | Jun 30 | Jun 29 | Jun 28 | Jun 27 | Jun 26 | Jun 25 | Jun 24 | Jun 23 | Jun 22 | Jun 21 | Jun 20 | Jun 19 | Jun 18 | Jun 17 | Jun 16 | Jun 15 | Jun 14 | Jun 13 | Jun 12 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 0 | 4 | 2 | 2 | 7 | 3 | 2 | 2 | 1 | 2 | 5 | 1 | 3 | 0 | 0 | 6 | 2 | 2 | 3 | 3 | 1 | 1 | 2 | 5 | 1 | 2 | 1 | 5 | 2 | 2 | 0 | 1 | 4 | 5 | 1 | 1 | 4 | 3 | 2 | 6 | 2 | 3 | 0 | 1 | 2 | 5 |
Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
Pywin32 (Deprecated)
This package was deprecated in favor of the pywin32
library,
which your package can depend on
and Package Control will install accordingly.
See https://packagecontrol.io/docs/dependencies on how to specify a dependency on this library
(previously called “dependency”)
in your package.
Pywin32 support for sublime (win32api etc)
Still evaluating what needs to be included and what doesn't, so if it is missing something important, please let me know.
Using Pywin32
Pywin32 modules should be accessible as soon as Sublime loads up the Pywin32 plugin…but since there is no guarunteed way to ensure all plugins are loaded after Pywin32 gets loaded, you should include Pywin32.setup
before including any pywin32 modules. You can include it once in the top most level file, and all subsequent includes from that file should be guarunteed access. It does not have to be included in all files that call pywin32 modules, just once in the top level file that is the entry point. If I could guaruntee pywin32 to get loaded before all plugins, then even this requriement would not be necessary.
Example (show url path of all open explorer windows):
import Pywin32.setup
from win32com.client.gencache import EnsureDispatch
def run():
for w in EnsureDispatch("Shell.Application").Windows():
print(w.LocationName + "=" + w.LocationURL)
run()