Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy wrote: > > On 2/28/2019 6:54 PM, Glenn Linderman wrote: > > > There seems to be enough evidence that something went wrong somewhere, > > though, and whoever maintains that process should start investigating, > > but it would still be nice to get

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 6:54 PM, Glenn Linderman wrote: There seems to be enough evidence that something went wrong somewhere, though, and whoever maintains that process should start investigating, but it would still be nice to get confirmation from a non-Google email recipient whether they did or did

Re: [Python-Dev] [RELEASE] Python 3.8.0a1 is now available for testing

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 >

Re: [Python-Dev] Summary of Python tracker Issues

On 2019-02-28 23:54, Glenn Linderman wrote: On 2/28/2019 2:52 PM, Terry Reedy wrote: On 2/28/2019 5:38 PM, Glenn Linderman wrote: On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote:     On 2/28/2019 8:07 AM, Jonathan Goble

Re: [Python-Dev] [RELEASE] Python 3.8.0a1 is now available for testing

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’:

Re: [Python-Dev] Summary of Python tracker Issues

> > It's also possible that the fault is not in sending (we have evidence here > that two entirely different protocols have not received it, and they are also > not in the archives [1]), but in the generation of the report. Could there > have been a subtle change to the bpo tracker itself, or

Re: [Python-Dev] Summary of Python tracker Issues

On Thu, Feb 28, 2019 at 6:57 PM Glenn Linderman wrote: > On 2/28/2019 2:52 PM, Terry Reedy wrote: > > On 2/28/2019 5:38 PM, Glenn Linderman wrote: > > On 2/28/2019 2:18 PM, Jonathan Goble wrote: > > On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote: > > On

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 2:52 PM, Terry Reedy wrote: On 2/28/2019 5:38 PM, Glenn Linderman wrote: On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote:     On 2/28/2019 8:07 AM, Jonathan Goble wrote:     > On Thu, Feb 28, 2019, 8:02 AM

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 5:38 PM, Glenn Linderman wrote: On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote: On 2/28/2019 8:07 AM, Jonathan Goble wrote: > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote: On 2/28/2019 8:07 AM, Jonathan Goble wrote: > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki mailto:songofaca...@gmail.com> >

Re: [Python-Dev] Summary of Python tracker Issues

On Thu, Feb 28, 2019, 5:11 PM Terry Reedy wrote: > On 2/28/2019 8:07 AM, Jonathan Goble wrote: > > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki > > wrote: > > > > No stats for last week? > > > > > > Been missing for two weeks actually. I did not receive a summary

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 8:07 AM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 8:02 AM INADA Naoki > wrote: No stats for last week? Been missing for two weeks actually. I did not receive a summary on either the 15th or 22nd. Ditto for me. I get pydev via gmane.

Re: [Python-Dev] Compact ordered set

Antoine Pitrou wrote: On a more abstract level, set and dict are both content-addressed collections parametered on hash and equality functions. Indeed. It's been said that a set is like "half a dict", and this is why sets were implemented using dicts in the old days. It's kind of an obvious

Re: [Python-Dev] datetime.timedelta total_microseconds

You could specify the return value type annotations in the docstring of a convert()/to_unit() method, or for each to_unit() method. Are they all floats? div and floordiv are not going away. Without reading the docs, I, too, wouldn't have guessed that division by the desired unit is the correct

Re: [Python-Dev] datetime.timedelta total_microseconds

> while "some_var / some_other_var" could be doing anything. "At an elementary level the division of two natural numbers is – among other possible interpretations – the process of calculating the number of times one number is contained within another one." --

Re: [Python-Dev] Compile-time resolution of packages [Was: Another update for PEP 394...]

On Wed, Feb 27, 2019 at 5:12 PM Toshio Kuratomi wrote: > > On Tue, Feb 26, 2019 at 2:07 PM Neil Schemenauer > wrote: > >> On 2019-02-26, Gregory P. Smith wrote: >> > On Tue, Feb 26, 2019 at 9:55 AM Barry Warsaw wrote: >> > For an OS distro provided interpreter, being able to restrict its use

Re: [Python-Dev] Can I get a review for PR 10437?

While more reviewers never hurt, Victor has left at least one comment on the PR. On Thu, Feb 28, 2019 at 7:59 AM Kevin Adler wrote: > This PR has been open for nearly 3 months without any comment. Can I > please get someone to review it? > > PR link: https://github.com/python/cpython/pull/10437

[Python-Dev] Can I get a review for PR 10437?

This PR has been open for nearly 3 months without any comment. Can I please get someone to review it?   PR link: https://github.com/python/cpython/pull/10437 Bug report: https://bugs.python.org/issue35198 ___ Python-Dev mailing list

Re: [Python-Dev] Summary of Python tracker Issues

On Thu, Feb 28, 2019, 8:02 AM INADA Naoki wrote: > No stats for last week? > Been missing for two weeks actually. I did not receive a summary on either the 15th or 22nd. > ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] Summary of Python tracker Issues

No stats for last week? On Sat, Feb 9, 2019 at 3:11 AM Python tracker wrote: > > ACTIVITY SUMMARY (2019-02-01 - 2019-02-08) > Python tracker at https://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond to this message. > > Issues

Re: [Python-Dev] Compact ordered set

On Thu, Feb 28, 2019 at 10:58 PM Antoine Pitrou wrote: > Some of them may be coming from C++, where the respective > characteristics of set and map (or unordered_set and > unordered_multimap) are closely related. I'm sure other languages > show similar analogies. > > On a more abstract level,

Re: [Python-Dev] Compact ordered set

> On 2019-02-28, at 12:56 , Antoine Pitrou wrote: > > On Thu, 28 Feb 2019 22:43:04 +1100 > Steven D'Aprano wrote: >> On Wed, Feb 27, 2019 at 02:15:53PM -0800, Barry Warsaw wrote: >> >>> I’m just relaying a data point. Some Python folks I’ve worked with do >>> make the connection between

Re: [Python-Dev] Compact ordered set

On Thu, 28 Feb 2019 22:43:04 +1100 Steven D'Aprano wrote: > On Wed, Feb 27, 2019 at 02:15:53PM -0800, Barry Warsaw wrote: > > > I’m just relaying a data point. Some Python folks I’ve worked with do > > make the connection between dicts and sets, and have questions about > > the ordering

Re: [Python-Dev] Compact ordered set

On Wed, Feb 27, 2019 at 02:15:53PM -0800, Barry Warsaw wrote: > I’m just relaying a data point. Some Python folks I’ve worked with do > make the connection between dicts and sets, and have questions about > the ordering guarantees of then (and how they relate). Sets and dicts are not related

Re: [Python-Dev] Compact ordered set

On Thu, Feb 28, 2019 at 7:23 AM Henry Chen wrote: > If sets were ordered, then what ought pop() return - first, last, or > nevertheless an arbitrary element? I lean toward arbitrary because in > existing code, set.pop often implies that which particular element is > immaterial. > >

Re: [Python-Dev] datetime.timedelta total_microseconds

> > I *think* this is the "correct" way to do it: > > def timedelta_to_microseconds(td): > return td.microseconds + td.seconds * 1000 + td.days * 8640 > > (hardly tested) > > -CHB > 1000? milli? micro? -- INADA Naoki ___ Python-Dev mailing