Python 3.7 support
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t38178_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t38178_1 && git checkout t38178_1Patchset v1 (message #1) is on t38178_1
A small patch to tweak the tests to support output differences with
Python 3.7 (currently in beta).
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On Tue, Feb 13, 2018 at 04:17:13PM -0500, Peter Eisentraut wrote:
A small patch to tweak the tests to support output differences with
Python 3.7 (currently in beta).
Wouldn't it be better to wait for the version to be released before
pushing anything in the tree? If there are again changes when this
comes out as GA then an extra patch would be needed.
--
Michael
On 2/13/18 21:45, Michael Paquier wrote:
On Tue, Feb 13, 2018 at 04:17:13PM -0500, Peter Eisentraut wrote:
A small patch to tweak the tests to support output differences with
Python 3.7 (currently in beta).Wouldn't it be better to wait for the version to be released before
pushing anything in the tree? If there are again changes when this
comes out as GA then an extra patch would be needed.
Sure, we can just leave it here for the record until the release comes
closer.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On 2/14/18 21:25, Peter Eisentraut wrote:
On 2/13/18 21:45, Michael Paquier wrote:
On Tue, Feb 13, 2018 at 04:17:13PM -0500, Peter Eisentraut wrote:
A small patch to tweak the tests to support output differences with
Python 3.7 (currently in beta).Wouldn't it be better to wait for the version to be released before
pushing anything in the tree? If there are again changes when this
comes out as GA then an extra patch would be needed.Sure, we can just leave it here for the record until the release comes
closer.
I have committed this now, since the release of Python 3.7 is soon.
I'll let the build farm have a pass at it, then backport it for the
upcoming minor releases.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
I have committed this now, since the release of Python 3.7 is soon.
I'll let the build farm have a pass at it, then backport it for the
upcoming minor releases.
gaur/pademelon (Python 2.5) not very happy :-(. Let me know if you'd
like me to try anything particular there.
regards, tom lane
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
I have committed this now, since the release of Python 3.7 is soon.
I'll let the build farm have a pass at it, then backport it for the
upcoming minor releases.
If you're intending to push this into the back branches before Monday's
releases, please do it *today*, the sooner the better. We are rapidly
closing in on the point where we'd not have a full set of buildfarm runs
done before the wrap. That is not a good situation for a patch with
portability implications.
regards, tom lane