TropicalPenguin

Thanks @obi1kenobi. I notice this is resolved in the `develop` branch. @Ostico I think we're reaching a point where releasing 1.5.6 makes sense (after making a decision about https://github.com/mogui/pyorient/pull/249, since...

I see. in_ and out were added as members of pyorient.ogm.edge.Edge, to enable building queries against the values of properties on an edge's in-vertex and out-vertex. I think this was...

Hm...maybe those members could be removed from the instance object.

Hi @obi1kenobi I took a look and I'm not totally clear how you're getting that problem. If there is a schema property with that name, it shouldn't be shadowed by...

Whew, it's been a while. Have needed to rekindle my memory of these interfaces. I suggest avoiding instantiating Query directly. Usage is a lot simpler through the graph, or what...

Yo, in some recent develop branch commits, I've added various container methods to OrientRecord. Left out the various ordering operations suggested across python 2/3 ... not convinced there's meaningful ordering...

There are two issues here: 1. Round-trip of Python date(time) objects 2. String-encoded date(time)s The CSV serializer can handle round-trips of date(time) objects, so long as encode and decode assume...

@nikulukani `datetime.date.today()` is not sufficient for testing round trips, since it doesn't include time.

This is with CSV serialization. Can trigger it pretty directly by adding: ``` import pdb; pdb.set_trace() g.client.command('SELECT $stack FROM (TRAVERSE in(\'on_top_of\') FROM {}) WHERE $depth > 0'.format(traversals[0]._id)) ``` towards the...

Should be fixed in `develop` branch.