Re: [python-win32] Relevance of very outdated `Pythonwin/pywin/idle`

2024-01-12 Thread Mark Hammond 
Some of those modules are actually used by pythonwin, particularly by 
pywin/scintilla - so while I agree the ability to update them is 
questionable, I don't think just killing the directory makes sense. Did 
you try to remove it? I'd be surprised if Pythonwin continues to work in 
that scenario.



I also don't see a huge maintenance cost nor must automated tooling 
churn - I haven't seen much in the way of external PRs touching this, 
nor have I personally touched these files recently - indeed most of the 
churn I see if from the *introduction* of such tooling, so one solution 
to that is probably to not try and introduce new tooling which touches 
or checks these files.



Cheers,


Mark


On 2024-01-12 12:50 p.m., Samuel Therrien wrote:

Hi!

I recently had to do a deep dive into 
https://github.com/mhammond/pywin32/tree/main/Pythonwin/pywin/idle 
 as 
part of a previous PR. See comment: 
https://github.com/mhammond/pywin32/pull/2102#discussion_r1380422005 



Of course it is extremely outdated, but I think the interesting part 
is that these IDLE modules are now part of the cpython repo (although 
most have been renamed over time), and some modules seem to not even 
be used as part of pythonwin.


I basically expect that none of this works at all today, especially 
given the minimum version requirement of Python 3.7-3.8. Is this worth 
keeping around at all?


 *
Pythonwin will look for IDLE extensions first in this directory,
then on the global sys.path.  Thus, if you have IDLE installed and
run it from the CVS sources, you may remove most of the extensions
from this directory, and the latest CVS version will then be used.

Could we just delete this entire folder instead, and update 
references, reducing further maintenance cost and automated tooling 
churn? Anything special I should look for in testing?



Basic type-checking with mypy and pyright by Avasam · Pull Request 
#2102 · mhammond/pywin32 

This is the PR that finally makes basic type-checking validation of 
public methods possible, easing the addition of 3.7+ type annotations. 
In its current state, a lot of checks are disabled, and so...

github.com

//


___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32

[python-win32] Relevance of very outdated `Pythonwin/pywin/idle`

2024-01-12 Thread Samuel Therrien 
Hi!

I recently had to do a deep dive into 
https://github.com/mhammond/pywin32/tree/main/Pythonwin/pywin/idle as part of a 
previous PR. See comment: 
https://github.com/mhammond/pywin32/pull/2102#discussion_r1380422005

Of course it is extremely outdated, but I think the interesting part is that 
these IDLE modules are now part of the cpython repo (although most have been 
renamed over time), and some modules seem to not even be used as part of 
pythonwin.

I basically expect that none of this works at all today, especially given the 
minimum version requirement of Python 3.7-3.8. Is this worth keeping around at 
all?


  *

Pythonwin will look for IDLE extensions first in this directory, then on
the global sys.path.  Thus, if you have IDLE installed and run it from
the CVS sources, you may remove most of the extensions from this
directory, and the latest CVS version will then be used.


