[Python-Dev] namedtuples bug between 3.3.2 and 3.4.1 (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Sun Sep 14 18:27:35 CEST 2014
- Previous message: [Python-Dev] namedtuples bug between 3.3.2 and 3.4.1
- Next message: [Python-Dev] namedtuples bug between 3.3.2 and 3.4.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 15 Sep 2014 02:13:53 +1000 Chris Angelico <rosuav at gmail.com> wrote:
On Sun, Sep 14, 2014 at 8:13 PM, Brynjar Smári Bjarnason <binni at binnisb.com> wrote: > I am using Python 3.4.1 installed with Anaconda. I tried the following > (expecting an OrderedDict as result): > >>>>from collections import namedtuple >>>>NT = namedtuple("NT",["a","b"]) >>>>nt = NT(1,2) >>>>print(vars(nt)) > {} > > so the result is an empty dict. In Python 3.3.2 (downgraded in the > same Anaconda environment) results in: > >>>>print(vars(nt)) > OrderedDict([('a', 1), ('b', 2)])
For what it's worth, I can't reproduce the issue on trunk CPython (built from default branch on Aug 21, so it's a little old now), nor on 3.4.1 as currently shipping with Debian Jessie, nor with 3.4.0 on Windows. So this may be an Anaconda issue. Do you know if it's meant to be a patched install of Python?
There may be a couple distutils-specific patches, but that's all. Anaconda issues should be reported at https://github.com/ContinuumIO/anaconda-issues/issues/
Regards
Antoine.
- Previous message: [Python-Dev] namedtuples bug between 3.3.2 and 3.4.1
- Next message: [Python-Dev] namedtuples bug between 3.3.2 and 3.4.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]