On Sun, Jul 1, 2018 at 7:12 PM, David Mertz wrote:
> Michael changed from set to list at my urging. A list is more general. A
> groupby in Pandas or SQL does not enforce uniqueness, but DOES preserve
> order.
>
It really is better to construct the collection using lists—in the fully
general ma
On Sun, Jul 1, 2018 at 7:28 PM, David Mertz wrote:
> But it's pretty simple. Whether my idea of collections.Grouping is adapted
> or whether a function/classmethod grouping() produces a plain dictionary,
>
or my custom class...
> the casting would be the same:
>
> {k:set(v) for k,v in deps.ite
Oh, it looks like he has modified the PEP and taken out the examples of
conversion. That's too bad, hopefully they'll be added back.
But it's pretty simple. Whether my idea of collections.Grouping is adapted
or whether a function/classmethod grouping() produces a plain dictionary,
the casting woul
Michael changed from set to list at my urging. A list is more general. A
groupby in Pandas or SQL does not enforce uniqueness, but DOES preserve
order. I think the PEP is not fully updated, but it's a list everywhere in
the proposal itself, just not in the "old techniques."
Moreover, Michael give
Ivan,
Did you mean this to go to the list? I hope so, as I've cc-d it this time
:-)
On Sun, Jul 1, 2018 at 1:20 AM, Ivan Levkivskyi
wrote:
> On 1 July 2018 at 06:18, Chris Barker via Python-ideas <
> python-ideas@python.org> wrote:
>
>> I'm really warming to the:
>>
>> Alternate: collections.Gr
On 1 July 2018 at 20:47, Ethan Furman wrote:
> On 07/01/2018 06:03 AM, Ivan Levkivskyi wrote:> On 27 June 2018 at 15:46,
> Ethan Furman wrote:
>
> [...]
>>> So I'm asking the community: What real-world examples can you offer for
>>> either behavior? Cases where nested
>>> classes should be enum
> -Original Message-
> From: Python-ideas list=sdamon@python.org> On Behalf Of Nick Timkovich
> Sent: Sunday, July 1, 2018 12:02 PM
> To: Matt Arcidy
> Cc: python-ideas
> Subject: Re: [Python-ideas] Add a __cite__ method for scientific packages
>
> From an abstract level, however,
On 07/01/2018 06:03 AM, Ivan Levkivskyi wrote:> On 27 June 2018 at 15:46, Ethan
Furman wrote:
[...]
So I'm asking the community: What real-world examples can you offer for either
behavior? Cases where nested
classes should be enum members, and cases where nested classes should not be
member
On Fri, Jun 29, 2018 at 8:58 PM, Matt Arcidy wrote:
> It seems like the very small percentage of academic users whose careers
> depend on this cannot resolve the political issue of forming a standards
> body.
>
> I don't see how externalizing the standard development will help. Kudos
> for short
I think a __citation__ *method* is a bad idea. This yells out "attribute"
to me. A function or two that parses those attributes in some manner is a
better idea... And there's no reason that function or two need to be
dunders. There's also no reason they need to be in the standard library...
There m
Replying to the list this time.
On 27 June 2018 at 15:46, Ethan Furman wrote:
> [...]
> So I'm asking the community: What real-world examples can you offer for
> either behavior? Cases where nested classes should be enum members, and
> cases where nested classes should not be members.
>
I wan
On 28 June 2018 at 01:19, Nathaniel Smith wrote:
> On Wed, Jun 27, 2018 at 2:20 PM, Andrei Kucharavy
> wrote:
> > To remediate to that situation, I suggest a __citation__ method
> associated
> > to each package installation and import. Called from the __main__,
> > __citation__() would scan __ci
12 matches
Mail list logo
