Re: [mezzanine-users] upgrading from 1.4.6 to 3.1.6 south disappears
On Tuesday, May 13, 2014 6:55:44 AM UTC+2, Stephen McDonald wrote: Nice work tracking that down. The error you're getting looks like a missing library (called future, that link you found is misleading) - how have you installed the latest Mezzanine version? It should automatically install the required dependencies when installing via pip - you can see the future lib references here in the setup: https://github.com/stephenmcd/mezzanine/blob/master/setup.py#L60 http://jupo.org Just to follow up on this. It's all resolved now after I upgraded with pip. I was trying to run it off a git checkout for testing the upgrade before I installed it system wide. Not wise. Thanks for your help! -- 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] upgrading from 1.4.6 to 3.1.6 south disappears
Nice work tracking that down. The error you're getting looks like a missing library (called future, that link you found is misleading) - how have you installed the latest Mezzanine version? It should automatically install the required dependencies when installing via pip - you can see the future lib references here in the setup: https://github.com/stephenmcd/mezzanine/blob/master/setup.py#L60 On Tue, May 13, 2014 at 2:51 PM, Penny Leach penelope.le...@gmail.comwrote: On Monday, May 12, 2014 3:19:44 AM UTC+2, Stephen McDonald wrote: Can't reproduce this going from a fresh 1.4.6 project and running it against 3.1.4. Thanks for looking into it! I've seen this behaviour with Django projects in general before though, where some unrelated issue has the side effect of Django reporting that management commands provided by third-party apps aren't available. While that's not much help, it's doubtful your issue is South related, and I suspect you need to somehow force the real issue to come up - perhaps with Django's own shell or runserver commands, which all have a --traceback option that might prove useful in this case too. It seems you're right. With further prodding, I managed to yield the following error: ImportError: No module named future.builtins Any ideas? I'm using python 2.7.3 and I found this page: https://docs.python.org/2/library/future_builtins.html but didn't get any further. Thanks! Penny -- 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] upgrading from 1.4.6 to 3.1.6 south disappears
Hi there, I'm trying to upgrade (actually I'm only trying to start running a test upgrade) from 1.4.6 to 3.1.4 and failing before I start because as soon as I switch to using the 3.1.4 mezzanine code, south has disappeared from manage.py output. USE_SOUTH is set to true, and I can literally reproduce the problem thus: - checkout mezzanine to the 1.4.6 branch - manage.py shows south section - checkout mezzanine to the 3.1.4 branch - manage.py shows no south USE_SOUTH seems to be still a valid setting in 3.1.4 because it's there in the project template still, so I can't imagine that is the problem. Has something else changed? Thanks! Penny -- 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] upgrading from 1.4.6 to 3.1.6 south disappears
Can't reproduce this going from a fresh 1.4.6 project and running it against 3.1.4. I've seen this behaviour with Django projects in general before though, where some unrelated issue has the side effect of Django reporting that management commands provided by third-party apps aren't available. While that's not much help, it's doubtful your issue is South related, and I suspect you need to somehow force the real issue to come up - perhaps with Django's own shell or runserver commands, which all have a --traceback option that might prove useful in this case too. Good luck. On Mon, May 12, 2014 at 5:50 AM, Penny Leach penelope.le...@gmail.comwrote: Hi there, I'm trying to upgrade (actually I'm only trying to start running a test upgrade) from 1.4.6 to 3.1.4 and failing before I start because as soon as I switch to using the 3.1.4 mezzanine code, south has disappeared from manage.py output. USE_SOUTH is set to true, and I can literally reproduce the problem thus: - checkout mezzanine to the 1.4.6 branch - manage.py shows south section - checkout mezzanine to the 3.1.4 branch - manage.py shows no south USE_SOUTH seems to be still a valid setting in 3.1.4 because it's there in the project template still, so I can't imagine that is the problem. Has something else changed? Thanks! Penny -- 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.
