Pure Python
All code, at first, is written in pure Python so that py-postgresql will work
anywhere that you can install Python 3. Optimizations in C are made where
needed, but are always optional.
Prepared Statements
Using the PG-API interface, protocol-level prepared statements may be created
and used multiple times. db.prepare(sql)(*args)
COPY Support
Use the convenient COPY interface to directly copy data from one connection to
another. No intermediate files or tricks are necessary.
Arrays and Composite Typescw
Arrays and composites are fully supported. Queries requesting them will returns
objects that provide access to the elements within.
"pg_python" Quick Console
Get a Python console with a connection to PostgreSQL for quick tests and simple
scripts.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py311-postgresql listed in the above command, you can pick from the names under the Packages section.
python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal
Any missed ports, feel free to bump.
Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.
all: drop support for expired FreeBSD 14.0
Simplify expressions for FreeBSD 13.X
Reviewed by: many
Differential Revision: https://reviews.freebsd.org/D46601
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
databases/py-postgresql: Support python 3.4
When python 3 only is specified, building the port tries to install
python 3.3 even if python 3.4 is requested, so this change addresses that.
PR: 194656
Submitted by: Axel Rau (chaos1.de)
Approved by: maintainer timeout
databases/py-postgresql: remove local plist hack and support staging
- clarify the license (BSD3C)
- use 3 in USE_PYTHON
- convert to using auto-generated packing list and remove NO_STAGE
- remove local plist hack - it is now handled by bsd.python.mk
- bump PORTREVISION for the case
Approved by: portmgr (blanket)
- update to 1.1.0
- trim Makefile header completely (requested by maintainer)
- add CHEESESHOP and make it primary MASTER_SITE, because other locations
doesn't hold the new release yet
- remove one distfile mirror (requested by maintainer)
- add LICENSE (BSD)
- replace USE_XZ with USE_ZIP, since it was changed upstream
- tune PYDISTUTILS_PKGNAME
- move python32 plist stuff into separate file
changelog:
http://pgfoundry.org/pipermail/python-general/2012-October/001003.html
PR: 172544 (but I can't see it in GNATS because of hub transition)
Submitted by: rm (myself)
Approved by: Volodymyr Kostyrko <c.kworr at gmail dot com> (maintainer, by mail)
- Update to 1.0.4 [1]
- Fix pkg-plist when Python version >= 3.2
(solution approved by maintainer via private email)
PR: ports/167569
Submitted by: William Grzybowski <william88 at gmail.com>
Approved by: Volodymyr Kostyrko <c.kworr at gmail.com> (maintainer)
Pure Python
All code, at first, is written in pure Python so that py-postgresql will work
anywhere that you can install Python 3. Optimizations in C are made where
needed, but are always optional.
Prepared Statements
Using the PG-API interface, protocol-level prepared statements may be created
and used multiple times. db.prepare(sql)(*args)
COPY Support
Use the convenient COPY interface to directly copy data from one connection to
another. No intermediate files or tricks are necessary.
Arrays and Composite Typescw
Arrays and composites are fully supported. Queries requesting them will returns
objects that provide access to the elements within.
"pg_python" Quick Console
Get a Python console with a connection to PostgreSQL for quick tests and simple
scripts.
WWW: http://python.projects.postgresql.org/
PR: ports/137782
Submitted by: Volodymyr Kostyrko <c.kworr@gmail.com>
