On Wednesday, October 4, 2017 at 1:29:58 AM UTC+2, Stephen McDonald wrote:
>
>
>
> On Wed, Oct 4, 2017 at 8:39 AM, > wrote:
>
>> Hi there,
>>
>> is there a rough estimate for when the next version will be released with
>> Django 1.11 support ?
>>
>
> There is no rough estimate
>
>
I would love
On Wed, Oct 4, 2017 at 8:39 AM, wrote:
> Hi there,
>
> is there a rough estimate for when the next version will be released with
> Django 1.11 support ?
>
There is no rough estimate
> I would love to use Mezzanine on my project but I'm using Django 1.11 and
> I wouldn't know how to use the git
One hint for the createdb error with Django 1.8 :
https://docs.djangoproject.com/en/1.8/howto/custom-management-commands/#django.core.management.NoArgsCommand
-> the error is caused by the fact that the options dictionnary passed to
the handle_noargs method does not include a 'database': 'default
Absolutely, I totally forgot to mention that.
On Sun, Apr 5, 2015 at 3:16 PM, Graham wrote:
> ok
> How about Python versions?
> 2.7.9 and 3.4.3
> Does that sound right?
> g
>
>
> On 05/04/15 17:08, Stephen McDonald wrote:
>
> Thanks Graham - I guess it mostly involves working with a virtualenv
ok
How about Python versions?
2.7.9 and 3.4.3
Does that sound right?
g
On 05/04/15 17:08, Stephen McDonald wrote:
Thanks Graham - I guess it mostly involves working with a virtualenv
for each Django version, as well as using pip in each of those to
install Mezzanine directly from Github or BitB
Thanks Graham - I guess it mostly involves working with a virtualenv for
each Django version, as well as using pip in each of those to install
Mezzanine directly from Github or BitBucket. There's probably a ton of info
online that better describes how to do that.
With that in place, next step is t
Hi Stephen
When you say
'Again, could *really* use help in testing the current dev branch
against Django 1.7 and 1.8'
Is there anything I can look at to know how to do this?
TIA
Graham
On 05/04/15 16:59, Stephen McDonald wrote:
Just a status update on the next release.
I've just removed all s
Just a status update on the next release.
I've just removed all support for South and Django 1.6 and earlier. Please
help me with a review and fixing anything I may have overlooked:
https://github.com/stephenmcd/mezzanine/commit/955488361b17959df80ae64e2cb9a2830d7f4540
https://github.com/stephenm
Indeed, thank you to all involved. I've also been watching, a bit
anxiously, for a 1.7 based release. Now 1.8. Kind of hate to do much work
on current site when big changes are coming. :)
I probably should jump in and see if I could help with fixing anything. I'm
sure it would teach me a lot. (
> I hope this doesn't sound like a criticism of Django, they can't know
what they're breaking if no one tells them.
yep, it's hard to question a lot of things about other libre/open source
projects without seeming ungrateful.
i'm a libre software developer myself so i'm keenly aware of all the
I thing could be maiking 3.1.x series LTS and Having a 3.2 release after
1.8 release and other work arrounds. like wagtail-cms team is doing.
enjoy the vacation!
Thank you for all your effort behind mezzanine.
Kind regards
On Wed, Mar 25, 2015 at 8:47 AM, Stephen McDonald wrote:
> Apologies f
Apologies for the delay, I'm currently on vacation overseas with my wife
and children over the next month.
On Tue, Mar 24, 2015 at 10:06 AM, elguavas wrote:
> given that django 1.8 will be released soon, how are things going for a
> new pip installable release of mezzanine that supports django
12 matches
Mail list logo
