databases/py-postgresql1.3.0_1

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>

databases/py-postgresql: Fix build with llvm15

Approved by:	portmgr (blanket)

databases/py-postgresql: Update to 1.3.0

Update maintainer's email
Update WWW

PR:		269488
Reported by:	maintainer

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

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.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

One more small cleanup, forgotten yesterday. Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

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

Switch default python3 version from 3.3 to 3.4. Bump PORTREVISIONs for the affected ports.

Exp-run by:	antoine

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

Convert USES=pgsql and USES=python:3

Convert d* to USES=zip

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)

Fix properties on pkg-plist

Add NO_STAGE all over the place in preparation for the staging support (cat: databases)

- 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)

- Get Rid MD5 support

- Update to 1.0.2

PR:		ports/150773
Submitted by:	Volodymyr Kostyrko <c.kworr at gmail.com> (maintainer)
Approved by:	pgollucci (mentor)

Update to version 1.0.1

PR:	ports/148148
Submitted by:	Volodymyr Kostyrko <c.kworr@gmail.com>
Approved by:	itetcu@ (mentor) implicit
Feature safe: yes

- Update to 0.9.3

PR:		ports/142473
Submitted 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>