James Bennett wrote:
> On 3/29/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>> I can't think of a way to account for "up to last 3 years" and "up to
>> the next 5 years" or variation thereof.
>
> paid_up_until = models.DateField()
>
> Then use Python's standard 'datetime.timedelta' to handle
On 30 Mar 2007, at 9:21 am, David Reynolds wrote:
>
> One of the things that annoys me about datetime is that it doesn't
> handle leap years properly. However, if you use python-dateutil[1] it
> has a relativedelta so you can do things like:
>
datetime.date.today()+relativedelta(years=+3)
On 30 Mar 2007, at 2:32 am, James Bennett wrote:
>
> On 3/29/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>> I can't think of a way to account for "up to last 3 years" and "up to
>> the next 5 years" or variation thereof.
>
> paid_up_until = models.DateField()
>
> Then use Python's standard
On 3/29/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
> I can't think of a way to account for "up to last 3 years" and "up to
> the next 5 years" or variation thereof.
paid_up_until = models.DateField()
Then use Python's standard 'datetime.timedelta' to handle offets;
e.g., if a member pays up for
I'm trying to think how I can solve this problem in my data model and
I'm coming up empty. I thought I'd post it here to see if anyone else
had a good idea...
I built a members-only website for due paying members. We'd like to use
the profile via the Django admin as a way to track which
5 matches
Mail list logo
