> On Feb 4, 2019, at 2:36 AM, Łukasz Langa wrote:
>
> @Raymond, would you be willing to work with Davin on finishing this work in
> time for alpha2?
I would be happy to help, but this is beyond my technical ability. The people
who are qualified to work on this have already chimed in on the d
I'll merge it tonight.
On Mon, Feb 4, 2019 at 2:22 PM Guido van Rossum wrote:
> OK, I approved the PR. Can some other core dev ensure that it gets merged?
> No backports though!
>
> On Mon, Feb 4, 2019 at 8:46 AM Paul Ganssle wrote:
>
>> There's already a PR, actually, #10902:
>> https://github
OK, I approved the PR. Can some other core dev ensure that it gets merged?
No backports though!
On Mon, Feb 4, 2019 at 8:46 AM Paul Ganssle wrote:
> There's already a PR, actually, #10902:
> https://github.com/python/cpython/pull/10902
>
> Victor reviewed and approved it, I think before I starte
The main problem here seems to be a shortage of communication. :/
Also, I agree on the exceptional nature of merging incomplete PRs.
-eric
On Mon, Feb 4, 2019 at 3:37 AM Łukasz Langa wrote:
>
>
> > On 4 Feb 2019, at 01:49, Guido van Rossum wrote:
> >
> > I think this is now up to the 3.8 releas
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 pyt
On Mon, 4 Feb 2019 09:45:39 -0600
Zachary Ware wrote:
> On Mon, Feb 4, 2019 at 4:39 AM Antoine Pitrou wrote:
> > What I did (*) is different: I asked to mark Davin inactive and to stop
> > auto-assigning him on bug tracker issues. Davin was /still/ listed in
> > the experts list, along with me a
There's already a PR, actually, #10902:
https://github.com/python/cpython/pull/10902
Victor reviewed and approved it, I think before I started this thread,
so now it's just waiting on merge.
On 2/4/19 11:38 AM, Guido van Rossum wrote:
> I recommend that you submit a PR so we can get it into 3.8 a
I recommend that you submit a PR so we can get it into 3.8 alpha 2.
On Mon, Feb 4, 2019 at 5:50 AM Paul Ganssle wrote:
> Hey all,
>
> This thread about the return type of datetime operations seems to have
> stopped without any explicit decision - I think I responded to everyone who
> had objecti
Hello Davin,
I would like this discussion to be constructive and not vindicative. So
I would ask that we leave personal attacks out of this.
> I have been part of several group discussions (among core developers)
> now regarding how to balance the efforts of contributors with copious
> time to
On Mon, Feb 4, 2019 at 4:39 AM Antoine Pitrou wrote:
> What I did (*) is different: I asked to mark Davin inactive and to stop
> auto-assigning him on bug tracker issues. Davin was /still/ listed in
> the experts list, along with me and others. IOW, there was no "editing
> out".
Auto-assignment
Antoine's change to the devguide was made on the basis that "he doesn't
contribute anymore" which, going by Antoine's own description in this
thread, he contradicts.
My current effort, mentioned in Antoine's other thread, is not my single
largest contribution. I have been impressed by the volume
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
Hey all,
This thread about the return type of datetime operations seems to have
stopped without any explicit decision - I think I responded to everyone
who had objections, but I think only Guido has given a +1 to whether or
not we should go ahead.
Have we got agreement to go ahead with this chang
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 - https://wirte
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 improv
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, Pyth
On 02/04, Łukasz Langa wrote:
On 4 Feb 2019, at 11:58, Stephane Wirtel wrote:
Hi all,
After a git pull, I have seen there is a merge for v3.8.0a1 by Łukasz
Langa, why? I think the code should keep a linear commit and in this
case, it's against the "commit&squash" of CPython and Github :/
Th
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 devel
> On 4 Feb 2019, at 11:58, Stephane Wirtel wrote:
>
> Hi all,
>
> After a git pull, I have seen there is a merge for v3.8.0a1 by Łukasz
> Langa, why? I think the code should keep a linear commit and in this
> case, it's against the "commit&squash" of CPython and Github :/
>
> Thank you for you
Hi all,
After a git pull, I have seen there is a merge for v3.8.0a1 by Łukasz
Langa, why? I think the code should keep a linear commit and in this
case, it's against the "commit&squash" of CPython and Github :/
Thank you for your response.
Stéphane
--
Stéphane Wirtel - https://wirtel.be - @mat
Hello,
In a recent message, Raymond dramatically pretends that I would have
"edited out" Davin of the maintainers list for the multiprocessing
module.
What I did (*) is different: I asked to mark Davin inactive and to stop
auto-assigning him on bug tracker issues. Davin was /still/ listed in
t
> On 4 Feb 2019, at 01:49, Guido van Rossum wrote:
>
> I think this is now up to the 3.8 release manager.
I responded on the tracker: https://bugs.python.org/issue35813#msg334817
I wrote:
> @Davin, in what time can you fill in the missing tests and documentation? If
> this is something you
On Sun, 3 Feb 2019 21:12:38 -0600
Davin Potts wrote:
>
> I was encouraged by Lukasz, Yury, and others to check in this code early,
> not waiting for tests and docs, in order to both solicit more feedback and
> provide for broader testing.
For the record: submitting a PR without tests or docs is
On Sun, 3 Feb 2019 18:10:43 -0800
Raymond Hettinger wrote:
> > On Feb 3, 2019, at 5:40 PM, Terry Reedy wrote:
> >
> > On 2/3/2019 7:55 PM, Guido van Rossum wrote:
> >> Also, did anyone ask Davin directly to roll it back?
> >
> > Antoine posted on the issue, along with Robert O. Robert revi
On Sun, 3 Feb 2019 17:52:55 -0800
Raymond Hettinger wrote:
> > On Feb 3, 2019, at 1:03 PM, Antoine Pitrou wrote:
> >
> > I'd like to ask for the reversion of the changes done in
> > https://github.com/python/cpython/pull/11664
>
> Please work *with* Davin on this one.
You know, Raymond, I'm
On Sun, 3 Feb 2019 21:25:27 -0600
Davin Potts wrote:
> On 2/3/2019 7:55 PM, Guido van Rossum wrote:
> > Also, did anyone ask Davin directly to roll it back?
>
> Simply put: no. There have been a number of reactionary comments in the
> last 16 hours but no attempt to reach out to me directly d
> On 4 Feb 2019, at 04:25, Davin Potts
> wrote:
>
> On 2/3/2019 7:55 PM, Guido van Rossum wrote:
> > Also, did anyone ask Davin directly to roll it back?
>
> Simply put: no. There have been a number of reactionary comments in the
> last 16 hours but no attempt to reach out to me directly
27 matches
Mail list logo
