On Wed, Oct 30, 2019 at 11:55 PM Oz Tiram wrote:
>
> Hi Steve,
>
> Thanks for your reply. While dataclass provide a cleaner API than DictRow
> (you can access `row.id` instead of `row["id"]`).
> However, dataclass still use the built in `__dict__` instead of `__slots__`.
>
> This means that the
Due to awkward CDN caching, some users who downloaded the source code
tarballs of Python 3.5.8 got a preliminary version instead of the final
version. As best as we can tell, this only affects the .xz release;
there are no known instances of users downloading an incorrect version
of the .tgz
On Thu., 31 Oct. 2019, 8:30 am Brett Cannon, wrote:
> Barry Warsaw wrote:
> > On Oct 30, 2019, at 14:31, Łukasz Langa luk...@langa.pl
> > wrote:
> > > Yes. This allows for synchronizing the schedule of
> > > Python release management with Fedora. They've been historically very
> helpful in early
On Thu., 31 Oct. 2019, 6:14 am Steve Dower, wrote:
>
> Also, PEP 602 makes no statement about when stable ABI APIs are
> "committed", and nor does PEP 384, so should we assume that the stable
> ABI becomes fixed at beta 1 (or RC 1)? That is, it is not allowed to
> remove or change any stable ABI
Barry Warsaw wrote:
> On Oct 30, 2019, at 14:31, Łukasz Langa luk...@langa.pl
> wrote:
> > Yes. This allows for synchronizing the schedule of
> > Python release management with Fedora. They've been historically very
> > helpful in early
> > finding regressions not only in core Python but also in t
On Oct 30, 2019, at 14:31, Łukasz Langa wrote:
>
> Yes. This allows for synchronizing the schedule of Python release management
> with Fedora. They've been historically very helpful in early finding
> regressions not only in core Python but also in third-party libraries,
> helping moving the c
On 29Oct2019 21:37, Oz Tiram wrote:
Quite a few tutorials show how to use namedtuple to gain memory saving
and speed, over the DictReader.
[...]
Python's own documentation has got a recipe in the collections modules[1]
Hence, I was wondering why not go the extra step and add a new class to the
> On 30 Oct 2019, at 20:26, Brett Cannon wrote:
>
> On behalf of the steering council I am happy to announce that as
> BDFL-Delegate I am accepting PEP 602 to move us to an annual release schedule
> (gated on a planned update; see below).
Thank you, I'm excited!
Nit:
> * 3 months for betas
On Oct 30, 2019, at 12:50, Matthias Klose wrote:
>
> On 30.10.19 20:26, Brett Cannon wrote:
>> This was discussed on https://discuss.python.org
>
> I appreciate that you are informing the python-dev ML. However this
> discussion was never announced on the ML. I assume this is a kind of thing
Steve Dower wrote:
> On 30Oct2019 1226, Brett Cannon wrote:
> >
> > Now that the stable ABI has been cleaned, extension modules should feel more
> > comfortable targeting the stable ABI which should make supporting newer
> > versions of Python
> > much easier
> >
> > I'm taking this as an indica
This PEP was mentioned on python-dev at least at
https://mail.python.org/archives/list/python-dev@python.org/message/WQ64ZGBECFDIRO6DS7JN3NALYDJGPAAE/
and
https://mail.python.org/archives/list/python-dev@python.org/message/YVSOOFLCBHPIA3HBL4L2BFBJENVHZDJC/.
This was also covered by the PEP 596
On 30Oct2019 1226, Brett Cannon wrote:
* Now that the stable ABI has been cleaned, extension modules should feel more
comfortable targeting the stable ABI which should make supporting newer
versions of Python much easier
I'm taking this as an indication that we should finish
https://bugs.pyt
On 30.10.19 20:26, Brett Cannon wrote:
This was discussed on https://discuss.python.org
I appreciate that you are informing the python-dev ML. However this discussion
was never announced on the ML. I assume this is a kind of thing that makes the
ML obsolete and forces everyone into discourse
On behalf of the steering council I am happy to announce that as BDFL-Delegate
I am accepting PEP 602 to move us to an annual release schedule (gated on a
planned update; see below).
The steering council thinks that having a consistent schedule every year when
we hit beta, RC, and final it will
Hi Serhiy,
Thanks! Now, I am feeling confused. On the one hand, it's already been
tried 10 years ago. On the other hand, obviously people do wish to have it.
I'm going to send a PR In GitHub. Let's see if a new PR with some
documentation can be appreciated.
Oz
On Wed, Oct 30, 2019, 16:25 Serhiy S
On 10/30/2019 02:53 AM, Steve Holden wrote:
If using a dictionary but still requiring attribute access, techniques such as
those used at https://github.com/holdenweb/hw can be used to simply client code.
Unless I'm missing something, that doesn't have the memory improvement that
namedtuples
29.10.19 22:37, Oz Tiram пише:
Quite a few tutorials show how to use namedtuple to gain memory saving
and speed, over the DictReader.
Python's own documentation has got a recipe in the collections modules[1]
Hence, I was wondering why not go the extra step and add a new class to
the CSV module
On Wed, Oct 30, 2019, 09:43 Steve Holden wrote:
> Since 3.7 it may be that dataclasses offer a cleaner implementation of the
> functionality you suggest.
>
Actually, IMO in this case it would be more useful and fitting to use
namedtuples rather than dataclasses, since CSV rows are naturally
tuple
Hi Steve,
Thanks for your reply. While dataclass provide a cleaner API than DictRow
(you can access `row.id` instead of `row["id"]`).
However, dataclass still use the built in `__dict__` instead of
`__slots__`.
```
>>> @dataclass
... class InventoryItem:
... '''Class for keeping track of an i
If using a dictionary but still requiring attribute access, techniques such
as those used at https://github.com/holdenweb/hw can be used to simply
client code.
Kind regards,
Steve Holden
On Wed, Oct 30, 2019 at 11:15 AM Oz Tiram wrote:
> Hi Steve,
>
> Thanks for your reply. While dataclass pro
Since 3.7 it may be that dataclasses offer a cleaner implementation of the
functionality you suggest. It shouldn't be too difficult to produce code
that uses dataclasses in 3.7+ but falls back to namedtuples when necessary.
You may wish to consider such an implementation strategy.
Best wishes,
Ste
21 matches
Mail list logo
