[mezzanine-users] Re: new release?

[Graham Oliver]

I raised this issue 
https://groups.google.com/d/msg/mezzanine-users/_QWfFVB3RVc/kar0ykEMZzgJ
In terms of a new release I am not sure of its impact (if any).
g

On Friday, 5 June 2015 13:00:19 UTC+12, elguavas wrote:
>
> bump ;)  i just looked in the issue tracker under "release blockers" and i 
> said there were zero.
>
> On Tuesday, March 24, 2015 at 10:06:32 AM UTC+11, 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 1.7?
>>
>> i'm also very interested in the new fabfile stuff for shared host 
>> installs.
>>
>> i'm also wondering, with mezz almost missing a whole django version 
>> without a pip installable release, are things on the mezz release front 
>> likely to continue to be very slow in staying up to date with changes in 
>> mezz git? 
>>
>> not intending to be critical, not at all, just looking for an honest 
>> assessment of how the project is faring with respect to official releases. 
>> cheers.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[elguavas]

bump ;)  i just looked in the issue tracker under "release blockers" and i 
said there were zero.

On Tuesday, March 24, 2015 at 10:06:32 AM UTC+11, 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 1.7?
>
> i'm also very interested in the new fabfile stuff for shared host installs.
>
> i'm also wondering, with mezz almost missing a whole django version 
> without a pip installable release, are things on the mezz release front 
> likely to continue to be very slow in staying up to date with changes in 
> mezz git? 
>
> not intending to be critical, not at all, just looking for an honest 
> assessment of how the project is faring with respect to official releases. 
> cheers.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - Possible Mezzanine Bug in relation to mezzanine.jupo.org install

[Graham]

The problem remains the same :-(
g

On 28/05/15 19:13, Mathias Ettinger wrote:

What happens if you swap django.contrib.auth and django.contrib.admin in your 
INSTALLED_APPS? Does it solves it without the extra step?



--
T : 021 081 71732

--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release? - Possible Mezzanine Bug in relation to mezzanine.jupo.org install

[Mathias Ettinger]

What happens if you swap django.contrib.auth and django.contrib.admin in your 
INSTALLED_APPS? Does it solves it without the extra step?

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release? - Possible Mezzanine Bug in relation to mezzanine.jupo.org install

[Graham Oliver]

Hello everyone
Using PostgreSQL in a virtual environment
When I go through the install process for the mezzanine.jupo.org web site I 
am encountering a problem with the latest Django version 1.8.2
Note the problem does *not* occur with 1.7.8

Here is a description and stack trace of the problem
https://github.com/stephenmcd/mezzanine.jupo.org/issues/6

I managed to get the install to work by running
python manage.py migrate auth (even though this exits with an error)
before the createdb command 

I got that idea from 
http://stackoverflow.com/questions/29689365/auth-user-error-with-django-1-8-and-syncdb-migrate

Cheers
g

p.s. I had to upgrade django-compressor to the latest version (1.5) to work 
around another problem

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release?

[Micah Yoder]

Yay, I just made that change manually in my copy and that fixed it! Thanks!
Surely I'm not the first person who ran into that???

On Sunday, May 3, 2015 at 6:41:15 PM UTC-5, Stephen McDonald wrote:
>
> This looks like a packaging issue with the comments app, I've provided 
> them with a fix here:
>
> https://github.com/django/django-contrib-comments/pull/40
>
> If you'd like to make use of that now, you can specify my fork of the 
> comments app in the above PR as your dependency.
>
>
> On Mon, May 4, 2015 at 12:46 AM, Micah Yoder  > wrote:
>
>> Hi,
>>
>> I've been trying to test out the upstream master code. I have a Python 
>> 3.4.3 virtualenv with django 1.8. When getting to the createdb step I'm 
>> getting this error:
>>
>>   File 
>> "/home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py",
>>  
>> line 174, in build_graph 
>>self.load_disk() 
>>  File 
>> "/home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py",
>>  
>> line 91, in load_disk 
>>for name in os.listdir(directory): 
>> NotADirectoryError: [Errno 20] Not a directory: 
>> '/home/micah/testsite/venv/lib/python3.4/site-packages/django_contrib_comments-1.6
>> .0-py3.4.egg/django_comments/migrations'
>>
>> That egg file definitely exists and the django_comments/migrations 
>> directory exists within it.
>>
>> I asked on IRC a few days ago and Stephen helpfully replied that I needed 
>> the git master version of django-contrib-comments.  I grabbed that and 
>> installed it and indeed that resolved the issue.  However, I then hit 
>> another error, representing an "out-of-sync" between Mezzanine and 
>> django-contrib-comments, which Stephen quickly fixed. Nice!  Unfortunately, 
>> after I installed it, the above error came back. And that's where I still 
>> am. :/
>>
>> Yes, I've re-installed the django-contrib-comments.  In fact I just now 
>> pulled the latest mezzanine and django-contrib-comments, installed them in 
>> that order, and I still get it.
>>
>> Any idea what's up/
>>
>> Thanks!
>>
>> Not a django expert but would like to get there. :)
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to mezzanine-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Stephen McDonald
> http://jupo.org
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Sreedhar Bukya]

Hi, 

My current project is working on Django 1.6.1 and mezzanine 3.0.8. 

This is the first time I am doing package upgrade. I am thinking to upgrade 
Django 1.8 in steps (first 1.7 then 1.8) and mezzanine to latest version 
both. 

What are the things i need to take care to complete upgrade?

If you could provide me some insights I  will be glad. 

Regards, 
Sreedhar 

On Tuesday, 24 March 2015 04:36:32 UTC+5:30, 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 1.7?
>
> i'm also very interested in the new fabfile stuff for shared host installs.
>
> i'm also wondering, with mezz almost missing a whole django version 
> without a pip installable release, are things on the mezz release front 
> likely to continue to be very slow in staying up to date with changes in 
> mezz git? 
>
> not intending to be critical, not at all, just looking for an honest 
> assessment of how the project is faring with respect to official releases. 
> cheers.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release?

[Stephen McDonald]

This looks like a packaging issue with the comments app, I've provided them
with a fix here:

https://github.com/django/django-contrib-comments/pull/40

If you'd like to make use of that now, you can specify my fork of the
comments app in the above PR as your dependency.


On Mon, May 4, 2015 at 12:46 AM, Micah Yoder  wrote:

