Jump to content

K.Lalkovski

Vectorworks, Inc Employee
  • Posts

    111
  • Joined

  • Last visited

Reputation

39 Great

Personal Information

  • Location
    Bulgaria

Contact Info

  • Skype
    k.lalkovski

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @Paolo, I saw you have already found a solution, but here is an example on Windows that finds package certifi. Just open vwx file and run find certifi node. The problem with the module not being found is that certifi for VW2023(Win) is not a direct descendant of the 'site-packages' folder and just the path to certifi needs to be added at runtime. testcertifipresence.vwx
  2. Hi Niels Timmer, Could you please attach here the object you have created in order for us to look into it? Thanks, Konstantin
  3. Hi @_James Yes, NBS Chorus plug-in works for 2023.Please, see attached video on how to install the plug-in with VW 2023. Regards Konstantin How to install NBS Chorus.mp4
  4. Hi TBexon, I do not know if you have found the solution for your issue or still interested in running PyOpenSSL with Vectorworks, but on Friday I started looking at this problem while resolving a bug from Dominique about the serch path. The DLL that pyOpenSSL looks for is python3.dll.It is in python's folder where also python.exe resides. This path is included in the python search paths in VW. For some reason the code of pyOpenSSL when installed cannot find python3.dll.It's package's code search problem. If you copy python3.dll from python's folder to VW application folder(where VW exe resides) you will be able to use pyOpenSSl.
  5. Hi @Paolo, There are two approaches to resolve the problem: First approach: Replace VW2022 SP1(619242) with the new VW 2022 SP2(622317) . Second, if you prefer to deal with the existing VW2022 SP1(619242) Please, find the attached file scripts.zip. On the problematic PC: 1. Go to <VW App folder>\Python39\Scripts 2.Delete the contents of this folder. 3.Unzip the contents of the scripts.zip file 4.Run VW and try to install PIL. You should be able to install the Pillow package and any other package. Let me know if this works for you! Scripts.zip
  6. Hi @Paolo, Please, take a look at the attached video. What is the number of the Autobuild 2022 you are testing on windows? Give me also details of your system configuration(windows version, processor). The warning on Mac will be removed in 2022 SP3. Could you prepare a video file for me to see what exactly happens on your machine? Pillow Install.mp4
  7. Hi TBexon, if you run this on 2022 it is going to work(returns true): localized_True_Bool = vs.EvalStr(vs.Handle(0), "1=1") # Gets Localised True Bool vs.AlrtDialog(str(localized_True_Bool))/*I removed type() here*/ Regards, Konstantin
  8. @tbexon I asked my colleagues @Yasen Aleksiev to look into this and answer you.
  9. Hello @Paolo I have been working on this issue when I have a good result I'll let you know.
  10. @tbexon Where do you receive this behavior om Mac OS or Windows?
  11. @Paolo It is a warning, not an error. The pip module is part of the current python distribution with Vectorworks, both on PC and Mac. The distribution is embedded into the Vectorworks application bundle on Mac. On Win it is just a folder on the disk. On Mac, the pip module cannot be directly accessed as this can be done on PC. This line of code is used to access the embedded pip on Mac ret_code = pip.main(['install', destination,'-q','--target', cmd]) and it is the reason for the warning. In the next version of VerifyOrGetLib, I'll fix the line in order to remove that warning.
×
×
  • Create New...