hi team!! yes, i've the same Kevin's first error "FAIL: test_syntax
(mezzanine.core.tests.CoreTests), and solved adding the commented
"pyflakes==0.6.1", "pep8==1.4.1" dependencies in "install_requires" section
of setup.py, then run again "python setup.py install" and the result is "OK"
thanks &
Hi Stephen
Thanks for confirming that.
I've made a change and created a pull request in Bitbucket.
I'm still not completely sure I've done the
forking/branching/pullrequesting quite right with Mercurial. I think the
problem stems from the fact that the words 'branch' and 'fork' mean very
differ
Looks like all tests are passing.
On Tue, Apr 22, 2014 at 7:54 PM, Kevin Golding
wrote:
> Hi Stephen
> Thanks for the timely response.
> When you mentioned the bad/missing Pillow install I recalled that I
> originally had some issues with Pillow. I think Pillow itself has a number
> of (possibly
Hi Stephen
Thanks for the timely response.
When you mentioned the bad/missing Pillow install I recalled that I
originally had some issues with Pillow. I think Pillow itself has a number
of (possibly undocumented?) dependencies and things go quite wrong if they
are not met when you try to install
Those all look like dependency issues.
Making sure you've got the correct versions of the test dependencies (as
per `tests_require` in setup.py) should fix the first failure.
The second and third look due to a bad/missing PIL/Pillow install.
The failures against Django 1.7 are expected - there's
Hi all
I was planning to make some changes for things that are deprecated in
Django1.7, so I forked Mezzanine on bitbucket and did all the steps in the
"Contributing" section to create a development environment (but using my
fork on bitbucket instead of the github one listed).
However before I