> Hi,
>
> I've been trying to test out the upstream master code. I have a Python
> 3.4.3 virtualenv with django 1.8. When getting to the createdb step I'm
> getting this error:
>
>   File
> "/home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py",
> line 174, in build_graph
>self.load_disk()
>  File
> "/home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py",
> line 91, in load_disk
>for name in os.listdir(directory):
> NotADirectoryError: [Errno 20] Not a directory:
> '/home/micah/testsite/venv/lib/python3.4/site-packages/django_contrib_comments-1.6
> .0-py3.4.egg/django_comments/migrations'
>
> That egg file definitely exists and the django_comments/migrations
> directory exists within it.
>
> I asked on IRC a few days ago and Stephen helpfully replied that I needed
> the git master version of django-contrib-comments.  I grabbed that and
> installed it and indeed that resolved the issue.  However, I then hit
> another error, representing an "out-of-sync" between Mezzanine and
> django-contrib-comments, which Stephen quickly fixed. Nice!  Unfortunately,
> after I installed it, the above error came back. And that's where I still
> am. :/
>
> Yes, I've re-installed the django-contrib-comments.  In fact I just now
> pulled the latest mezzanine and django-contrib-comments, installed them in
> that order, and I still get it.
>
> Any idea what's up/
>
> Thanks!
>
> Not a django expert but would like to get there. :)
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Micah Yoder]

Hi,

I've been trying to test out the upstream master code. I have a Python 
3.4.3 virtualenv with django 1.8. When getting to the createdb step I'm 
getting this error:

  File 
"/home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py",
 
line 174, in build_graph 
   self.load_disk() 
 File 
"/home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py",
 
line 91, in load_disk 
   for name in os.listdir(directory): 
NotADirectoryError: [Errno 20] Not a directory: 
'/home/micah/testsite/venv/lib/python3.4/site-packages/django_contrib_comments-1.6
.0-py3.4.egg/django_comments/migrations'

That egg file definitely exists and the django_comments/migrations 
directory exists within it.

I asked on IRC a few days ago and Stephen helpfully replied that I needed 
the git master version of django-contrib-comments.  I grabbed that and 
installed it and indeed that resolved the issue.  However, I then hit 
another error, representing an "out-of-sync" between Mezzanine and 
django-contrib-comments, which Stephen quickly fixed. Nice!  Unfortunately, 
after I installed it, the above error came back. And that's where I still 
am. :/

Yes, I've re-installed the django-contrib-comments.  In fact I just now 
pulled the latest mezzanine and django-contrib-comments, installed them in 
that order, and I still get it.

Any idea what's up/

Thanks!

Not a django expert but would like to get there. :)

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release?

[Eduardo Rivas]

Also, you can take a look at the issues marked as "release blocker" in 
the issue tracker to get a sense of what is actually keeping the next 
release from happening.


--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Graham Oliver]

Hi Gavin
My understanding is that it is done on a best-efforts basis, so the short 
answer to your question is 'no'.
Cheers
g

On Wednesday, 29 April 2015 10:06:51 UTC+12, Gavin Wahl wrote:
>
> Is there a timeline for a release that supports Django 1.8?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Gavin Wahl]

Is there a timeline for a release that supports Django 1.8?

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - TypeError at /search/ unsupported operand type(s) for |=:

[Graham Oliver]

ok retested on Django 1.77 and 1.8 - all is good

On Wednesday, 15 April 2015 09:48:34 UTC+12, Stephen McDonald wrote:
>
> Good find Graham, thanks a lot for tracking it down.
>
> That's fixed now:
>
>
> https://github.com/stephenmcd/mezzanine/commit/3ad1a6a9ce049e14fe9d120be1226844ad201baf
>
> On Tue, Apr 14, 2015 at 5:55 PM, Graham Oliver  > wrote:
>
>> no problems in 1.7.7
>> Here is the return from the [m._meta.get_parent_list() for m in models] 
>> in 1.7.7
>> [{}, {> 'mezzanine.pages.models.Page'>}, {}, 
>> set(), {}, set(), {> 'mezzanine.pages.models.Page'>}, {}, 
>> {}]
>>
>> Here is the same return in 1.8
>> [[], [> 'mezzanine.pages.models.Page'>], [], 
>> [], [], [], [> 'mezzanine.pages.models.Page'>], [], 
>> []]
>>
>> cheers
>> g
>>
>>
>> My best guess is that it is something to do with 
>>
>> On Tuesday, 14 April 2015 19:00:18 UTC+12, Graham Oliver wrote:
>>>
>>> Python 3.4  Django 1.8
>>>
>>>  Request Method: GET  Request URL: http://192.168.1.81:8000/
>>> search/?q=samoa  Django Version: 1.8  Exception Type: TypeError  Exception 
>>> Value: 
>>>
>>> unsupported operand type(s) for |=: 'list' and 'list'
>>>
>>>  Exception Location: /home/graham/Virtual-Environments/test-py3-dj1.8/
>>> lib/python3.4/site-packages/mezzanine/core/managers.py in search, line 
>>> 265  Python Executable: /home/graham/Virtual-
>>> Environments/test-py3-dj1.8/bin/python 
>>> I will do some digging
>>> g
>>>
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to mezzanine-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Stephen McDonald
> http://jupo.org
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - TypeError at /search/ unsupported operand type(s) for |=:

[Stephen McDonald]

Good find Graham, thanks a lot for tracking it down.

That's fixed now:

https://github.com/stephenmcd/mezzanine/commit/3ad1a6a9ce049e14fe9d120be1226844ad201baf

On Tue, Apr 14, 2015 at 5:55 PM, Graham Oliver 
wrote:

> no problems in 1.7.7
> Here is the return from the [m._meta.get_parent_list() for m in models] in
> 1.7.7
> [{}, { 'mezzanine.pages.models.Page'>}, {},
> set(), {}, set(), { 'mezzanine.pages.models.Page'>}, {},
> {}]
>
> Here is the same return in 1.8
> [[], [ 'mezzanine.pages.models.Page'>], [],
> [], [], [], [ 'mezzanine.pages.models.Page'>], [],
> []]
>
> cheers
> g
>
>
> My best guess is that it is something to do with
>
> On Tuesday, 14 April 2015 19:00:18 UTC+12, Graham Oliver wrote:
>>
>> Python 3.4  Django 1.8
>>
>>  Request Method: GET  Request URL: http://192.168.1.81:8000/
>> search/?q=samoa  Django Version: 1.8  Exception Type: TypeError  Exception
>> Value:
>>
>> unsupported operand type(s) for |=: 'list' and 'list'
>>
>>  Exception Location: /home/graham/Virtual-Environments/test-py3-dj1.8/
>> lib/python3.4/site-packages/mezzanine/core/managers.py in search, line
>> 265  Python Executable: /home/graham/Virtual-Environments/test-py3-dj1.8/
>> bin/python
>> I will do some digging
>> g
>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - TypeError at /search/ unsupported operand type(s) for |=:

