Hi everyone,
We're working on upgrading our product from Django 1.6 to 1.8, and one of
the biggest tasks is moving from Django Evolution to Django's migrations.
Please correct me if I'm missing something, but from my testing and
investigation into the code, it seems that the migrate command wil
fice as opposed to needing a build environment and
source to install it.
It's starting to sound like the best bet for us is to move away from
pip/easy_install for end-user consumption of the software and onto more of
a dedicated installer that can manage dependencies more explicitly, maybe
t
On Wed, Aug 19, 2015 at 4:43 PM, Markus Holtermann wrote:
> Hey Christian,
>
> On Wed, Aug 19, 2015 at 02:41:49PM -0700, Christian Hammond wrote:
>
>> Regarding the version number, from what I've read, there's still a
>> reported
>> compatibility issue
s, though, we sign all the builds and
include checksums in both the links and in dedicated .sha256sum files. Not
the best solution, but it's something at least :/
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.bea
Hi Carl,
I know it's been a while since we discussed this, but today's security
release is the first one that's really affecting our product and we've
finally got things in shape to be able to start distributing unofficial
Django security releases (we've also just been swamped since our discuss
Hi Carl, James,
Sorry for the late reply on this. I've been unavailable the past week.
I know you guys are still sorting out how you want to run this, but I
wanted to let you know that, given our current dependence on Python 2.6,
I'm willing to do what's needed to maintain security backports fo
On Dec 14, 12:02 am, Julien Phalip wrote:
> On Dec 13, 10:16 am, Tai Lee wrote:
>
> -snip-
>
> > One suggestion from #1105 was to split out this functionality into
> > individual decorators, @takes_context, @takes_block. I'm not sure how
> > easy this would be technically to implement, but I thin
