When I run snowflake.connector.connect(**credentials['MY_DATABASE']), I get the following warning:
~/opt/anaconda3/lib/python3.8/site-packages/cryptography/hazmat/backends/openssl/x509.py:14: CryptographyDeprecationWarning: This version of cryptography contains a temporary pyOpenSSL fallback path. Upgrade pyOpenSSL now.
warnings.warn(
I have updated pyOpenSSL to its latest version. These are the versions I've installed:
I am not sure what updates I need to make to avoid getting this warning. I'd appreciate your help.
Related
I am getting 20 errors every time I install web3.js. I tried using earlier versions of the library but am still getting errors. I found this thread and was able to download version 0.19.0 but there is no documentation for 0.19.0 on the web so it's not really usable. Does anyone have any ideas?
I have a private package in npm which is very frequently updated,
and i want to do a minor change on one of theprevious versionsof the package.
for example my current version is 1.14.0 and i want to make change on top of 1.11.1, so that all the changes after 1.11.1 are excluded.
EDIT
versions released in between
1.11.1, 1.12.0, 1.12.1, 1.12.2, 1.13.0, 1.14.0
Is it possible? if yes how?
Thanks
What is the most reliable source to find the latest version number?
Is it github?
And if yes, which version should I take?
Right now, here is what I see:
Should I take the 1.0.2k?
But then 1.1.0d seems like it is more recent (if it follows semantic versioning). What do the letters actually mean?
Note: in my case this is to compile an openssl version with nginx.
Last time I picked (quite randomly) the version 1.0.2h which seemed the latest at the time.
So what is the process to follow to find the latest openssl version?
https://www.openssl.org/ shows which version are current and supported.
Currently there are two major versions in development: 1.1.0 and 1.0.2. 1.1.0 is newer and has more features. But due to the cleanups between 1.0.2 and 1.1.0 lots of undocumented API (i.e. things which never were an official API but got used anyway since no official API existed) got broken and not all software works or works stable with 1.1.0 yet. Also, 1.1.0 tends to introduce not only features but also bugs faster than 1.0.2 when looking at the release history. And with 1.1.0 the chance is higher that documented behavior changes even between patch releases.
Thus if you need the new features with 1.1.0 then go with it. If you prefer a more stable version with a smaller chance of bugs use 1.0.2. In all cases you should always use the latest patch release and keep using it if new patches get released or backport security patches.
I attempted to update my version of SVN from 1.7 to 1.8 as per this guide:
http://snippets.khromov.se/subversion-1-8-centos-6/
All seemed to install fine, however now I have an issue when I try to restart Apache:
/usr/sbin/httpd: symbol lookup error: /usr/sbin/httpd: undefined symbol: apr_crypto_init
Does anyone know how to solve this?
Which packages need to be updated?
I had same issue after installing some perl modules.
I did the following to resolve it:
yum remove vulture-common-3.2-185.1.x86_64
cd /usr/lib
ln -sf libaprutil-1.so.0.2.9 libaprutil-1.so.0
ln -sf libapr-1.so.0.2.9 libapr-1.so.0
apr_crypto_init is new with APR-Util 1.4.x. CentOS 6 should already have APR-Util 1.4.x. So either you're not using CentOS 6 which those instructions are made for or you're not using the apr-util/httpd version that comes with CentOS 6.
If you're not using CentOS 6 then I suggest you go get a version built for your distribution from WANdisco's download site (the script that the site you linked to actually is from WANdisco).
If you're using your own httpd version you'll either have to switch or you'll have to build your own copy of Subversion.
I have had similar experiences with other applications using this library and Centos 6.x. I have tracked most of the problems down to using the 'minimum install' version of the OS. From what I have been able to determine, the minimum or light install versions of Centos have a tendency to have older versions of the binaries. For example, my version of APR-Utils are 1.3x even though I am using version 6.6.
This is supposedly done for better stability and backward compatibility from what I can find but it causes some headaches if you aren't aware. You may need to use a more 'complete' version of the OS in order for this library to be the latest version, provided you are starting from scratch.
I have:
Ubuntu 8.04
python 2.5.2 installed on this Ubuntu
matplotlib 0.92.0 installed
I want to upgrade to (atleast) matplotlib 0.99
so that I can do 3d plotting.
The synaptic package (also the command line apt-get)
tells me that whatever I have is the latest matplotlib (which is not true).
How can I install matplotlib 0.99 or matplotlib 1.0.1 ?
You have the latest available package version for your operating system. Given that Ubuntu is at version 11 now and you are using 8.04, the version difference in the matplotlib package might not come as very surprising.
As for installing the newest version, I'd suggest reading:
http://matplotlib.sourceforge.net/faq/installing_faq.html
...if all fails, you can always install from source.
Note that support for Desktop versions of 8.04 LTS is due to expire shortly -- if this is a desktop machine, perhaps the easiest answer is to upgrade to 10.04 LTS, 10.10, or the very-soon-upcoming 11.04 release (or whatever they'll call the next release). Maybe not "the easiest answer", but an answer that includes security updates for Mozilla, Adobe Flash, the Kernel, and so forth.
Many newer versions of packages are supported via the Ubuntu Backports facility, but I didn't spot python-matplotlib in the list of available packages. Perhaps they would provide it if you asked nicely, perhaps it would be too much work.
You can always try installing newer versions from newer releases, but newer versions of python and libraries might introduce worse problems. (But probably will work fine.) See the apt_preferences(5) manpage for details on how to configure multiple APT sources and select some specific packages from a newer distribution (pinning), and rely on the older distribution for all the other packages.
Jim's answer of building the version you need from source is probably your best second option, if installing a newer version of the distribution is too daunting / otherwise impossible at this point.