[Graham Oliver]

no problems in 1.7.7
Here is the return from the [m._meta.get_parent_list() for m in models] in 
1.7.7
[{}, {}, {}, 
set(), {}, set(), {}, {}, 
{}]

Here is the same return in 1.8
[[], [], [], 
[], [], [], [], [], 
[]]

cheers
g


My best guess is that it is something to do with 

On Tuesday, 14 April 2015 19:00:18 UTC+12, Graham Oliver wrote:
>
> Python 3.4  Django 1.8
>
>  Request Method: GET  Request URL: 
> http://192.168.1.81:8000/search/?q=samoa  Django Version: 1.8  Exception 
> Type: TypeError  Exception Value: 
>
> unsupported operand type(s) for |=: 'list' and 'list'
>
>  Exception Location: 
> /home/graham/Virtual-Environments/test-py3-dj1.8/lib/python3.4/site-packages/mezzanine/core/managers.py
>  
> in search, line 265  Python Executable: 
> /home/graham/Virtual-Environments/test-py3-dj1.8/bin/python 
> I will do some digging
> g
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - TypeError at /search/ unsupported operand type(s) for |=:

[Graham Oliver]

Python 3.4  Django 1.8

 Request Method: GET  Request URL: http://192.168.1.81:8000/search/?q=samoa  
Django 
Version: 1.8  Exception Type: TypeError  Exception Value: 

unsupported operand type(s) for |=: 'list' and 'list'

 Exception Location: 
/home/graham/Virtual-Environments/test-py3-dj1.8/lib/python3.4/site-packages/mezzanine/core/managers.py
 
in search, line 265  Python Executable: 
/home/graham/Virtual-Environments/test-py3-dj1.8/bin/python 
I will do some digging
g


-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - TypeError: __init__() got an unexpected keyword argument

[Graham Oliver]

Can't reproduce
No longer consider this a problem
g

On Friday, 10 April 2015 16:28:24 UTC+12, Graham Oliver wrote:
>
> All good on Python 3.4.3 and Django 1.8
> When I switch to Python 3.4.3 and Django 1.77 I get this stack trace when 
> doing 'python manage.py runserver'
>
> Unhandled exception in thread started by  check_errors..wrapper at 0x7ff18c8aba60>
> Traceback (most recent call last):
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/django/utils/autoreload.py",
>  
> line 222, in wrapper
> fn(*args, **kwargs)
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/mezzanine/core/management/commands/runserver.py",
>  
> line 154, in inner_run
> super(Command, self).inner_run(*args, **kwargs)
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/django/core/management/commands/runserver.py",
>  
> line 107, in inner_run
> self.check_migrations()
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/django/core/management/commands/runserver.py",
>  
> line 159, in check_migrations
> executor = MigrationExecutor(connections[DEFAULT_DB_ALIAS])
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/django/db/migrations/executor.py",
>  
> line 17, in __init__
> self.loader = MigrationLoader(self.connection)
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/django/db/migrations/loader.py",
>  
> line 48, in __init__
> self.build_graph()
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/django/db/migrations/loader.py",
>  
> line 177, in build_graph
> self.load_disk()
>   File 
> "/home/graham/.pyenv/versions/py3.4.3-dj1.7.7/lib/python3.4/site-packages/django/db/migrations/loader.py",
>  
> line 103, in load_disk
> migration_module = import_module("%s.%s" % (module_name, 
> migration_name))
>   File 
> "/home/graham/.pyenv/versions/3.4.3/lib/python3.4/importlib/__init__.py", 
> line 109, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 2254, in _gcd_import
>   File "", line 2237, in _find_and_load
>   File "", line 2226, in 
> _find_and_load_unlocked
>   File "", line 1200, in _load_unlocked
>   File "", line 1129, in _exec
>   File "", line 1471, in exec_module
>   File "", line 321, in 
> _call_with_frames_removed
>   File 
> "/home/graham/Dropbox/mp-soul-2/soulapp2/migrations/0001_initial.py", line 
> 11, in 
> class Migration(migrations.Migration):
>   File 
> "/home/graham/Dropbox/mp-soul-2/soulapp2/migrations/0001_initial.py", line 
> 36, in Migration
> ('objects', mezzanine.pages.managers.PageManager()),
> TypeError: __init__() got an unexpected keyword argument 'managers'
>
> cheers
> g
>
> On Thursday, 9 April 2015 20:29:35 UTC+12, Alex Hill wrote:
>>
>> Thanks for the report Graham - a fix for this has just been applied to 
>> master.
>>
>> Cheers,
>> Alex
>>
>> On Thu, Apr 9, 2015 at 2:33 PM, Graham  wrote:
>>
>>>  All good.
>>> g
>>>
>>>
>>> On 09/04/15 17:18, Stephen McDonald wrote:
>>>  
>>> I've actually added a new issue label called "release blockers" to the 
>>> issue tracker, which contains the new issue just discussed here. 
>>>
>>>  
>>> https://github.com/stephenmcd/mezzanine/issues?q=is%3Aopen+is%3Aissue+label%3A%22release+blocker%22
>>>  
>>>  So now we can track exactly what's left to do before the next release.
>>>
>>>  Thanks again Graham!
>>>  
>>> On Thu, Apr 9, 2015 at 2:34 PM, Graham  wrote:
>>>
 Hi Stephen
 I think I am using the up to date version of the code, namely

 try:
 # Django >= 1.8
 find_template_loader = context.engine.find_template_loader
 except AttributeError:
 # Django <= 1.7
 print ("hello")
 from django.template.loaders import find_template_loader

 prints hello

 This does not fit the logic of the comments because the Django version 
 is  1.8

 g



 On 09/04/15 15:59, Stephen McDonald wrote:
   
> That was resolved a few months ago:
>
>
> https://github.com/stephenmcd/mezzanine/commit/a50de50699bb6a24bfb5f118449991aa7608b426
>
> It looks like you're using the current 3.1.10 release of Mezzanine,
> rather than the development branch from Github.
>
> On 4/9/15, Graham Oliver  wrote:
>
>> Django 1.8
>> Python 3.4.3
>>
>> Accessing the admin
>>
>> ImportError at /admin/login/
>>
>> cannot import name 'find_template_loader'
>>
>>   Request Method: GET  Request URL:
>> http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
>> Exception
>> Type: ImportError  Exception Value:
>>
>> cannot import name 'find_template_loader'
>>
>>   Exception Location:
>>

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Stephen McDonald]

