> On 04 Jun 2016, at 00:55, Philip James wrote:
>
> If it's required, should it be vendors?
That doesn’t sound optimal because pytz’ release cycle is tied to the TZ
database’s cycle, which is different from Django’s.
--
Aymeric.
--
You received this message because you are subscribed to the
> On Jun 4, 2016, at 1:18 PM, Aymeric Augustin
> wrote:
>
> That doesn’t sound optimal because pytz’ release cycle is tied to the TZ
> database’s cycle, which is different from Django’s.
IMO just stick pytz in install_requires and be done with it. It’s a very
trivial dependency, and is avai
On 06/03/2016 03:55 PM, Philip James wrote:
> Is there consensus on making pytz required? (I, personally, am in favor,
> since I too can't remember the last project I did that didn't need it.)
>
> If it's required, should it be vendored?
-1 on vendoring pytz. I think it's fine to just make it a r
Adding pytz to install_requires might not contribute to a bug fix or new
feature right now, but it does remove a point of confusion from the docs. I
think it also reduces friction in getting Django up-and-running, which
seems valuable for Django users and Django contributors.
PJJ
http://philipjohn
I just realized that I think something's gotten lost in this thread:
Josh's original point was about requiring pytz _if you want timezone
support_ (that is, if USE_TZ=True). That would I presume involve raising
ImproperlyConfigured (or maybe having a site check raise an error?) if
USE_TZ=True and p
On 06/04/2016 12:38 PM, Carl Meyer wrote:
> I just realized that I think something's gotten lost in this thread:
> Josh's original point was about requiring pytz _if you want timezone
> support_ (that is, if USE_TZ=True). That would I presume involve raising
> ImproperlyConfigured (or maybe having
Details are available on the Django project weblog:
https://www.djangoproject.com/weblog/2016/jun/04/bugfix-release/
--
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
On Saturday, August 8, 2015 at 2:53:32 PM UTC-7, Aymeric Augustin wrote:
>
> Hello,
>
> While writing some horrific code [1] related to the development server’s
> auto-reloading, I realized that its design is fundamentally flawed and I
> think that we should reconsider it.
>
> The current imple
Triaged
---
https://code.djangoproject.com/ticket/26680 - more than one row returned by
a subquery used as an expression (duplicate)
https://code.djangoproject.com/ticket/23518 - Subquery does not respect
explicit __exact (fixed)
https://code.djangoproject.com/ticket/26681 - save_as=Tru
