| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Add transforms feature |
| Date: | 2015-04-28 20:15:20 |
| Message-ID: | 553FEA58.4070001@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 4/28/15 4:10 PM, Andrew Dunstan wrote:
>> Do we actually have a Windows machine building with Python3?
>
>
> The answer seems to be "probably not". When I tried enabling this with
> bowerbird I got a ton of errors like these:
>
> plpy_cursorobject.obj : error LNK2001: unresolved external symbol
> PyObject_SelfIter [C:\prog\bf\root\HEAD\pgsql\plpython3.vcxproj]
> plpy_cursorobject.obj : error LNK2019: unresolved external symbol
> __imp_PyType_Ready referenced in function PLy_cursor_init_type
> [C:\prog\bf\root\HEAD\pgsql\plpython3.vcxproj]
>
>
> Something else to fix I guess.
I think at least at one point the community Windows binaries built by
EnterpriseDB were built against Python 3 (which upset some users). But
they might not be using the msvc toolchain.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2015-04-28 20:31:59 | shared_libperl, shared_libpython |
| Previous Message | Andrew Dunstan | 2015-04-28 20:10:42 | Re: [COMMITTERS] pgsql: Add transforms feature |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2015-04-28 20:31:59 | shared_libperl, shared_libpython |
| Previous Message | Andrew Dunstan | 2015-04-28 20:10:42 | Re: [COMMITTERS] pgsql: Add transforms feature |