Big thanks to Alex Hill who's worked out the fix for the issue last
reported here - if you're testing, please pull the latest in again and give
it a whirl.

On Thu, Apr 9, 2015 at 3:02 PM, Stephen McDonald  wrote:

> My apologies, I was wrong earlier - looks like this code's really broken
> in 1.8. I'm not across so I'm not sure why, but I'll open an issue for it.
>
> Thanks a lot.
>
> On Thu, Apr 9, 2015 at 2:34 PM, Graham  wrote:
>
>> Hi Stephen
>> I think I am using the up to date version of the code, namely
>>
>> try:
>> # Django >= 1.8
>> find_template_loader = context.engine.find_template_loader
>> except AttributeError:
>> # Django <= 1.7
>> print ("hello")
>> from django.template.loaders import find_template_loader
>>
>> prints hello
>>
>> This does not fit the logic of the comments because the Django version
>> is  1.8
>>
>> g
>>
>>
>>
>> On 09/04/15 15:59, Stephen McDonald wrote:
>>
>>> That was resolved a few months ago:
>>>
>>> https://github.com/stephenmcd/mezzanine/commit/
>>> a50de50699bb6a24bfb5f118449991aa7608b426
>>>
>>> It looks like you're using the current 3.1.10 release of Mezzanine,
>>> rather than the development branch from Github.
>>>
>>> On 4/9/15, Graham Oliver  wrote:
>>>
 Django 1.8
 Python 3.4.3

 Accessing the admin

 ImportError at /admin/login/

 cannot import name 'find_template_loader'

   Request Method: GET  Request URL:
 http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
 Exception
 Type: ImportError  Exception Value:

 cannot import name 'find_template_loader'

   Exception Location:
 /home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
 site-packages/mezzanine/template/loader_tags.py

 in find_template, line 62  Python Executable:
 /home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version:
 3.4.3
   Python
 Path:

 ['/home/graham/Dropbox/mp-soul-2',
   '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
   '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
 site-packages',
   '/home/graham/Dropbox']

   Server time: Thu, 9 Apr 2015 15:19:14 +1200
 Error during template rendering

 In template
 /home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
 error at line *1*
 cannot import name 'find_template_loader' 1 {% overextends
 "admin/base_site.html" %}

 --
 You received this message because you are subscribed to the Google
 Groups
 "Mezzanine Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an
 email to mezzanine-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to mezzanine-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Stephen McDonald
> http://jupo.org
>



-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Alexander Hill]

Thanks for the report Graham - a fix for this has just been applied to
master.

Cheers,
Alex

On Thu, Apr 9, 2015 at 2:33 PM, Graham  wrote:

>  All good.
> g
>
>
> On 09/04/15 17:18, Stephen McDonald wrote:
>
> I've actually added a new issue label called "release blockers" to the
> issue tracker, which contains the new issue just discussed here.
>
>
> https://github.com/stephenmcd/mezzanine/issues?q=is%3Aopen+is%3Aissue+label%3A%22release+blocker%22
>
>  So now we can track exactly what's left to do before the next release.
>
>  Thanks again Graham!
>
> On Thu, Apr 9, 2015 at 2:34 PM, Graham  wrote:
>
>> Hi Stephen
>> I think I am using the up to date version of the code, namely
>>
>> try:
>> # Django >= 1.8
>> find_template_loader = context.engine.find_template_loader
>> except AttributeError:
>> # Django <= 1.7
>> print ("hello")
>> from django.template.loaders import find_template_loader
>>
>> prints hello
>>
>> This does not fit the logic of the comments because the Django version
>> is  1.8
>>
>> g
>>
>>
>>
>> On 09/04/15 15:59, Stephen McDonald wrote:
>>
>>> That was resolved a few months ago:
>>>
>>>
>>> https://github.com/stephenmcd/mezzanine/commit/a50de50699bb6a24bfb5f118449991aa7608b426
>>>
>>> It looks like you're using the current 3.1.10 release of Mezzanine,
>>> rather than the development branch from Github.
>>>
>>> On 4/9/15, Graham Oliver  wrote:
>>>
 Django 1.8
 Python 3.4.3

 Accessing the admin

 ImportError at /admin/login/

 cannot import name 'find_template_loader'

   Request Method: GET  Request URL:
 http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
 Exception
 Type: ImportError  Exception Value:

 cannot import name 'find_template_loader'

   Exception Location:

 /home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/mezzanine/template/loader_tags.py

 in find_template, line 62  Python Executable:
 /home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version:
 3.4.3
   Python
 Path:

 ['/home/graham/Dropbox/mp-soul-2',
   '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',

 '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages',
   '/home/graham/Dropbox']

   Server time: Thu, 9 Apr 2015 15:19:14 +1200
 Error during template rendering

 In template
 /home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
 error at line *1*
 cannot import name 'find_template_loader' 1 {% overextends
 "admin/base_site.html" %}

 --
 You received this message because you are subscribed to the Google
 Groups
 "Mezzanine Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an
 email to mezzanine-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to mezzanine-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
>  --
> Stephen McDonald
> http://jupo.org
>  --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Graham]

All good.
g

On 09/04/15 17:18, Stephen McDonald wrote:
I've actually added a new issue label called "release blockers" to the 
issue tracker, which contains the new issue just discussed here.


https://github.com/stephenmcd/mezzanine/issues?q=is%3Aopen+is%3Aissue+label%3A%22release+blocker%22

So now we can track exactly what's left to do before the next release.

Thanks again Graham!

On Thu, Apr 9, 2015 at 2:34 PM, Graham > wrote:


Hi Stephen
I think I am using the up to date version of the code, namely

try:
# Django >= 1.8
find_template_loader = context.engine.find_template_loader
except AttributeError:
# Django <= 1.7
print ("hello")
from django.template.loaders import find_template_loader

prints hello

This does not fit the logic of the comments because the Django
version is  1.8

g



On 09/04/15 15:59, Stephen McDonald wrote:

That was resolved a few months ago:


https://github.com/stephenmcd/mezzanine/commit/a50de50699bb6a24bfb5f118449991aa7608b426

It looks like you're using the current 3.1.10 release of
Mezzanine,
rather than the development branch from Github.

On 4/9/15, Graham Oliver mailto:greenbay.gra...@gmail.com>> wrote:

Django 1.8
Python 3.4.3

Accessing the admin

ImportError at /admin/login/

cannot import name 'find_template_loader'

  Request Method: GET  Request URL:
http://127.0.0.1:8000/admin/login/?next=/admin/ Django
Version: 1.8
Exception
Type: ImportError  Exception Value:

cannot import name 'find_template_loader'

  Exception Location:

/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/mezzanine/template/loader_tags.py

