I prefer Proposal 2 out of the list, and regarding Russell's point I
believe that the tutorial ought to promote Python 3 and be written from
that perspective with Python 2 exceptions - because exactly of Django's
importance in the Python landscape.
Thanks and good day.
On 09/08/2012 19:35, R
On Fri, Aug 10, 2012 at 4:58 AM, charettes wrote:
> I think this will only be an issue for django application maintainers.
>
> IMHO, projects target a specific version of python and won't have to provide
> python 2-3 compatibility. Am I wrong?
Yes and no.
On the one hand -- yes. Jo(sephin)e Publ
On Thu, Aug 9, 2012 at 2:42 PM, Flavio Curella wrote:
> From the benchmark, my understanding is that, on PostGIS 2.0:
>
> 1) for the 2D case, the best index is 'gist (columname)'
> 2) for the 3D case, the best index is 'gist (columname
> gist_geometry_ops_nd)' only when using specific 3D operators
Sorry, please ignore that last message, I see now that you
were referring to this:
https://docs.djangoproject.com/en/dev/ref/databases/#autocommit-mode
So essentially, the official documentation would state that to resolve this
problem, you would use the following for your db settings:
'OPTIONS'
Thanks for the detailed explanation on this.
Am I correct in assuming you are referring to the following decorator as
being the fix for the problem?
@transaction.autocommit
def viewfunc(request):
pass
On Thu, Aug 9, 2012 at 3:55 AM, Karen Tracey wrote:
> On Wed, Aug 8, 2012 at 9:25 AM, Ca
>From the benchmark, my understanding is that, on PostGIS 2.0:
1) for the 2D case, the best index is 'gist (columname)'
2) for the 3D case, the best index is 'gist (columname gist_geometry_ops_nd)'
only when using specific 3D operators (ie: '&&&')
I think we should create the index for 2D case,
I was running the wrong query for the 3D case.
I've updated the benchmark gist and added some test under PostGIS 1.5.
On Thursday, August 9, 2012 4:03:45 PM UTC-5, Anssi Kääriäinen wrote:
>
> On 9 elo, 23:48, Jeremy Dunck wrote:
> > I'm fairly familiar with the django gis code, but I haven't bee
On 9 elo, 23:48, Jeremy Dunck wrote:
> I'm fairly familiar with the django gis code, but I haven't been
> following postgis 2.0. Could you point me towards some discussion of
> the index changes from 1.5 to 2.0? On the face of it, I'm doubtful
> that they've removed a useful form of indexing wit
The informations I've found on the 'net were quite old, so I did a quick
benchmark.
https://gist.github.com/3307966
TL;DR: index is better than no index or the 'gist_geometry_ops_nd' index
On Thursday, August 9, 2012 3:48:47 PM UTC-5, jdunck wrote:
>
> I'm fairly familiar with the django gis co
I think this will only be an issue for django application maintainers.
IMHO, projects target a specific version of python and won't have to
provide python 2-3 compatibility. Am I wrong?
Le jeudi 9 août 2012 16:36:12 UTC-4, Aymeric Augustin a écrit :
>
> Hello,
>
> One of the first lessons in th
I'm fairly familiar with the django gis code, but I haven't been
following postgis 2.0. Could you point me towards some discussion of
the index changes from 1.5 to 2.0? On the face of it, I'm doubtful
that they've removed a useful form of indexing with no
replacement/alternative.
It's hard for m
Hello,
One of the first lessons in the tutorial is to define a __unicode__ method. In
Python 3, __unicode__ is replaced by __str__ (and __str__ by __bytes__, but
that method won't be needed in general).
Writing these methods in a way works on both Python 2 and 3 proves surprisingly
messy. I'd
Coming back to this: I think making the pre/post sync signals usable
for this seems like a good enough approach until migrations framework
gives us a cleaner way for this.
The problem is easiest to see in a custom HSTORE field. There is need
to issue a "create extension hstore" before any model is
On 8 elo, 18:12, Flavio Curella wrote:
> Hi,
>
> I've made some work onhttps://code.djangoproject.com/ticket/16455and I
> think I'm close to have it ready for checking.
>
> Can I have a quick review from the committers? I'm mostly interested in
> feedback about:
>
> * the v8 patch installs multidi
14 matches
Mail list logo
