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