in find_template, line 62  Python Executable:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python
Python Version: 3.4.3
  Python
Path:

['/home/graham/Dropbox/mp-soul-2',
  '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
 
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
 
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
 
'/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages',

  '/home/graham/Dropbox']

  Server time: Thu, 9 Apr 2015 15:19:14 +1200
Error during template rendering

In template

/home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
error at line *1*
cannot import name 'find_template_loader' 1 {% overextends
"admin/base_site.html" %}

--
You received this message because you are subscribed to
the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails
from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google

Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to mezzanine-users+unsubscr...@googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.




--
Stephen McDonald
http://jupo.org
--
You received this message because you are subscribed to the Google 
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Stephen McDonald]

I've actually added a new issue label called "release blockers" to the
issue tracker, which contains the new issue just discussed here.

https://github.com/stephenmcd/mezzanine/issues?q=is%3Aopen+is%3Aissue+label%3A%22release+blocker%22

So now we can track exactly what's left to do before the next release.

Thanks again Graham!

On Thu, Apr 9, 2015 at 2:34 PM, Graham  wrote:

> Hi Stephen
> I think I am using the up to date version of the code, namely
>
> try:
> # Django >= 1.8
> find_template_loader = context.engine.find_template_loader
> except AttributeError:
> # Django <= 1.7
> print ("hello")
> from django.template.loaders import find_template_loader
>
> prints hello
>
> This does not fit the logic of the comments because the Django version is
> 1.8
>
> g
>
>
>
> On 09/04/15 15:59, Stephen McDonald wrote:
>
>> That was resolved a few months ago:
>>
>> https://github.com/stephenmcd/mezzanine/commit/
>> a50de50699bb6a24bfb5f118449991aa7608b426
>>
>> It looks like you're using the current 3.1.10 release of Mezzanine,
>> rather than the development branch from Github.
>>
>> On 4/9/15, Graham Oliver  wrote:
>>
>>> Django 1.8
>>> Python 3.4.3
>>>
>>> Accessing the admin
>>>
>>> ImportError at /admin/login/
>>>
>>> cannot import name 'find_template_loader'
>>>
>>>   Request Method: GET  Request URL:
>>> http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
>>> Exception
>>> Type: ImportError  Exception Value:
>>>
>>> cannot import name 'find_template_loader'
>>>
>>>   Exception Location:
>>> /home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
>>> site-packages/mezzanine/template/loader_tags.py
>>>
>>> in find_template, line 62  Python Executable:
>>> /home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version:
>>> 3.4.3
>>>   Python
>>> Path:
>>>
>>> ['/home/graham/Dropbox/mp-soul-2',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
>>>   '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
>>> site-packages',
>>>   '/home/graham/Dropbox']
>>>
>>>   Server time: Thu, 9 Apr 2015 15:19:14 +1200
>>> Error during template rendering
>>>
>>> In template
>>> /home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
>>> error at line *1*
>>> cannot import name 'find_template_loader' 1 {% overextends
>>> "admin/base_site.html" %}
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to mezzanine-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Stephen McDonald]

My apologies, I was wrong earlier - looks like this code's really broken in
1.8. I'm not across so I'm not sure why, but I'll open an issue for it.

Thanks a lot.

On Thu, Apr 9, 2015 at 2:34 PM, Graham  wrote:

> Hi Stephen
> I think I am using the up to date version of the code, namely
>
> try:
> # Django >= 1.8
> find_template_loader = context.engine.find_template_loader
> except AttributeError:
> # Django <= 1.7
> print ("hello")
> from django.template.loaders import find_template_loader
>
> prints hello
>
> This does not fit the logic of the comments because the Django version is
> 1.8
>
> g
>
>
>
> On 09/04/15 15:59, Stephen McDonald wrote:
>
>> That was resolved a few months ago:
>>
>> https://github.com/stephenmcd/mezzanine/commit/
>> a50de50699bb6a24bfb5f118449991aa7608b426
>>
>> It looks like you're using the current 3.1.10 release of Mezzanine,
>> rather than the development branch from Github.
>>
>> On 4/9/15, Graham Oliver  wrote:
>>
>>> Django 1.8
>>> Python 3.4.3
>>>
>>> Accessing the admin
>>>
>>> ImportError at /admin/login/
>>>
>>> cannot import name 'find_template_loader'
>>>
>>>   Request Method: GET  Request URL:
>>> http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
>>> Exception
>>> Type: ImportError  Exception Value:
>>>
>>> cannot import name 'find_template_loader'
>>>
>>>   Exception Location:
>>> /home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
>>> site-packages/mezzanine/template/loader_tags.py
>>>
>>> in find_template, line 62  Python Executable:
>>> /home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version:
>>> 3.4.3
>>>   Python
>>> Path:
>>>
>>> ['/home/graham/Dropbox/mp-soul-2',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
>>>   '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
>>>   '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
>>> site-packages',
>>>   '/home/graham/Dropbox']
>>>
>>>   Server time: Thu, 9 Apr 2015 15:19:14 +1200
>>> Error during template rendering
>>>
>>> In template
>>> /home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
>>> error at line *1*
>>> cannot import name 'find_template_loader' 1 {% overextends
>>> "admin/base_site.html" %}
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to mezzanine-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Graham]

Hi Stephen
I think I am using the up to date version of the code, namely

try:
# Django >= 1.8
find_template_loader = context.engine.find_template_loader
except AttributeError:
# Django <= 1.7
print ("hello")
from django.template.loaders import find_template_loader

prints hello

This does not fit the logic of the comments because the Django version 
is  1.8


g



On 09/04/15 15:59, Stephen McDonald wrote:

That was resolved a few months ago:

https://github.com/stephenmcd/mezzanine/commit/a50de50699bb6a24bfb5f118449991aa7608b426

It looks like you're using the current 3.1.10 release of Mezzanine,
rather than the development branch from Github.

On 4/9/15, Graham Oliver  wrote:

Django 1.8
Python 3.4.3

Accessing the admin

ImportError at /admin/login/

cannot import name 'find_template_loader'

  Request Method: GET  Request URL:
http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
Exception
Type: ImportError  Exception Value:

cannot import name 'find_template_loader'

  Exception Location:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/mezzanine/template/loader_tags.py

in find_template, line 62  Python Executable:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version: 3.4.3
  Python
Path:

['/home/graham/Dropbox/mp-soul-2',
  '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
  '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages',
  '/home/graham/Dropbox']

  Server time: Thu, 9 Apr 2015 15:19:14 +1200
Error during template rendering

In template
/home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
error at line *1*
cannot import name 'find_template_loader' 1 {% overextends
"admin/base_site.html" %}

