The Record.columns attribute is accessible in both 1.6.3 and 1.6.4
identically. Documentation is limited in a few areas, I'll admit, but that
is largely due to a lack of time to work on the project.
I see no such issue with installing py2neo 1.6.3:
$ pip install py2neo==1.6.3
Downloading/unpacking py2neo==1.6.3
Downloading py2neo-1.6.3.tar.gz (216kB): 216kB downloaded
Running setup.py (path:/home/elgin/venv/test/build/py2neo/setup.py)
egg_info for package py2neo
Installing collected packages: py2neo
Running setup.py install for py2neo
building 'py2neo.packages.jsonstream.cjsonstream_2x' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c
py2neo/packages/jsonstream/cjsonstream_2x.c -o
build/temp.linux-x86_64-2.7/py2neo/packages/jsonstream/cjsonstream_2x.o
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro
build/temp.linux-x86_64-2.7/py2neo/packages/jsonstream/cjsonstream_2x.o -o
build/lib.linux-x86_64-2.7/py2neo/packages/jsonstream/cjsonstream_2x.so
changing mode of build/scripts-2.7/neotool from 644 to 755
changing mode of /home/elgin/venv/test/bin/neotool to 755
Successfully installed py2neo
Cleaning up...
I can only assume there must be something non-standard about your
environment.
Nigel
On 22 March 2014 13:46, Alan Robertson <al...@unix.sh> wrote:
> You changed the access to columns - and I didn't see any column
> attribute like there is now. It could be that I missed it before. In any
> case, I'm now using it, and would love it if it would stay around.
>
> But since there is no documentation of this particular data structure, it
> wasn't clear how one was supposed to use it.
>
> Regarding pip: specifying ==1.6.3 does NOT work - it gives me 1.6.4
> anyway. I have no idea why. It knows I wanted 1.6.3, but it said
> "installing 1.6.4 instead" or something like that.
>
>
>
> On 3/22/2014 5:04 AM, Nigel Small wrote:
>
> Hi Alan
>
> I'm unclear as to how your code might be broken based on the 1.6.4
> release. In terms of query results, there were some internal optimisations
> that were carried out to improve performance but nothing should have
> changed in the public API. If you can be clearer on what you perceive has
> changed, I can either clarify correct usage or add a bug to be fixed.
>
> Version 1.6.3 has not been removed either, as per standard pip usage,
> you can install that specific version by using:
>
> pip install py2neo==1.6.3
>
> Nigel
>
>
> On 21 March 2014 22:32, Alan Robertson <al...@unix.sh> wrote:
>
>> Hi Nigel,
>>
>> When you return query results, you've had 3 different versions of how to
>> introspect the column names of the resulting data (1.6.4 being the
>> latest one).
>>
>> Could you *please* create a consistent method for me to use to extract
>> the column names and then keep that working on your new versions?
>> [Having it be an object method would be awesome].
>>
>> I really need to know the column names so I can create corresponding
>> columns with Python objects of the same names as the Neo4j objects you
>> deliver to me.
>>
>> If you could do this, it would be very helpful for me, and would
>> eliminate the last two reasons I got extremely frustrated with py2neo.
>>
>> Of course, this is made more frustrating by the fact that 1.6.3 is not
>> longer available.
>>
>> If you feel the need to break APIs, it would be good to allow the old
>> version to stay around for those who haven't converted to the new
>> version yet.
>>
>>
>> --
>> Alan Robertson <al...@unix.sh> <al...@unix.sh> - @OSSAlanR
>>
>> "Openness is the foundation and preservative of friendship... Let me
>> claim from you at all times your undisguised opinions." - William
>> Wilberforce
>>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
