Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Python script can't import ssl | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | General | Reporter: | psilocybe <prrvchr> | ||||||
Component: | scripting | Assignee: | AOO issues mailing list <issues> | ||||||
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | |||||||
Severity: | Normal | ||||||||
Priority: | P5 (lowest) | CC: | oooforum, prrvchr | ||||||
Version: | 4.0.0 | ||||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Windows, all | ||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
Developer Difficulty: | --- | ||||||||
Attachments: |
|
Description
psilocybe
2023-05-28 10:34:32 UTC
I forgot to mention that everything works fine with OpenOffice 4.x.x and Ubuntu and therefore this problem seems to be more related to the OpenOffice package delivered for Windows. Up... Would anyone be kind enough to confirm or not this issue? Created attachment 87189 [details]
importSSL.py macro
Put the macro importSSL.py in the right folder with the command:
copy importSSL.py %UserProfile%\AppData\Roaming\OpenOffice\4\user\Scripts\python
Run macro through menus:
Tools -> Macros -> Run macros... -> My Macros -> importSSL -> importSSL -> Run
Normally there must be an error on import ssl module.
More information here: https://forum.openoffice.org/fr/forum/viewtopic.php?p=373903#p373903 Created attachment 87197 [details] No error encountered when script running Remember that this issue tracker is not dedicated for OXT debug. Testing with your step-by-step in comment #3 No error occurs with AOO 4.1.14 and Windows 10 x64 Pro (In reply to oooforum (fr) from comment #5) > Remember that this issue tracker is not dedicated for OXT debug. This has nothing to do with my extension since I manage to reproduce just with this python macro!!! I'm surprised, Bidouille, that you bothered to try... Anyway OAuth2OOo 1.x has just migrated to Python 3.8 minimum. No more support for OpenOffice and LibreOffice 6.x on Windows. For me this problem is solved... (In reply to psilocybe from comment #7) > For me this problem is solved... So issue is closed too You are free to do what you are responsible for.
But given the macro that I took the trouble to write and which confirms this issue, I don't think this decision makes much sense:
> it is not because you close an issue that it is resolved ...
It only confirms that I made the right decision to migrate to Python 3.8 minimum...
(In reply to psilocybe from comment #9) > But given the macro that I took the trouble to write and which confirms this > issue, I don't think this decision makes much sense Read my comment 5 and see the attached screenshot |