--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.





--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Graham]

oops sorry
will sort
g

On 09/04/15 15:59, Stephen McDonald wrote:

That was resolved a few months ago:

https://github.com/stephenmcd/mezzanine/commit/a50de50699bb6a24bfb5f118449991aa7608b426

It looks like you're using the current 3.1.10 release of Mezzanine,
rather than the development branch from Github.

On 4/9/15, Graham Oliver  wrote:

Django 1.8
Python 3.4.3

Accessing the admin

ImportError at /admin/login/

cannot import name 'find_template_loader'

  Request Method: GET  Request URL:
http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
Exception
Type: ImportError  Exception Value:

cannot import name 'find_template_loader'

  Exception Location:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/mezzanine/template/loader_tags.py

in find_template, line 62  Python Executable:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version: 3.4.3
  Python
Path:

['/home/graham/Dropbox/mp-soul-2',
  '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
  '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages',
  '/home/graham/Dropbox']

  Server time: Thu, 9 Apr 2015 15:19:14 +1200
Error during template rendering

In template
/home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
error at line *1*
cannot import name 'find_template_loader' 1 {% overextends
"admin/base_site.html" %}

--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.





--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Stephen McDonald]

That was resolved a few months ago:

https://github.com/stephenmcd/mezzanine/commit/a50de50699bb6a24bfb5f118449991aa7608b426

It looks like you're using the current 3.1.10 release of Mezzanine,
rather than the development branch from Github.

On 4/9/15, Graham Oliver  wrote:
> Django 1.8
> Python 3.4.3
>
> Accessing the admin
>
> ImportError at /admin/login/
>
> cannot import name 'find_template_loader'
>
>  Request Method: GET  Request URL:
> http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8
> Exception
> Type: ImportError  Exception Value:
>
> cannot import name 'find_template_loader'
>
>  Exception Location:
> /home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/mezzanine/template/loader_tags.py
>
> in find_template, line 62  Python Executable:
> /home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version: 3.4.3
>  Python
> Path:
>
> ['/home/graham/Dropbox/mp-soul-2',
>  '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
>  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
>  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
>  '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
>  '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages',
>  '/home/graham/Dropbox']
>
>  Server time: Thu, 9 Apr 2015 15:19:14 +1200
> Error during template rendering
>
> In template
> /home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
> error at line *1*
> cannot import name 'find_template_loader' 1 {% overextends
> "admin/base_site.html" %}
>
> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'

[Graham Oliver]

Django 1.8
Python 3.4.3

Accessing the admin 

ImportError at /admin/login/ 

cannot import name 'find_template_loader'

 Request Method: GET  Request URL: 
http://127.0.0.1:8000/admin/login/?next=/admin/  Django Version: 1.8  Exception 
Type: ImportError  Exception Value: 

cannot import name 'find_template_loader'

 Exception Location: 
/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/mezzanine/template/loader_tags.py
 
in find_template, line 62  Python Executable: 
/home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python  Python Version: 3.4.3  
Python 
Path: 

['/home/graham/Dropbox/mp-soul-2',
 '/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
 '/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
 '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
 '/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
 '/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages',
 '/home/graham/Dropbox']

 Server time: Thu, 9 Apr 2015 15:19:14 +1200  
Error during template rendering 

In template 
/home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html, 
error at line *1*
cannot import name 'find_template_loader' 1 {% overextends 
"admin/base_site.html" %}

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release?

[Graham]

ok thanks
This worked for me

1. pip install south

