I agree that we need a replacement; the current behaviour isn't all that
useful, IMHO. My vote would for choice #2, after all it seems more natural
(to me, at least), to think of numbers as a range, especially while
searching. Option 1 seems less intuitive for a situation like this.
+1 from me, es
Hi Sjoerd,
I too would love to see this feature in Django 2.0; in fact, I've been
following its progress quite closely. I would love to help out with it and
have the necessary time to do so.
John Griebel | Senior Backend Engineer | 3Blades.io | 814-227-4213
On Thu, Jul 27, 2017 at 5:
ironment set
up.
On Jul 29, 2017 4:49 AM, "Emil Stenström" wrote:
John: Awesome! Do you need anything to get started or is Sjoerd's review
comments and todolist enough?
On Friday, 28 July 2017 15:03:12 UTC+2, John Griebel wrote:
> Hi Sjoerd,
> I too would love to see this
precated immediately?
7.) view_tests - I see Sjoerd already made some small changes here and
wanted to confirm that the rest of the URL conf was not left unconverted
intentionally before converting them myself.
Feedback on 6 and 7, in particular, would be great.
Thanks,
John Griebel | Senior Bac
im's PR is pretty
complete.
Thanks,
John Griebel | Senior Backend Engineer | 3Blades.io | 814-227-4213
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop recei