Pywin32
Pywin32 support for sublime (win32api etc)
Details
Installs
- Total 12K
- Win 12K
- Mac 5
- Linux 0
Jan 21 | Jan 20 | Jan 19 | Jan 18 | Jan 17 | Jan 16 | Jan 15 | Jan 14 | Jan 13 | Jan 12 | Jan 11 | Jan 10 | Jan 9 | Jan 8 | Jan 7 | Jan 6 | Jan 5 | Jan 4 | Jan 3 | Jan 2 | Jan 1 | Dec 31 | Dec 30 | Dec 29 | Dec 28 | Dec 27 | Dec 26 | Dec 25 | Dec 24 | Dec 23 | Dec 22 | Dec 21 | Dec 20 | Dec 19 | Dec 18 | Dec 17 | Dec 16 | Dec 15 | Dec 14 | Dec 13 | Dec 12 | Dec 11 | Dec 10 | Dec 9 | Dec 8 | Dec 7 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 2 | 3 | 4 | 2 | 4 | 3 | 5 | 2 | 1 | 5 | 2 | 5 | 5 | 4 | 5 | 3 | 0 | 2 | 1 | 0 | 1 | 0 | 2 | 0 | 2 | 2 | 3 | 2 | 2 | 1 | 0 | 1 | 3 | 1 | 0 | 3 | 2 | 3 | 0 | 4 | 1 | 3 | 2 | 0 | 1 | 4 |
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()