Re: python install defies all efforts and leaves programmer a broken shell of a man - Mailing list pgsql-sql
From | Michael Moore |
---|---|
Subject | Re: python install defies all efforts and leaves programmer a broken shell of a man |
Date | |
Msg-id | CACpWLjPi0t=Zvbj0x_SY3RvK6kcM75m8bwZxH0UTz01gSzoaSg@mail.gmail.com Whole thread Raw |
In response to | Re: python install defies all efforts and leaves programmer a broken shell of a man (Adrian Klaver <adrian.klaver@aklaver.com>) |
List | pgsql-sql |
On Wed, May 11, 2016 at 1:38 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 05/11/2016 11:43 AM, Michael Moore wrote:I followed your instructions and got python2 running. I was hoping for
python3, but python2 should be just fine to learn on . Thanks for your help.
Out of curiosity was that with the EDB installer or the BigSQL one?
On Tue, May 10, 2016 at 5:07 PM, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
On 05/10/2016 04:51 PM, Michael Moore wrote:
On Tue, May 10, 2016 at 4:30 PM, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>> wrote:
On 05/10/2016 04:25 PM, Michael Moore wrote:
I think I've tried every combination of postgres 9.4 and 9.5
and psycopg2 and python. I've used Dependency Walker to
examine
dlls and
read countless web pages. My current error is "ERROR:
could not
load
library "C:/Program
Files/PostgreSQL/9.4/lib/plpython3.dll": The
specified procedure could not be found." Many people have
encountered
this error and there seems to be no shortage of
"solutions". So my
question is, does anybody have a clean set of
instructions on
how to get
python working on a windows install of postgres; any
version. I'm
flexible, I can start fresh, I don't care which versions, I
don't care
if it's 32 bit or 64 bit. I just want to try it out.
How did you install Postgres and from what source?
Where and when are you getting the error message?
Thanks,
Mike
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com>>
Hi, I installed postgres from http://www.postgresql.org/ . I have
version 94 and 95 installed and running on my windows 7 machine
in 64
bit. I use pgAdmin and these installs are running with no
problems. I
get the aforementioned error message when I execute: "
CREATE EXTENSION plpython3u
SCHEMA pg_catalog
VERSION "1.0";'
Also when I try "CREATE PROCEDURAL LANGUAGE 'plpython3u', same
result.Dependency walker shows a dependency on PYTHON33.DLL and
there is
no such file as that either in /lib or /bin. So, according to
various
"solution", I should be able to download this missing DLL . I've not
done this yet because 1) it seems suspicious that a DLL is
missing from
the install and 2) I don't tend to trust sites that offer free DLLs.
Virus city.
Do not play in Windows much, but I believe you have to use the
StackBuilder that is installed along with with the database. Select
it and then look for the Language Pack section.
Another, recently announced option(though it means uninstalling your
current cluster, I believe):
http://www.postgresql.org/message-id/CAKq0gv+Gc0i8j=ktQSkMkLJmmTqUHAm=Eza7zLv+MdXCB6H+Bw@mail.gmail.com
http://www.bigsql.org/
I have not tried the above yet, so I can offer no practical advice.
Also Python is at 2.7.11(http://www.bigsql.org/components.jsp).
Mike
--
Adrian Klaver
--
Adrian Klaver
adrian.klaver@aklaver.com
I'm pretty sure it was BigSQL which installed all of the extension in a sub directory:
C:\Postgres95\PostgreSQL\pg95\share\postgresql\extension
C:\Postgres95\PostgreSQL\pg95\share\postgresql\extension
this is the location of file plpython2u.control which Postgres tries to find when you do the CREATE LANGUAGE command. I don't know if this is the standard place where Postgres looks for this .control file or if it is part of the BigSQL install.
Postgres95 is a folder that I created for the install target.
After the install I still needed to so
CREATE EXTENSION 'plpython2u'; and
CREATE EXTENSION 'plpython2u'; and
CREATE PROCEDURAL LANGUAGE 'plpythonu'
HANDLER plpython_call_handler
INLINE plpython_inline_handler
VALIDATOR plpython_validator;
I don't think that the EnterpriseDB languagepack had anything to do with it unless the install did some magic that I was not aware of.