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