Django 1.6 :sadface:

[daniel]

We received an issue a couple days ago (https://github.com/toastdriven/django-haystack/issues/805) that raises a severe Django 1.6 issue. Django itself has changed how ``Node`` works (https://github.com/django/django/commit/d3f00bd5706b35961390d3814dd7e322ead3a9a3). Unfortunately, I'm swamped ATM & it's doubtful I'll be able to address it in the near future. Does anyone else have time to tackle it?

As I see it, we can introduce a short-term fix by just manually copying over the old methods in Django onto the ``SearchNode`` class & making sure the existing tests in ``django-haystack/tests/core`` pass. Longer-term, we should probably properly alter it to keep inline with Django & to simplify things. Help?


Daniel

[George Hickman]

I might be able to help with this as I'm running another Refresh Oxford (http://refreshoxford.co.uk) Hack Day next Saturday (22nd June). </shameless-plug>

So hopefully I can either cajoule some other hackers into helping me or at least get the tests passing with the short term solution. If anyone is interested in combing efforts on this please feel free to email me or grab me on IRC (ghickman on freenode).

George

--
You received this message because you are subscribed to the Google Groups "Haystack Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-haystack...@googlegroups.com.
To post to this group, send email to django-ha...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-haystack-dev.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Dan Watson]

Has any progress been made on this? With the Django 1.6 beta 1 announcement today, I'd like to get this nailed down. I don't mind tackling it, I just want to make sure I won't be duplicating anyone's effort.

Regards,

Dan

On Sunday, June 16, 2013 6:58:49 AM UTC-4, george wrote:

I might be able to help with this as I'm running another Refresh Oxford (http://refreshoxford.co.uk) Hack Day next Saturday (22nd June). </shameless-plug>

So hopefully I can either cajoule some other hackers into helping me or at least get the tests passing with the short term solution. If anyone is interested in combing efforts on this please feel free to email me or grab me on IRC (ghickman on freenode).

George

On 15 June 2013 at 01:13:30, daniel (dan...@toastdriven.com) wrote:

We received an issue a couple days ago (https://github.com/toastdriven/django-haystack/issues/805) that raises a severe Django 1.6 issue. Django itself has changed how ``Node`` works (https://github.com/django/django/commit/d3f00bd5706b35961390d3814dd7e322ead3a9a3). Unfortunately, I'm swamped ATM & it's doubtful I'll be able to address it in the near future. Does anyone else have time to tackle it?

As I see it, we can introduce a short-term fix by just manually copying over the old methods in Django onto the ``SearchNode`` class & making sure the existing tests in ``django-haystack/tests/core`` pass. Longer-term, we should probably properly alter it to keep inline with Django & to simplify things. Help?


Daniel

--
You received this message because you are subscribed to the Google Groups "Haystack Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to django-haystack-dev+unsub...@googlegroups.com.

[Daniel Lindsley]

Dan,

   I'm working on it. I have most of Haystack ported to Py3 & will just work in the needed changes as part of it.

Daniel

To unsubscribe from this group and stop receiving emails from it, send an email to django-haystack...@googlegroups.com.