Could we just delete this entire folder instead, and update references, 
reducing further maintenance cost and automated tooling churn? Anything special 
I should look for in testing?
[https://opengraph.githubassets.com/b62496876f356f98f081228d039b0186cbce83377c606fe280d33ceba55766fc/mhammond/pywin32/pull/2102]
Basic type-checking with mypy and pyright by Avasam · Pull Request #2102 · 
mhammond/pywin32
This is the PR that finally makes basic type-checking validation of public 
methods possible, easing the addition of 3.7+ type annotations. In its current 
state, a lot of checks are disabled, and so...
github.com


___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32

Re: [python-win32] PythonService was unable to locate the service manager

2024-01-12 Thread Mark Hammond 

On 2024-01-11 5:46 p.m., Jacob Nolan via python-win32 wrote:


I performed a custom install for all users on my E: drive 
(E:/installs/python3). Added it to the path. It is not under my 
specific user account. My understanding is this is a global install.


What exactly is E:? If anything other than a local device it might not 
be available to the user running the service.


I then run it under administrator privileged cmd and successfully 
install the service.


Looking at security permissions for pythonservice.exe in the root 
python directory. SYSTEM and Admin users have full control.


To be clear, the entire Python tree will need those permissions, not 
just that .exe. And the question is whether the user running the service 
has access - SYSTEM and Admin should cover many common scenarios, but 
not all. You could try configuring the service for your specific user 
just to see if it works - if it does it would still point to user 
permissions.


Mark





*Jacob Nolan*
*Gayner Technical Services*
Phone: 0437210168
Email: j...@gaynertechnicalservices.com.au
On 1/12/24 01:19, Mark Hammond wrote:


The "" 
part sounds like it is failing to find Python itself. Where is Python 
installed? Is it possible the user running the service can't access 
that location? I believe Python being installed in the default 
location could cause this if the server is running as any other other 
than the user which installed Python.


Mark


On 2024-01-11 1:20 a.m., Jacob Nolan via python-win32 wrote:


Currently experiencing this issue on my Windows machine when 
installing a Windows Service. This is the error output I get from 
running in the cmd as administrator. Restricting me from being able 
to run my services.


*- PythonService was unable to locate the service manager. Please 
see the event log for details.**

*


Here is the output from event viewer application log:

|The description for Event ID 14 from source Python Service cannot 
be found. Either the component that raises this event is not 
installed on your local computer or the installation is corrupted. 
You can install or repair the component on the local computer. If 
the event originated on another computer, the display information 
had to be saved with the event. The following information was 
included with the event: traceback.print_exception() failed> The specified resource type 
cannot be found in the image file |



This issue has happened on each of these version I've tested 
Python3.11, 3.10.10 and 3.10.8.


Currently running Python 3.10.8 64 Bit on Windows Server 2016.

- I've installed pywin32

- Run post_install in the root directory of python310

- Installed the service with install flag

- Attempted to start service with start flag

- PythonService was unable to locate the service manager. Please see 
the event log for details.


--
*Thanks*
*Jacob*

___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32


___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32

Re: [python-win32] PythonService was unable to locate the service manager

2024-01-12 Thread Jacob Nolan via python-win32 
I performed a custom install for all users on my E: drive 
(E:/installs/python3). Added it to the path. It is not under my specific 
user account. My understanding is this is a global install.


I then run it under administrator privileged cmd and successfully 
install the service.


Looking at security permissions for pythonservice.exe in the root python 
directory. SYSTEM and Admin users have full control.



*Jacob Nolan*
*Gayner Technical Services*
Phone: 0437210168
Email: j...@gaynertechnicalservices.com.au
On 1/12/24 01:19, Mark Hammond wrote:


The "" 
part sounds like it is failing to find Python itself. Where is Python 
installed? Is it possible the user running the service can't access 
that location? I believe Python being installed in the default 
location could cause this if the server is running as any other other 
than the user which installed Python.


Mark


On 2024-01-11 1:20 a.m., Jacob Nolan via python-win32 wrote:


Currently experiencing this issue on my Windows machine when 
installing a Windows Service. This is the error output I get from 
running in the cmd as administrator. Restricting me from being able 
to run my services.


*- PythonService was unable to locate the service manager. Please see 
the event log for details.**

*


Here is the output from event viewer application log:

|The description for Event ID 14 from source Python Service cannot be 
found. Either the component that raises this event is not installed 
on your local computer or the installation is corrupted. You can 
install or repair the component on the local computer. If the event 
originated on another computer, the display information had to be 
saved with the event. The following information was included with the 
event:  
The specified resource type cannot be found in the image file |



This issue has happened on each of these version I've tested 
Python3.11, 3.10.10 and 3.10.8.


Currently running Python 3.10.8 64 Bit on Windows Server 2016.

- I've installed pywin32

- Run post_install in the root directory of python310

- Installed the service with install flag

- Attempted to start service with start flag

- PythonService was unable to locate the service manager. Please see 
the event log for details.


--
*Thanks*
*Jacob*

___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32