2. python manage.py makemigrations soulapp2 (note that the Django 
documentation is incorrect according to the first answer here 
http://stackoverflow.com/questions/24912173/django-1-7-makemigrations-not-detecting-changes)


3. python manage.py migrate --fake-initial

4. pip uninstall south

Thanks
g

On 08/04/15 20:54, Mathias Ettinger wrote:
If you never created migration for south, it might be possible that 
you won't even have to use the --fake-initial option. But yeah, it is 
the way to go.



Le 08/04/2015 10:50, Graham a écrit :

No I don't so I will need to do something to stop the errors occuring
I was thinking something along these lines Does that look right?
https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south

On 08/04/15 20:43, Mathias Ettinger wrote:

Do you have migration defined in your soulapp2 application?

If not, it is standard Django behaviour. The doc says:
Be aware, however, that unmigrated apps cannot depend on migrated 
apps, by the very nature of not having migrations. This means that 
it is not generally possible to have an unmigrated app have a 
ForeignKey or ManyToManyField to a migrated app; some cases may 
work, but it will eventually fail.




Le 08/04/2015 03:43, Graham Oliver a écrit :

Django 1.8 - Python 3.4.3
Took the advice of the console 'You have unapplied migrations; your 
app may not work properly until they are applied.

Run 'python manage.py migrate' to apply them.'

and ran python manage.py migrate

stack trace

Running migrations:
  Rendering model states...Traceback (most recent call last):
  File "manage.py", line 28, in 
execute_from_command_line(sys.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 338, in execute_from_command_line

utility.execute()
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 330, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 390, in run_from_argv

self.execute(*args, **cmd_options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 441, in execute

output = self.handle(*args, **options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/commands/migrate.py", 
line 221, in handle
executor.migrate(targets, plan, fake=fake, 
fake_initial=fake_initial)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/executor.py", 
line 100, in migrate

state.apps  # Render all real_apps -- performance critical
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/utils/functional.py", 
line 60, in __get__

res = instance.__dict__[self.name] = self.func(instance)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 154, in apps

return StateApps(self.real_apps, self.models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 220, in __init__

self.render_multiple(list(models.values()) + self.real_models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 258, in render_multiple

"for more" % (new_unrendered_models, get_docs_version())
django.db.migrations.state.InvalidBasesError: Cannot resolve bases 
for [, 'soulapp2.SoulClassInformation'>, ]
This can happen if you are inheriting models from an app with 
migrations (e.g. contrib.auth)
 in an app with no migrations; see 
https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies 
for more


*Note*
The 3 models mentioned are the only ones in the project that 
inherit from 'Page' and 'RichText'

--
You received this message because you are subscribed to a topic in 
the Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/mezzanine-users/_QWfFVB3RVc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google 
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, 
send an email to mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to a topic in 
the Google Groups "Mezzanine Us

Re: [mezzanine-users] Re: new release?

[Mathias Ettinger]

If you never created migration for south, it might be possible that you 
won't even have to use the --fake-initial option. But yeah, it is the 
way to go.



Le 08/04/2015 10:50, Graham a écrit :

No I don't so I will need to do something to stop the errors occuring
I was thinking something along these lines Does that look right?
https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south

On 08/04/15 20:43, Mathias Ettinger wrote:

Do you have migration defined in your soulapp2 application?

If not, it is standard Django behaviour. The doc says:
Be aware, however, that unmigrated apps cannot depend on migrated 
apps, by the very nature of not having migrations. This means that it 
is not generally possible to have an unmigrated app have a ForeignKey 
or ManyToManyField to a migrated app; some cases may work, but it 
will eventually fail.




Le 08/04/2015 03:43, Graham Oliver a écrit :

Django 1.8 - Python 3.4.3
Took the advice of the console 'You have unapplied migrations; your 
app may not work properly until they are applied.

Run 'python manage.py migrate' to apply them.'

and ran python manage.py migrate

stack trace

Running migrations:
  Rendering model states...Traceback (most recent call last):
  File "manage.py", line 28, in 
execute_from_command_line(sys.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 338, in execute_from_command_line

utility.execute()
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 330, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 390, in run_from_argv

self.execute(*args, **cmd_options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 441, in execute

output = self.handle(*args, **options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/commands/migrate.py", 
line 221, in handle
executor.migrate(targets, plan, fake=fake, 
fake_initial=fake_initial)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/executor.py", 
line 100, in migrate

state.apps  # Render all real_apps -- performance critical
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/utils/functional.py", 
line 60, in __get__

res = instance.__dict__[self.name] = self.func(instance)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 154, in apps

return StateApps(self.real_apps, self.models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 220, in __init__

self.render_multiple(list(models.values()) + self.real_models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 258, in render_multiple

"for more" % (new_unrendered_models, get_docs_version())
django.db.migrations.state.InvalidBasesError: Cannot resolve bases 
for [, 'soulapp2.SoulClassInformation'>, ]
This can happen if you are inheriting models from an app with 
migrations (e.g. contrib.auth)
 in an app with no migrations; see 
https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies for 
more


*Note*
The 3 models mentioned are the only ones in the project that inherit 
from 'Page' and 'RichText'

--
You received this message because you are subscribed to a topic in 
the Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/mezzanine-users/_QWfFVB3RVc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google 
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, 
send an email to mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to a topic in the 
Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/mezzanine-users/_QWfFVB3RVc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because

Re: [mezzanine-users] Re: new release?

[Graham]

No I don't so I will need to do something to stop the errors occuring
I was thinking something along these lines Does that look right?
https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south

On 08/04/15 20:43, Mathias Ettinger wrote:

Do you have migration defined in your soulapp2 application?

If not, it is standard Django behaviour. The doc says:
Be aware, however, that unmigrated apps cannot depend on migrated 
apps, by the very nature of not having migrations. This means that it 
is not generally possible to have an unmigrated app have a ForeignKey 
or ManyToManyField to a migrated app; some cases may work, but it will 
eventually fail.




Le 08/04/2015 03:43, Graham Oliver a écrit :

Django 1.8 - Python 3.4.3
Took the advice of the console 'You have unapplied migrations; your 
app may not work properly until they are applied.

Run 'python manage.py migrate' to apply them.'

and ran python manage.py migrate

stack trace

Running migrations:
  Rendering model states...Traceback (most recent call last):
  File "manage.py", line 28, in 
execute_from_command_line(sys.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 338, in execute_from_command_line

utility.execute()
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 330, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 390, in run_from_argv

self.execute(*args, **cmd_options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 441, in execute

output = self.handle(*args, **options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/commands/migrate.py", 
line 221, in handle

executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/executor.py", 
line 100, in migrate

state.apps  # Render all real_apps -- performance critical
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/utils/functional.py", 
line 60, in __get__

res = instance.__dict__[self.name] = self.func(instance)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 154, in apps

return StateApps(self.real_apps, self.models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 220, in __init__

self.render_multiple(list(models.values()) + self.real_models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 258, in render_multiple

"for more" % (new_unrendered_models, get_docs_version())
django.db.migrations.state.InvalidBasesError: Cannot resolve bases 
for [, 'soulapp2.SoulClassInformation'>, ]
This can happen if you are inheriting models from an app with 
migrations (e.g. contrib.auth)
 in an app with no migrations; see 
https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies 
for more


*Note*
The 3 models mentioned are the only ones in the project that inherit 
from 'Page' and 'RichText'

--
You received this message because you are subscribed to a topic in 
the Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/mezzanine-users/_QWfFVB3RVc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google 
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release?

[Mathias Ettinger]

Do you have migration defined in your soulapp2 application?

If not, it is standard Django behaviour. The doc says:
Be aware, however, that unmigrated apps cannot depend on migrated apps, 
by the very nature of not having migrations. This means that it is not 
generally possible to have an unmigrated app have a ForeignKey or 
ManyToManyField to a migrated app; some cases may work, but it will 
eventually fail.




Le 08/04/2015 03:43, Graham Oliver a écrit :

Django 1.8 - Python 3.4.3
Took the advice of the console 'You have unapplied migrations; your 
app may not work properly until they are applied.

Run 'python manage.py migrate' to apply them.'

and ran python manage.py migrate

stack trace

Running migrations:
  Rendering model states...Traceback (most recent call last):
  File "manage.py", line 28, in 
execute_from_command_line(sys.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 338, in execute_from_command_line

utility.execute()
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py", 
line 330, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 390, in run_from_argv

self.execute(*args, **cmd_options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py", 
line 441, in execute

output = self.handle(*args, **options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/commands/migrate.py", 
line 221, in handle

executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/executor.py", 
line 100, in migrate

state.apps  # Render all real_apps -- performance critical
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/utils/functional.py", 
line 60, in __get__

res = instance.__dict__[self.name] = self.func(instance)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 154, in apps

return StateApps(self.real_apps, self.models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 220, in __init__

self.render_multiple(list(models.values()) + self.real_models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py", 
line 258, in render_multiple

"for more" % (new_unrendered_models, get_docs_version())
django.db.migrations.state.InvalidBasesError: Cannot resolve bases for 
[, 'soulapp2.SoulClassInformation'>, ]
This can happen if you are inheriting models from an app with 
migrations (e.g. contrib.auth)
 in an app with no migrations; see 
https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies 
for more


*Note*
The 3 models mentioned are the only ones in the project that inherit 
from 'Page' and 'RichText'

--
You received this message because you are subscribed to a topic in the 
Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/mezzanine-users/_QWfFVB3RVc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Graham Oliver]

Django 1.8 - Python 3.4.3
Took the advice of the console 'You have unapplied migrations; your app may 
not work properly until they are applied.
Run 'python manage.py migrate' to apply them.'

and ran python manage.py migrate

stack trace

Running migrations:
  Rendering model states...Traceback (most recent call last):
  File "manage.py", line 28, in 
execute_from_command_line(sys.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py",
 
line 338, in execute_from_command_line
utility.execute()
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/__init__.py",
 
line 330, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py",
 
line 390, in run_from_argv
self.execute(*args, **cmd_options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/base.py",
 
line 441, in execute
output = self.handle(*args, **options)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/core/management/commands/migrate.py",
 
line 221, in handle
executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/executor.py",
 
line 100, in migrate
state.apps  # Render all real_apps -- performance critical
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/utils/functional.py",
 
line 60, in __get__
res = instance.__dict__[self.name] = self.func(instance)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py",
 
line 154, in apps
return StateApps(self.real_apps, self.models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py",
 
line 220, in __init__
self.render_multiple(list(models.values()) + self.real_models)
  File 
"/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/django/db/migrations/state.py",
 
line 258, in render_multiple
"for more" % (new_unrendered_models, get_docs_version())
django.db.migrations.state.InvalidBasesError: Cannot resolve bases for 
[, , ]
This can happen if you are inheriting models from an app with migrations 
(e.g. contrib.auth)
 in an app with no migrations; see 
https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies for 
more

*Note*
The 3 models mentioned are the only ones in the project that inherit from 
'Page' and 'RichText'

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[David Unric]

Can confirm, exactly same warning messages.

On Tuesday, April 7, 2015 at 9:43:46 AM UTC+2, Graham Oliver wrote:
>
> Just adding this to this thread. Let me know if it should go elsewhere
> Django 1.8, Python 3.4.3
> When I do python manage.py runserver
>
> 1) I get many of these 'RemovedInDjango19Warning'
>
> also
>
> 2) I get this warning
> WARNINGS:
> core.SitePermission.user: (fields.W342) Setting unique=True on a 
> ForeignKey has the same effect as using a OneToOneField.
> HINT: ForeignKey(unique=True) is usually better served by a 
> OneToOneField.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Graham Oliver]

Same results on Python 2.7.9

I notice that all of the 4 tests except the first one had this text

'You have unapplied migrations; your app may not work properly until they 
are applied.
Run 'python manage.py migrate' to apply them.'


-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Graham Oliver]

Django 1.7.7, Python 3.4.3

python manage.py runserver 

Performing system checks...

System check identified some issues:

WARNINGS:
?: (1_6.W001) Some project unittests may not execute as expected.
HINT: Django 1.6 introduced a new default test runner. It looks like 
this project was generated using Django 1.5 or earlier. You should ensure 
your tests are all running & behaving as expected. See 
https://docs.djangoproject.com/en/dev/releases/1.6/#new-test-runner for 
more information.

System check identified 1 issue (0 silenced).

You have unapplied migrations; your app may not work properly until they 
are applied.
Run 'python manage.py migrate' to apply them.

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Graham Oliver]

Just adding this to this thread. Let me know if it should go elsewhere
Django 1.8, Python 3.4.3
When I do python manage.py runserver

1) I get many of these 'RemovedInDjango19Warning'

also

2) I get this warning
WARNINGS:
core.SitePermission.user: (fields.W342) Setting unique=True on a ForeignKey 
has the same effect as using a OneToOneField.
HINT: ForeignKey(unique=True) is usually better served by a 
OneToOneField.


On Tuesday, 24 March 2015 12:06:32 UTC+13, 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 1.7?
>
> i'm also very interested in the new fabfile stuff for shared host installs.
>
> i'm also wondering, with mezz almost missing a whole django version 
> without a pip installable release, are things on the mezz release front 
> likely to continue to be very slow in staying up to date with changes in 
> mezz git? 
>
> not intending to be critical, not at all, just looking for an honest 
> assessment of how the project is faring with respect to official releases. 
> cheers.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Eduardo Rivas]

Here's my take on the createdb issue. The version checking feels dirty, but 
it works. https://github.com/stephenmcd/mezzanine/pull/1247

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Eduardo Rivas]

As you can see in the file linked by Mathias, you can get rid of the test 
runner warning by overriding a setting:

TEST_RUNNER = 'django.test.runner.DiscoverRunner'

The docstring 

 
of the function that performs the check seems to support the assumption 
that this setting should be overridden, so I think it is an acceptable fix.








-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: new release?

[Ken Bolton]

On Tue, Mar 24, 2015 at 8:46 AM, Asif Saifuddin  wrote:

> Why not a version 3.2 with dj 1.7 and 1.8 support?
>

Django has a glorious history of supporting the three most recent point
releases. Mezzanine, appropriately, continues that by releasing versions
that support the currently-supported versions of Django. This has always
been, in my opinion, the sensible way to approach releases. Right now,
support for Django 1.5 is far more important. If support were dropped for
1.5, this would make Mezzanine much less valuable for those of us who have
relied on stable releases for five years.

If you absolutely need some feature in 1.7, you have two options: 1. use
master or 2. fix the outstanding issues that are blocking a release.

1.8 support is right out. Asking for it is a distraction from the important
work of the contributors and maintainers.

- ken

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Asif Saifuddin]

Why not a version 3.2 with dj 1.7 and 1.8 support?

On Tuesday, March 24, 2015 at 9:52:17 AM UTC+6, Eduardo Rivas wrote:
>
> Hi. I'm sharing my personal viewpoint (wait for Steve to give a official 
> statement):
>
>- My appreciation is that catching up with Django 1.7 is taking a lot 
>because it introduces a lot of backwards-incompatible changes AND 
> Mezzanine 
>wants to keep supporting Django 1.6 too. With 1.8 we might not have the 
>same problem, because we probably won't be seeing so many breaking 
> changes. 
>Also, the next release will have Model translation support, which is huge 
>too!
>- A warning related to the Fabric script: it will only work if you 
>have sudo privileges on the remote server. I'm mentioning this because 
>shared hosting accounts often lack this privilege.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: new release?

[Eduardo Rivas]

Hi. I'm sharing my personal viewpoint (wait for Steve to give a official 
statement):

   - My appreciation is that catching up with Django 1.7 is taking a lot 
   because it introduces a lot of backwards-incompatible changes AND Mezzanine 
   wants to keep supporting Django 1.6 too. With 1.8 we might not have the 
   same problem, because we probably won't be seeing so many breaking changes. 
   Also, the next release will have Model translation support, which is huge 
   too!
   - A warning related to the Fabric script: it will only work if you have 
   sudo privileges on the remote server. I'm mentioning this because shared 
   hosting accounts often lack this privilege.

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.