From hanthonyhoyt at gmail.com Wed Sep 25 15:36:15 2019 From: hanthonyhoyt at gmail.com (Tony Hoyt) Date: Wed, 25 Sep 2019 15:36:15 -0400 Subject: [python-ldap] Wheel file for RHEL 7 Message-ID: I have a question for your team. At one point, I was able to download a RHEL 7 compatible wheel file for python-ldap 3.1.0. When i try to pull down the library now, my process tries to build from source instead and it fails. I can't really update my build environment so I'm going on a prayer that you guys might have a copy or can dig up a copy one way or another. Do you guys still have a copy of it somewhere? I swear it existed at one point but I can't find it anywhere. I have snippets of the wheel file buried in a old build of my app including a file named "_ ldap.cpython-36m-x86_64-linux-gnu.so", but it appears that there is no pip cache for me to pull from on this one. Can you guys help me out at all on this because I'm in a bit of a bad spot. Thanks Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: From encukou at gmail.com Wed Sep 25 17:15:27 2019 From: encukou at gmail.com (Petr Viktorin) Date: Wed, 25 Sep 2019 23:15:27 +0200 Subject: [python-ldap] Wheel file for RHEL 7 In-Reply-To: References: Message-ID: <8dc9bb19-257a-ef64-6854-2d9a19e5dc0b@gmail.com> On 2019-09-25 21:36, Tony Hoyt wrote: > I have a question for your team.At one point, I was able to download a > RHEL 7 compatible wheel file for python-ldap 3.1.0.When i try to pull > down the library now, my process tries to build from source instead and > it fails.? I can't really update my build environment so I'm going on a > prayer that you guys might have a copy or can dig up a copy one way or > another.? Do you guys still have a copy of it somewhere?? I swear it > existed at one point but I can't find it anywhere.? I have snippets of > the wheel file buried in a old build of my app including a file named > "_ldap.cpython-36m-x86_64-linux-gnu.so > ", but it appears that > there is no pip cache for me to pull from on this one.?? Can you guys > help me out at all on this because I'm in a bit of a bad spot.? Thanks Hello, Where did you download the wheel? AFAIK, there was no wheel released for 3.1.0. I don't have one around, sorry. You are asking strangers on the internet to give you compiled code, which, presumably, you want to expose to your company infrastructure. That does not sound like a good idea. If you can't update the build environment, can you set up a new system instead? The main reason python-ldap doesn't distribute binary wheels nowadays is that doing this securely is quite difficult ? PyPI wheels (manylinux, Windows, macOS) would need to bundle OpenLDAP, which we'd need to keep patched with security updates. Also, binary wheels from PyPI aren't really auditable. From olivier.waterloos at aginsurance.be Mon Sep 30 07:05:36 2019 From: olivier.waterloos at aginsurance.be (olivier.waterloos at aginsurance.be) Date: Mon, 30 Sep 2019 11:05:36 +0000 Subject: [python-ldap] fatal error C1083: Cannot open include fil In-Reply-To: References: Message-ID: <2dbea5db79df45df9bb6356396d56c38@aginsurance.be> Hello, I have an issue to install the package python-ldap: C:\Users\\AppData\Local\Temp\easy_install-imrjml50\python-ldap-3.2.0\Modules\constants.h(7): fatal error C1083: Cannot open include fil e: 'lber.h': No such file or directory error: Setup script exited with error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.23.28 105\\bin\\HostX86\\x64\\cl.exe' failed with exit status 2 On the internet I found the whl from the site https://www.lfd.uci.edu/~gohlke/pythonlibs/#python-ldap, but the module stays unrecognized. I have download python-ldap-3.2.0.tar.gz and it gives the same error. Do you have another solution? I'm on Windows 2016 Standard 64bits with Python 3.7. Thanks Kind regards Olivier Waterloos I&O Collaboration & Applic. Engineering +32 2 664 03 70 +32 473 98 03 82 Visit our website on www.aginsurance.be [AGI_SIGNATURE_GIRAFFE] Deze e-mail, met inbegrip van elk bijgevoegd document, is vertrouwelijk. Indien u niet de geadresseerde bent, is het openbaar maken, kopi?ren of gebruik maken ervan verboden. Indien u dit bericht verkeerdelijk hebt ontvangen, gelieve het te vernietigen en de afzender onmiddellijk te verwittigen. De veiligheid en juistheid van email-berichten kunnen niet gewaarborgd worden, aangezien de informatie kan onderschept of gesaboteerd worden, verloren gaan of virussen kan bevatten. De afzender wijst bijgevolg elke aansprakelijkheid af in dergelijke gevallen. Indien een controle zich opdringt, gelieve een papieren kopie te vragen. Ce message ?lectronique, y compris tout document joint, est confidentiel. Si vous n'?tes pas le destinataire de ce message, toute divulgation, copie ou utilisation en est interdite. Si vous avez re?u ce message par erreur, veuillez le d?truire et en informer imm?diatement l'exp?diteur. La s?curit? et l'exactitude des transmissions de messages ?lectroniques ne peuvent ?tre garanties ?tant donn? que les informations peuvent ?tre intercept?es, alt?r?es, perdues ou infect?es par des virus; l'exp?diteur d?cline d?s lors toute responsabilit? en pareils cas. Si une v?rification s'impose, veuillez demander une copie papier. This email and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this email. Email transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. If verification is required please request a hard copy version. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 67591 bytes Desc: image001.jpg URL: From pviktori at redhat.com Mon Sep 30 08:31:19 2019 From: pviktori at redhat.com (Petr Viktorin) Date: Mon, 30 Sep 2019 14:31:19 +0200 Subject: [python-ldap] fatal error C1083: Cannot open include fil In-Reply-To: <2dbea5db79df45df9bb6356396d56c38@aginsurance.be> References: <2dbea5db79df45df9bb6356396d56c38@aginsurance.be> Message-ID: On 2019-09-30 13:05, olivier.waterloos at aginsurance.be wrote: > Hello, > > I have an issue to install the package python-ldap: > > C:\Users\\AppData\Local\Temp\easy_install-imrjml50\python-ldap-3.2.0\Modules\constants.h(7): > fatal error C1083: Cannot open include fil > > e: 'lber.h': No such file or directory > > error: Setup script exited with error: command 'C:\\Program Files > (x86)\\Microsoft Visual > Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.23.28 > > 105\\bin\\HostX86\\x64\\cl.exe' failed with exit status 2 > > On the internet I found the whl from the site > https://www.lfd.uci.edu/~gohlke/pythonlibs/#python-ldap, but the module > stays unrecognized. > > I have download python-ldap-3.2.0.tar.gz and it gives the same error. > > Do you have another solution? > > I?m on Windows 2016 Standard 64bits with Python 3.7. > > Thanks > Hello! The instructions for Windows are available here: http://python-ldap.org/en/python-ldap-3.2.0/installing.html#installing-from-pypi Note that you need the build prerequisites. That's what you are missing; 'lber.h' is part of OpenLDAP. If you can figure out a better way to build on Windows, please share. Unfortunately, I haven't seen many people on this list contribute Windows knowledge. I don't use Windows myself.