Searched refs:pythonw (Results 1 – 20 of 20) sorted by relevance
| /external/python/cpython3/Mac/ |
| D | Makefile.in | 175 pythonw: $(srcdir)/Tools/pythonw.c Makefile
177 $(srcdir)/Tools/pythonw.c -I.. -I$(srcdir)/../Include \
272 rm pythonw
|
| /external/python/cpython3/PC/ |
| D | pythonw_exe.rc | 15 1 ICON DISCARDABLE "icons\pythonw.ico"
45 VALUE "OriginalFilename", "pythonw" PYTHON_DEBUG_EXT ".exe\0"
|
| D | pylauncher.rc | 17 1 ICON DISCARDABLE "icons\pythonw.ico"
24 6 ICON DISCARDABLE "icons\pythonw.ico"
|
| /external/python/cpython3/Lib/idlelib/ |
| D | idle.bat | 4 start "IDLE" "%CURRDIR%..\..\pythonw.exe" "%CURRDIR%idle.pyw" %1 %2 %3 %4 %5 %6 %7 %8 %9
|
| /external/python/cpython3/ |
| D | .gitignore | 90 Mac/pythonw
|
| D | Makefile.pre.in | 2211 $(INSTALL_PROGRAM) $(STRIPFLAG) Mac/pythonw $(DESTDIR)$(BINDIR)/python$(LDVERSION)$(EXE); \
2832 cd Mac && $(MAKE) pythonw
|
| /external/python/cpython3/Tools/msi/bundle/bootstrap/ |
| D | PythonBootstrapperApplication.cpp | 669 LPWSTR pythonw = nullptr; in EnableMaxPathSupport() local
670 StrAllocFormatted(&pythonw, L"%ls\\pythonw.exe", targetDir); in EnableMaxPathSupport()
671 if (!pythonw || !pythonw[0]) { in EnableMaxPathSupport()
685 BalLog(BOOTSTRAPPER_LOG_LEVEL_STANDARD, "Executing %ls %ls", pythonw, arguments); in EnableMaxPathSupport()
686 HINSTANCE res = ShellExecuteW(0, L"runas", pythonw, arguments, NULL, SW_HIDE); in EnableMaxPathSupport()
|
| /external/python/cpython3/PCbuild/ |
| D | readme.txt | 101 pythonw
102 pythonw.exe, a variant of python.exe that doesn't open a Command
|
| D | pcbuild.sln | 57 Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "pythonw", "pythonw.vcxproj", "{F4229CC3-873C-4…
|
| /external/python/cpython3/Doc/library/ |
| D | site.rst | 137 with :file:`pythonw.exe` on Windows (which is used by default to start IDLE),
|
| D | idle.rst | 720 A zombie pythonw.exe process could be a problem. On Windows, use Task
776 use ``python`` or ``py`` rather than ``pythonw`` or ``pyw``.)
|
| D | sys.rst | 1893 to a console and Python apps started with :program:`pythonw`.
|
| D | multiprocessing.rst | 1115 set_executable(os.path.join(sys.exec_prefix, 'pythonw.exe'))
|
| /external/python/cpython3/Doc/using/ |
| D | windows.rst | 532 ``python.exe`` and ``pythonw.exe`` are all provided. Tcl/tk (including all
571 directly calls the ``python.exe`` or ``pythonw.exe`` with the required
|
| /external/python/cpython3/Misc/NEWS.d/ |
| D | 3.13.1.rst | 65 Fix venvwlauncher to launch pythonw instead of python so no extra console
|
| D | 3.5.0a1.rst | 1218 pythonw.exe.
2258 run with pythonw.exe.
|
| D | 3.9.0a1.rst | 4642 Remove ``pythonw.exe`` dependency on the Microsoft C++ runtime.
|
| /external/python/cpython3/Doc/whatsnew/ |
| D | 3.6.rst | 159 * ``python.exe`` and ``pythonw.exe`` have been marked as long-path aware,
|
| D | 3.7.rst | 2559 creates redirector scripts named ``python.exe`` and ``pythonw.exe`` instead.
|
| /external/python/cpython3/Misc/ |
| D | HISTORY | 1089 is run with pythonw.exe.
1436 when it is run with pythonw.exe.
3647 undocumented pythonw* symlinks are no longer installed anywhere.
12924 - Issue #6834: replace the implementation for the 'python' and 'pythonw'
17112 Windows GUI apps and scripts started with `pythonw.exe`.
20086 - Boosted the stack reservation for python.exe and pythonw.exe from
21047 asking whether to let pythonw.exe talk to address 127.0.0.1, say yes,
21116 - Scripts runs with pythonw no longer had full window manager access.
21315 - pythonw did not allow user interaction in 2.3rc1, this has been fixed.
23338 bundle. There is a command line tool "pythonw" that runs your script
[all …]
|