Hi,
Le ven. 1 mars 2019 à 02:12, Neil Schemenauer a écrit :
> I believe the correct fix is to use PEP 3121 per-interpreter module
> state. I created a new issue:
>
> https://github.com/psycopg/psycopg2/issues/854
>
> I think the fix is not trival as the psycopgmodule.c source code has
>
On 2019-02-26, Stephane Wirtel wrote:
> I also filled an issue [2] for brotlipy (used by httpbin and requests).
> The problem is with PyInterpreterState.
I tried compiling psycopg2 today and it has a similar problem:
psycopg/psycopgmodule.c: In function ‘psyco_is_main_interp’:
Armin Rigo released https://pypi.org/project/cffi/1.12.2/ which is
compatible with Python 3.8.0a2.
The issue was related to the PyInterpreterState change:
https://bugs.python.org/issue35886#msg336501
Note: "[RELEASE] Python 3.8.0a1 is now available for testing" the
correct version is 3.8.0a2 :-)
Hi Łukasz,
Thank you for your job.
I have created a Merge Request for the docker image of Barry [1].
I also filled an issue [2] for brotlipy (used by httpbin and requests).
The problem is with PyInterpreterState.
Via Twitter, I have proposed to the community to fix the issue [2].
[1]:
I packaged another release. Go get it here:
https://www.python.org/downloads/release/python-380a2/
Python 3.8.0a2 is the second of four planned alpha releases of Python 3.8,
the next feature release of Python. During the alpha phase, Python 3.8
remains under heavy development: additional
On 2/7/19 5:16 PM, Stephane Wirtel wrote:
On 02/06, Petr Viktorin wrote:
On 2/6/19 8:43 AM, Stephane Wirtel wrote:
On 02/05, Barry Warsaw wrote:
On Feb 5, 2019, at 02:24, Stephane Wirtel wrote:
You’re welcome! I just pushed an update to add 3.8.0a1 to the set
of Python’s (including git
Sorry Petr,
I didn't see this message with the test suites.
--
Stéphane Wirtel - https://wirtel.be - @matrixise
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On 02/06, Petr Viktorin wrote:
On 2/6/19 8:43 AM, Stephane Wirtel wrote:
On 02/05, Barry Warsaw wrote:
On Feb 5, 2019, at 02:24, Stephane Wirtel wrote:
You’re welcome! I just pushed an update to add 3.8.0a1 to the set
of Python’s (including git head). Do you think there’s a better
way to
On 2/6/19 2:26 PM, Matthias Klose wrote:
On 06.02.19 13:23, Petr Viktorin wrote:
FWIW, we're preparing to rebuild all Fedora packages with the 3.8 alphas/betas,
so everything's tested when 3.8.0 is released:
https://fedoraproject.org/wiki/Changes/Python3.8
That should cover the main Python
On 06.02.19 13:23, Petr Viktorin wrote:
> FWIW, we're preparing to rebuild all Fedora packages with the 3.8
> alphas/betas,
> so everything's tested when 3.8.0 is released:
> https://fedoraproject.org/wiki/Changes/Python3.8
>
> That should cover the main Python projects, too.
well, the real
On 2/6/19 8:43 AM, Stephane Wirtel wrote:
On 02/05, Barry Warsaw wrote:
On Feb 5, 2019, at 02:24, Stephane Wirtel wrote:
You’re welcome! I just pushed an update to add 3.8.0a1 to the set of
Python’s (including git head). Do you think there’s a better way to
publicize these images?
I know
On 02/05, Barry Warsaw wrote:
On Feb 5, 2019, at 02:24, Stephane Wirtel wrote:
You’re welcome! I just pushed an update to add 3.8.0a1 to the set of Python’s
(including git head). Do you think there’s a better way to publicize these
images?
I know that Julien Palard wanted a docker image
On Feb 5, 2019, at 02:24, Stephane Wirtel wrote:
>
> I was not aware of this image. So it's true that it's very useful.
>
> Thank you very much,
You’re welcome! I just pushed an update to add 3.8.0a1 to the set of Python’s
(including git head). Do you think there’s a better way to publicize
Hi Barry,
I was not aware of this image. So it's true that it's very useful.
Thank you very much,
Stéphane
On 02/04, Barry Warsaw wrote:
On Feb 4, 2019, at 05:02, Stephane Wirtel wrote:
Just one idea, we could create a Docker image with this alpha version.
This Docker image could be used
On Feb 4, 2019, at 05:02, Stephane Wirtel wrote:
>
> Just one idea, we could create a Docker image with this alpha version.
>
> This Docker image could be used with the CI of the main projects and the
> test suites of these projects.
>
> If we have some issues, we should create an issue for
Hi Łukasz,
I have some issues with pytest and this release, you can see this BPO
https://bugs.python.org/issue35895
Have a nice day and thank you for your job.
Stéphane
--
Stéphane Wirtel - https://wirtel.be - @matrixise
___
Python-Dev mailing list
On 02/04, Stephane Wirtel wrote:
It's unofficial but I used the Dockerfile for 3.7 and created this
Docker image:
https://cloud.docker.com/u/matrixise/repository/docker/matrixise/python
Sorry: here is the right link
https://hub.docker.com/r/matrixise/python
--
Stéphane Wirtel -
It's unofficial but I used the Dockerfile for 3.7 and created this
Docker image:
https://cloud.docker.com/u/matrixise/repository/docker/matrixise/python
docker pull matrixise/python:3.8.0a1
I am not an expert about the releasing of a Docker image but we could
work with that and try to
On 02/04, Łukasz Langa wrote:
I packaged my first release. *wipes sweat off of face*
Go get it here:
https://www.python.org/downloads/release/python-380a1/
Python 3.8.0a1 is the first of four planned alpha releases of Python 3.8,
the next feature release of Python. During the alpha phase,
I packaged my first release. *wipes sweat off of face*
Go get it here:
https://www.python.org/downloads/release/python-380a1/
Python 3.8.0a1 is the first of four planned alpha releases of Python 3.8,
the next feature release of Python. During the alpha phase, Python 3.8
remains under heavy
20 matches
Mail list logo
