Re: first() and last(), earliest() and latest()

Hi everyone, I opened a new pull request implementing Shai's suggestions (I didn't overwrite the current branch so we can still compare the two implementations if needed). I initially modeled "first()" and "last()"'s behaviors to mimic "latest()", but in this new pull request, you can pass

Re: reconsider re-opening ticket 901

On 12 touko, 02:55, Russell Keith-Magee wrote: > To that end - I want to make sure that we're clear about what we're talking > about here. > > What is on the table is essentially adding a refresh() call on an object > instance that is an API analog of ".get(id=self.id)"

Re: reconsider re-opening ticket 901

On Sat, May 11, 2013 at 7:55 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > I'm sure I understand this argument. Python objects are passed around by > reference, not by value, so if you've passed in a Django object deep into > another library, that library will be pointing at the

Re: reconsider re-opening ticket 901

On 12 May 2013, at 00:55, Russell Keith-Magee wrote: > I'm sure I understand this argument. Python objects are passed around by > reference, not by value, so if you've passed in a Django object deep into > another library, that library will be pointing at the same

Re: Perception of attitude in tickets

On Sat, May 11, 2013 at 3:47 PM, Wim Feijen wrote: > Hi Simon, Luke and Aymeric, > > Simon, first of all, thanks for your feedback. > > Core developers, I think Simons comment is a thing we should take > seriously. A ticket was closed and people didn't understand the process

Re: reconsider re-opening ticket 901

On Sat, May 11, 2013 at 4:03 PM, Wim Feijen wrote: > Hi, > > Following up on the discussion on: > > https://groups.google.com/forum/?fromgroups=#!topic/django-developers/DUQtBrM2iTs > > I'd like to start a clear discussion about re-opening ticket 901. >

Re: Triaging: Close as needsinfo

On Sunday 12 May 2013, Łukasz Rekucki wrote: > Hi, > > On 11 May 2013 22:58, Shai Berger wrote: > > In > > other communities, I have usually seen "needsinfo" as a ticket state, > > rather > > than a reason for closing; such tickets are then closed later, if enough > > time > >

Re: reconsider re-opening ticket 901

[resend, reference included; sorrt for the noise] On Saturday 11 May 2013, Anssi Kääriäinen wrote: > > - While it might seem trivial to implement reload()/refresh() when > needed, Indeed, it might; which is why I would assume many people have already done it. For these people, a new

Re: reconsider re-opening ticket 901

On Saturday 11 May 2013, Anssi Kääriäinen wrote: > > - While it might seem trivial to implement reload()/refresh() when > needed, Indeed, it might; which is why I would assume many people have already done it. For these people, a new reload()/refresh() in core may go unnoticed or redundantly

Re: Triaging: Close as needsinfo

Hi, On 11 May 2013 22:58, Shai Berger wrote: > In > other communities, I have usually seen "needsinfo" as a ticket state, > rather > than a reason for closing; such tickets are then closed later, if enough > time > has passed and no further info is received. > To me that's

Re: first() and last(), earliest() and latest()

Hi Selwin, On Saturday 11 May 2013, Selwin Ong wrote: > Hi everyone, > > I submitted a pull request implementing "first()" and "last()" here: > https://github.com/django/django/pull/1054 > > Comments welcome! > You implemented the "order_by" parameter as taking only one field name; this is

Triaging: Close as needsinfo

Hi Django devs, I would like to raise a little concern I ran into lately. When going over some Oracle-related tickets, I came across ticket #20201[0] . The ticket description was missing important details, so I commented about them. A few days later, Aymeric came around, and closed the ticket

Re: BCrypt + Python3

On May 11, 2013, at 4:10 AM, Claude Paroz wrote: > Le samedi 11 mai 2013 07:59:18 UTC+2, Donald Stufft a écrit : > I went looking for BCrypt + Django + Python3 today and this is what I found: > > The current recommended solution to bcrypt + Django is using py-bcrypt which

Re: test discovery

On Saturday, May 11, 2013 2:38:23 PM UTC+2, Carl Meyer wrote: > > No good reason, just an oversight I think. If that's all that's needed to > make the CI happy, feel free to change it, should be a simple fix. > Perfect, pushed a fix, let's see what jenkins says. -- You received this message

Re: test discovery

Hi Florian, On May 11, 2013, at 7:51 AM, Florian Apolloner wrote: > Hi Carl, > > before I read all the tickets etc; why does runtests.py not use the > TEST_RUNNER from settings.py (see >

Re: test discovery

Hi Carl, before I read all the tickets etc; why does runtests.py not use the TEST_RUNNER from settings.py (see https://github.com/django/django/commit/9012833af857e081b515ce760685b157638efcef#L60L149)? We'd need that for jenkins to produce xml files as output. Thanks, Florian -- You

Re: first() and last(), earliest() and latest()

Hi everyone, I submitted a pull request implementing "first()" and "last()" here: https://github.com/django/django/pull/1054 Comments welcome! Best, Selwin On Thursday, February 28, 2013 5:34:16 AM UTC+7, Wim Feijen wrote: > > Hi all, > > We struggled to get a proper definition for a first()

Re: test discovery

Not good, at least our Jenkins runner which should generate xml output doesn't like it :/ On Saturday, May 11, 2013 5:36:55 AM UTC+2, Carl Meyer wrote: > > I merged this patch tonight. Thanks to everyone who contributed! Now let's > see how the CI servers feel about it... > > Carl > > On

Re: reconsider re-opening ticket 901

On 11 touko, 11:03, Wim Feijen wrote: > Hi, > > Following up on the discussion > on:https://groups.google.com/forum/?fromgroups=#!topic/django-developers... > > I'd like to start a clear discussion about re-opening ticket > 901.https://code.djangoproject.com/ticket/901 > >

reconsider re-opening ticket 901

Hi, Following up on the discussion on: https://groups.google.com/forum/?fromgroups=#!topic/django-developers/DUQtBrM2iTs I'd like to start a clear discussion about re-opening ticket 901. https://code.djangoproject.com/ticket/901 Ticket 901 was marked 7 years ago as won't fix and has been

Re: Perception of attitude in tickets

Hi Simon, Luke and Aymeric, Simon, first of all, thanks for your feedback. Core developers, I think Simons comment is a thing we should take seriously. A ticket was closed and people didn't understand the process and re-opened it. I believe we could have explained more clearly: 1. our