Re: [mezzanine-users] Error with Pisa? P3?
Thanks so much!! now I know where to look..
BTW Shouldn't both reportlab and pillow be in the requirements txt file??
They were the only two I needed to download separately..
On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
>
> The error is coming from sx/pisa3/__init__.py, line 43 which says:
>
> {{{
> if not REPORTLAB22:
> raise ImportError, "Reportlab Toolkit Version 2.2 or higher
> needed"
> }}}
>
> Now, obviously you do have reportlab of a version higher than 2.2 but
> there was a bug mentioned on the cartridge issues a few weeks ago which
> seemed to indicate that reportlab 3.0 isn't reporting its version
> correctly as higher than 2.2.
>
> See
> https://github.com/stephenmcd/cartridge/issues/174#issuecomment-35755887
>
> It seems like it's a known bug in pisa.
>
> Hope this helps.
>
> Seeya. Danny.
>
> On 27/02/2014 9:52 AM, Tom Brander wrote:
> > Hmm did not have reportlab, so I installed it but no change, here is the
> > pip list
> > (myvenv3) tom@tom-sam:~/whiteplume$ pip list
> > bleach (1.4)
> > Cartridge (0.9.2)
> > Django (1.6.2)
> > filebrowser-safe (0.3.2)
> > future (0.9.0)
> > grappelli-safe (0.3.6)
> > html5lib (0.999)
> > Mezzanine (3.0.9)
> > oauthlib (0.6.1)
> > Pillow (2.3.0)
> > pip (1.5.4)
> > pisa (3.0.33)
> > pytz (2013.9)
> > reportlab (3.0)
> > requests (2.2.1)
> > requests-oauthlib (0.4.0)
> > setuptools (2.2)
> > six (1.5.2)
> > tzlocal (1.0)
> >
> >
> > On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
> >
> > On 27/02/2014 7:29 AM, Tom Brander wrote:
> > > Went to create a pdf invoice and got this error:
> > > I am using Python #.3 if that makes a diff??
> > > Does not give me much to go on the "view" invoice is working
> fine...
> >
> > Can you do a pip list for us?
> >
> > Do you have pisa and reportlab both installed? What versions?
> >
> >
> > >
> > > Traceback:
> > > File
> > >
> >
> "/home/tom/myvenv3/lib/python3.3/site-packages/django/core/handlers/base.py"
>
> >
> > > in get_response
> > >107. response = middleware_method(request,
> > > callback, callback_args, callback_kwargs)
> > > File
> > >
> >
> "/home/tom/myvenv3/lib/python3.3/site-packages/mezzanine/pages/middleware.py"
>
> >
> > > in process_view
> > >78. response = view_func(request, *view_args,
> > **view_kwargs)
> > > File
> > >
> >
> "/home/tom/myvenv3/lib/python3.3/site-packages/cartridge/shop/views.py"
> > > in invoice
> > >358. import ho.pisa
> > > File
> > "/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py"
> > > in
> > >26. from sx.pisa3.pisa import *
> > >
> > > Exception Type: SyntaxError at /shop/invoice/1/
> > > Exception Value: invalid syntax (__init__.py, line 43)
> > >
> > > --
> > > 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/groups/opt_out
> > .
> >
> >
> >
> > --
> > Email: mol...@gmail.com
> >
>
>
>
> --
> Email: mol...@gmail.com
>
--
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/groups/opt_out.
[mezzanine-users] Mezzanine Multiple Content Blocks per Page
Hey guys, I saw in a Mezzanine demo video on youtube that you can have multiple content segments per page. How is this achieved? I couldn't find any doc for it, maybe because I don't know what the feature is called. Thanks! -- 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/groups/opt_out.
Re: [mezzanine-users] Mezzanine Multiple Content Blocks per Page
Hi Radomir, There are a couple of projects listed on the Mezzanine home page. I have never used those. I roll my own solutions based on the needs. Mezzanine uses Django's template system. Mezzanine Page objects can have "child" pages. I leverage that relationship to create far more complex solutions than any of the content-block applications out there. hth, ken On Thu, Feb 27, 2014 at 12:38 PM, Radomir Wojcik wrote: > Hey guys, > > I saw in a Mezzanine demo video on youtube that you can have multiple > content segments per page. How is this achieved? I couldn't find any doc > for it, maybe because I don't know what the feature is called. > > Thanks! > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
[mezzanine-users] Re: Mezzanine Multiple Content Blocks per Page
Ah so its an add-on or purely custom. I thought this was a feature that is already built in to Mez. If it isn't, it should. So when I am editing pages I can edit a smaller chunk rather than the whole page. Plus the vanilla editor makes a mess of the html so you easily get lost in the markup. -- 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/groups/opt_out.
Re: [mezzanine-users] Re: Mezzanine Multiple Content Blocks per Page
Try https://github.com/renyi/mezzanine-blocks. On Thu, Feb 27, 2014 at 1:36 PM, Radomir Wojcik wrote: > I thought this was a feature that is already built in to Mez. If it isn't, it should. -1. Content blocks are a feature best left outside of Mezzanine. I admire and appreciate how lean Mezzanine remains. 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/groups/opt_out.
Re: [mezzanine-users] Re: Mezzanine Multiple Content Blocks per Page
> > Cool thanks! -- 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/groups/opt_out.
[mezzanine-users] HOST_THEMES working sample
So after working with the django sites framework, I see how easy it is to have multiple sites running Mezzanine in one instance. It works great if you have a multiple language site and don't want to use the internationalization built into Django and instead create a separate site where the skin/theme remains the same. I would love to see a working example of HOST_THEMES though as I couldn't get this to work. If someone can post an easy, clonable github example using localhost and 127.0.0.1 to make it simple it would I think benefit the whole Mezzanine community! -- 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/groups/opt_out.
Re: [mezzanine-users] HOST_THEMES working sample
This docs PR doesn't have a working example for localhost, but is at least an attempt at documenting the process for HOST_THEMES: https://github.com/stephenmcd/mezzanine/pull/961. Comments welcome on that PR. Jeff On Feb 27, 2014, at 2:18 PM, Radomir Wojcik wrote: > So after working with the django sites framework, I see how easy it is to > have multiple sites running Mezzanine in one instance. It works great if you > have a multiple language site and don't want to use the internationalization > built into Django and instead create a separate site where the skin/theme > remains the same. > > > I would love to see a working example of HOST_THEMES though as I couldn't get > this to work. If someone can post an easy, clonable github example using > localhost and 127.0.0.1 to make it simple it would I think benefit the whole > Mezzanine community! > > -- > 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] HOST_THEMES working sample
> > I was already past that point, the docs help, I relied on peoples examples > from the mailing list. If I post a non-working example would someone be > able to fork it, fix it , tell me why it wasn't working? The doc here also > doesn't talk about base.html , Both of my themes have different base.html > files which is pretty much all I need for the differences in the skins. > -- 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/groups/opt_out.
Re: [mezzanine-users] Re: deployment issue --- gunicorn
I confirm that this solved the same problem. More info here:
http://gunicorn-docs.readthedocs.org/en/latest/configure.html#configuration-file
It's been fixed two months ago:
https://github.com/stephenmcd/mezzanine/issues/870
Il giorno giovedì 16 gennaio 2014 12:35:58 UTC+1, Klamann, Norbert ha
scritto:
>
> I repeated the whole exercise and now it works .
>
> gunicorn.conf.py is changed an looks like that.
>
> mezzanine@wsa02:~/mezz_test/project$ cat gunicorn.conf.py
>
> from __future__ import unicode_literals
> import multiprocessing
> bind = "127.0.0.1:8000"
> workers = multiprocessing.cpu_count() * 2 + 1
> loglevel = "error"
> proc_name = "mezz_test"
>
> Now I get a Error 500 when I visit the new instance but that is another
> problem i presume.
>
>
> Thanks for your help
>
> Norbert
>
>
>
>
>
>
> 2014/1/16 Stephen McDonald >
>
>> Thanks Harry
>>
>> FWIW my successful test used 8000 for the gunicorn port.
>>
>>
>> On Thu, Jan 16, 2014 at 11:32 AM, >wrote:
>>
>>> At least for the most basic deployment of mezzanine (ie. no custom theme
>>> app yet) I seem to have resolved the issue.
>>>
>>> Although I did a few different things, I think that the major factor was
>>> changing the gunicorn port from 8000 to anything else (8001, ).
>>>
>>> I'll keep you posted as to whether this moment of success persists.
>>>
>>> Harry
>>>
>>>
>>> On Friday, 10 January 2014 13:41:31 UTC+8, har...@iinet.net.au wrote:
>>>
Hi,
I'm very new to Mezzanine and have been loving it --- especially the
fabric deploment. However, I seem to be having some troubles with
gunicorn.
I started from a fresh linode running debian and allowed 'fab all' to
build the full system.
I would very much appreciate some assistance with this.
My basic process is:
server:
new linode profile
ssh as root
adduser user
apt-get install sudo vim
add harry to sudoers file
on local machine:
ssh-copy-id -i ~/.ssh/id_rsa.pub
sudo pip install virtualenvwrapper
add to bashrc:
export WORKON_HOME=$HOME/.virtualenvs
source /usr/local/bin/virtualenvwrapper.sh
export PIP_VIRTUALENV_BASE=$WORKON_HOME
local:
mkvirtualenv black_earth_{project}
pip install -r requirements.txt
createdb {project}
mezzanine-project {project}
set database parameters in local_settings.py
copy keys and deploy setting (FABRIC) to local_settings.py
set allowed_hosts in settings.py
ALLOWED_HOSTS = [
'localhosts',
'.mysite.org.au',
]
python manage.py createdb
check local server
set up git repository
git init
git add .
git git remote add origin {gitserver}
git push -u origin master
pip freeze > requirements.txt
fab all
pip error:
sudo pip install setuptools --no-use-wheel --upgrade
At the final point in the deployment --- restart --- I get the error:
$ supervisorctl start black_earth_semina:gunicorn_black_earth_semina ->
[blackearthcollective.org.au] out: sudo password:
[blackearthcollective.org.au] out:
black_earth_semina:gunicorn_black_earth_semina:
ERROR (abnormal termination)
[blackearthcollective.org.au] out:
This is with a completely standard mezzanine setup. I thought that the
problem was with my theme project.
from the supervisor gunicorn log:
!!!
!!! WARNING: This command is deprecated.
!!!
!!! You should now run your application with the WSGI interface
!!! installed with your project. Ex.:
!!!
!!! gunicorn myproject.wsgi:application
!!!
!!! See https://docs.djangoproject.com/en/1.4/howto/deployment/
wsgi/gunicorn/
!!! for more info.
!!!
2014-01-10 01:16:35 [12088] [CRITICAL] WORKER TIMEOUT (pid:12097)
>>> --
>>> 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/groups/opt_out.
>>>
>>
>>
>>
>> --
>> Stephen McDonald
>> http://jupo.org
>>
>> --
>> 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/Ltmdrd3D2aw/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> mezzanine-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
--
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...@goog
Re: [mezzanine-users] HOST_THEMES working sample
It's really went written Jeff, thanks a lot. Will definitely merge in soon. On Fri, Feb 28, 2014 at 8:19 AM, Jeff Pittman wrote: > This docs PR doesn't have a working example for localhost, but is at least > an attempt at documenting the process for HOST_THEMES: > https://github.com/stephenmcd/mezzanine/pull/961. Comments welcome on > that PR. > > Jeff > > On Feb 27, 2014, at 2:18 PM, Radomir Wojcik wrote: > > So after working with the django sites framework, I see how easy it is to > have multiple sites running Mezzanine in one instance. It works great if > you have a multiple language site and don't want to use the > internationalization built into Django and instead create a separate site > where the skin/theme remains the same. > > > I would love to see a working example of HOST_THEMES though as I couldn't > get this to work. If someone can post an easy, clonable github example > using localhost and 127.0.0.1 to make it simple it would I think benefit > the whole Mezzanine community! > > -- > 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/groups/opt_out. > > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
Re: [mezzanine-users] Re: deployment issue --- gunicorn
Thanks Federico, I never stopped to realise that fix matched up with that
issue - good to know!
On Fri, Feb 28, 2014 at 10:42 AM, Federico Bruni wrote:
> I confirm that this solved the same problem. More info here:
>
> http://gunicorn-docs.readthedocs.org/en/latest/configure.html#configuration-file
>
> It's been fixed two months ago:
> https://github.com/stephenmcd/mezzanine/issues/870
>
>
> Il giorno giovedì 16 gennaio 2014 12:35:58 UTC+1, Klamann, Norbert ha
> scritto:
>>
>> I repeated the whole exercise and now it works .
>>
>> gunicorn.conf.py is changed an looks like that.
>>
>> mezzanine@wsa02:~/mezz_test/project$ cat gunicorn.conf.py
>>
>> from __future__ import unicode_literals
>> import multiprocessing
>> bind = "127.0.0.1:8000"
>> workers = multiprocessing.cpu_count() * 2 + 1
>> loglevel = "error"
>> proc_name = "mezz_test"
>>
>> Now I get a Error 500 when I visit the new instance but that is another
>> problem i presume.
>>
>>
>> Thanks for your help
>>
>> Norbert
>>
>>
>>
>>
>>
>>
>> 2014/1/16 Stephen McDonald
>>
>>> Thanks Harry
>>>
>>> FWIW my successful test used 8000 for the gunicorn port.
>>>
>>>
>>> On Thu, Jan 16, 2014 at 11:32 AM, wrote:
>>>
At least for the most basic deployment of mezzanine (ie. no custom
theme app yet) I seem to have resolved the issue.
Although I did a few different things, I think that the major factor
was changing the gunicorn port from 8000 to anything else (8001, ).
I'll keep you posted as to whether this moment of success persists.
Harry
On Friday, 10 January 2014 13:41:31 UTC+8, har...@iinet.net.au wrote:
>
> Hi,
>
> I'm very new to Mezzanine and have been loving it --- especially the
> fabric deploment. However, I seem to be having some troubles with
> gunicorn.
>
> I started from a fresh linode running debian and allowed 'fab all' to
> build the full system.
>
> I would very much appreciate some assistance with this.
>
> My basic process is:
>
> server:
>
> new linode profile
> ssh as root
> adduser user
> apt-get install sudo vim
> add harry to sudoers file
> on local machine:
> ssh-copy-id -i ~/.ssh/id_rsa.pub
> sudo pip install virtualenvwrapper
> add to bashrc:
>
> export WORKON_HOME=$HOME/.virtualenvs
> source /usr/local/bin/virtualenvwrapper.sh
> export PIP_VIRTUALENV_BASE=$WORKON_HOME
>
> local:
>
> mkvirtualenv black_earth_{project}
> pip install -r requirements.txt
> createdb {project}
> mezzanine-project {project}
> set database parameters in local_settings.py
> copy keys and deploy setting (FABRIC) to local_settings.py
> set allowed_hosts in settings.py
> ALLOWED_HOSTS = [
> 'localhosts',
> '.mysite.org.au',
> ]
> python manage.py createdb
> check local server
> set up git repository
> git init
> git add .
> git git remote add origin {gitserver}
> git push -u origin master
> pip freeze > requirements.txt
> fab all
>
> pip error:
> sudo pip install setuptools --no-use-wheel --upgrade
>
> At the final point in the deployment --- restart --- I get the error:
>
> $ supervisorctl start black_earth_semina:gunicorn_black_earth_semina
> ->
>
> [blackearthcollective.org.au] out: sudo password:
> [blackearthcollective.org.au] out:
> black_earth_semina:gunicorn_black_earth_semina:
> ERROR (abnormal termination)
> [blackearthcollective.org.au] out:
>
> This is with a completely standard mezzanine setup. I thought that
> the problem was with my theme project.
>
> from the supervisor gunicorn log:
>
> !!!
> !!! WARNING: This command is deprecated.
> !!!
> !!! You should now run your application with the WSGI interface
> !!! installed with your project. Ex.:
> !!!
> !!! gunicorn myproject.wsgi:application
> !!!
> !!! See https://docs.djangoproject.com/en/1.4/howto/deployment/
> wsgi/gunicorn/
> !!! for more info.
> !!!
>
> 2014-01-10 01:16:35 [12088] [CRITICAL] WORKER TIMEOUT (pid:12097)
>
--
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/groups/opt_out.
>>>
>>>
>>>
>>> --
>>> Stephen McDonald
>>> http://jupo.org
>>>
>>> --
>>> 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/Ltmdrd3D2aw/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> mezzanine-use...@go
Re: [mezzanine-users] first steps with fabric deployment
2014-02-26 13:18 GMT+01:00 : > Yes, I think fab create has to restart from the beginning. One more > advice, be sure that all Fabric settings in settings.py are completed (or > as much as you can). I tried to leave the field REPO_URL empty and fab > deploy didn't work until I set a real git repository. Yes, I see that each time you run 'fab deploy' the git repository is checked and pulled to get the updates. I've followed your advice, added as many settings as possible and solved an issue with the gunicorn file, see: https://github.com/stephenmcd/mezzanine/issues/870 Now the server is serving the contents, but... the database is still wrong. All the static and theme files are correct (favicon, homepage), but all the rest (other pages and access to admin) is wrong. Something went wrong with manage.py migrate. How can I find the problem? In the output I see many "Nothing to migrate". -- 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/groups/opt_out.
Re: [mezzanine-users] Re: deployment issue --- gunicorn
If the commit or the pull request message contains a reference to the issue
#number, then they will be linked each other. See:
https://help.github.com/articles/closing-issues-via-commit-messages
2014-02-28 1:03 GMT+01:00 Stephen McDonald :
> Thanks Federico, I never stopped to realise that fix matched up with that
> issue - good to know!
>
>
> On Fri, Feb 28, 2014 at 10:42 AM, Federico Bruni wrote:
>
>> I confirm that this solved the same problem. More info here:
>>
>> http://gunicorn-docs.readthedocs.org/en/latest/configure.html#configuration-file
>>
>> It's been fixed two months ago:
>> https://github.com/stephenmcd/mezzanine/issues/870
>>
>>
>> Il giorno giovedì 16 gennaio 2014 12:35:58 UTC+1, Klamann, Norbert ha
>> scritto:
>>>
>>> I repeated the whole exercise and now it works .
>>>
>>> gunicorn.conf.py is changed an looks like that.
>>>
>>> mezzanine@wsa02:~/mezz_test/project$ cat gunicorn.conf.py
>>>
>>> from __future__ import unicode_literals
>>> import multiprocessing
>>> bind = "127.0.0.1:8000"
>>> workers = multiprocessing.cpu_count() * 2 + 1
>>> loglevel = "error"
>>> proc_name = "mezz_test"
>>>
>>> Now I get a Error 500 when I visit the new instance but that is another
>>> problem i presume.
>>>
>>>
>>> Thanks for your help
>>>
>>> Norbert
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2014/1/16 Stephen McDonald
>>>
Thanks Harry
FWIW my successful test used 8000 for the gunicorn port.
On Thu, Jan 16, 2014 at 11:32 AM, wrote:
> At least for the most basic deployment of mezzanine (ie. no custom
> theme app yet) I seem to have resolved the issue.
>
> Although I did a few different things, I think that the major factor
> was changing the gunicorn port from 8000 to anything else (8001, ).
>
> I'll keep you posted as to whether this moment of success persists.
>
> Harry
>
>
> On Friday, 10 January 2014 13:41:31 UTC+8, har...@iinet.net.au wrote:
>
>>
>> Hi,
>>
>> I'm very new to Mezzanine and have been loving it --- especially the
>> fabric deploment. However, I seem to be having some troubles with
>> gunicorn.
>>
>> I started from a fresh linode running debian and allowed 'fab all' to
>> build the full system.
>>
>> I would very much appreciate some assistance with this.
>>
>> My basic process is:
>>
>> server:
>>
>> new linode profile
>> ssh as root
>> adduser user
>> apt-get install sudo vim
>> add harry to sudoers file
>> on local machine:
>> ssh-copy-id -i ~/.ssh/id_rsa.pub
>> sudo pip install virtualenvwrapper
>> add to bashrc:
>>
>> export WORKON_HOME=$HOME/.virtualenvs
>> source /usr/local/bin/virtualenvwrapper.sh
>> export PIP_VIRTUALENV_BASE=$WORKON_HOME
>>
>> local:
>>
>> mkvirtualenv black_earth_{project}
>> pip install -r requirements.txt
>> createdb {project}
>> mezzanine-project {project}
>> set database parameters in local_settings.py
>> copy keys and deploy setting (FABRIC) to local_settings.py
>> set allowed_hosts in settings.py
>> ALLOWED_HOSTS = [
>> 'localhosts',
>> '.mysite.org.au',
>> ]
>> python manage.py createdb
>> check local server
>> set up git repository
>> git init
>> git add .
>> git git remote add origin {gitserver}
>> git push -u origin master
>> pip freeze > requirements.txt
>> fab all
>>
>> pip error:
>> sudo pip install setuptools --no-use-wheel --upgrade
>>
>> At the final point in the deployment --- restart --- I get the error:
>>
>> $ supervisorctl start black_earth_semina:gunicorn_black_earth_semina
>> ->
>>
>> [blackearthcollective.org.au] out: sudo password:
>> [blackearthcollective.org.au] out:
>> black_earth_semina:gunicorn_black_earth_semina:
>> ERROR (abnormal termination)
>> [blackearthcollective.org.au] out:
>>
>> This is with a completely standard mezzanine setup. I thought that
>> the problem was with my theme project.
>>
>> from the supervisor gunicorn log:
>>
>> !!!
>> !!! WARNING: This command is deprecated.
>> !!!
>> !!! You should now run your application with the WSGI interface
>> !!! installed with your project. Ex.:
>> !!!
>> !!! gunicorn myproject.wsgi:application
>> !!!
>> !!! See https://docs.djangoproject.com/en/1.4/howto/deployment/
>> wsgi/gunicorn/
>> !!! for more info.
>> !!!
>>
>> 2014-01-10 01:16:35 [12088] [CRITICAL] WORKER TIMEOUT (pid:12097)
>>
> --
> 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/groups/opt_out.
>
>>
Re: [mezzanine-users] Error with Pisa? P3?
Tried to used the fix suggested but still getting the same error (FWIW I
never did get the message version 2.2 or higher needed),, so I'm suspecting
pisa is a no go with Python 3 and that it is simply failing??
Posted question in the xhtml2pdf group, linked below:
https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
Error:
Exception Value:
invalid syntax (__init__.py, line 43)
Exception
Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
in , line 26Python Executable:/home/tom/myvenv3/bin/pythonPython
Version:3.3.2
On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
>
> Thanks so much!! now I know where to look..
>
> BTW Shouldn't both reportlab and pillow be in the requirements txt file??
> They were the only two I needed to download separately..
>
> On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
>>
>> The error is coming from sx/pisa3/__init__.py, line 43 which says:
>>
>> {{{
>> if not REPORTLAB22:
>> raise ImportError, "Reportlab Toolkit Version 2.2 or higher
>> needed"
>> }}}
>>
>> Now, obviously you do have reportlab of a version higher than 2.2 but
>> there was a bug mentioned on the cartridge issues a few weeks ago which
>> seemed to indicate that reportlab 3.0 isn't reporting its version
>> correctly as higher than 2.2.
>>
>> See
>> https://github.com/stephenmcd/cartridge/issues/174#issuecomment-35755887
>>
>> It seems like it's a known bug in pisa.
>>
>> Hope this helps.
>>
>> Seeya. Danny.
>>
>> On 27/02/2014 9:52 AM, Tom Brander wrote:
>> > Hmm did not have reportlab, so I installed it but no change, here is
>> the
>> > pip list
>> > (myvenv3) tom@tom-sam:~/whiteplume$ pip list
>> > bleach (1.4)
>> > Cartridge (0.9.2)
>> > Django (1.6.2)
>> > filebrowser-safe (0.3.2)
>> > future (0.9.0)
>> > grappelli-safe (0.3.6)
>> > html5lib (0.999)
>> > Mezzanine (3.0.9)
>> > oauthlib (0.6.1)
>> > Pillow (2.3.0)
>> > pip (1.5.4)
>> > pisa (3.0.33)
>> > pytz (2013.9)
>> > reportlab (3.0)
>> > requests (2.2.1)
>> > requests-oauthlib (0.4.0)
>> > setuptools (2.2)
>> > six (1.5.2)
>> > tzlocal (1.0)
>> >
>> >
>> > On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
>> >
>> > On 27/02/2014 7:29 AM, Tom Brander wrote:
>> > > Went to create a pdf invoice and got this error:
>> > > I am using Python #.3 if that makes a diff??
>> > > Does not give me much to go on the "view" invoice is working
>> fine...
>> >
>> > Can you do a pip list for us?
>> >
>> > Do you have pisa and reportlab both installed? What versions?
>> >
>> >
>> > >
>> > > Traceback:
>> > > File
>> > >
>> >
>> "/home/tom/myvenv3/lib/python3.3/site-packages/django/core/handlers/base.py"
>>
>> >
>> > > in get_response
>> > >107. response =
>> middleware_method(request,
>> > > callback, callback_args, callback_kwargs)
>> > > File
>> > >
>> >
>> "/home/tom/myvenv3/lib/python3.3/site-packages/mezzanine/pages/middleware.py"
>>
>>
>> >
>> > > in process_view
>> > >78. response = view_func(request, *view_args,
>> > **view_kwargs)
>> > > File
>> > >
>> >
>> "/home/tom/myvenv3/lib/python3.3/site-packages/cartridge/shop/views.py"
>> > > in invoice
>> > >358. import ho.pisa
>> > > File
>> > "/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py"
>> > > in
>> > >26. from sx.pisa3.pisa import *
>> > >
>> > > Exception Type: SyntaxError at /shop/invoice/1/
>> > > Exception Value: invalid syntax (__init__.py, line 43)
>> > >
>> > > --
>> > > 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/groups/opt_out
>> > .
>> >
>> >
>> >
>> > --
>> > Email: mol...@gmail.com
>> >
>>
>>
>>
>> --
>> Email: mol...@gmail.com
>>
>
--
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/groups/opt_out.
Re: [mezzanine-users] Error with Pisa? P3?
Best option for now is to downgrade reportlab to 2.7 (I did that on my site
this morning, after this discussion!)
Just add reportlab==2.7 to your requirements/project.txt and do a pip
install -U -r requirements/project.txt
Seeya. Danny.
On 28 February 2014 10:45, Tom Brander wrote:
> Tried to used the fix suggested but still getting the same error (FWIW I
> never did get the message version 2.2 or higher needed),, so I'm suspecting
> pisa is a no go with Python 3 and that it is simply failing??
>
>
>
> Posted question in the xhtml2pdf group, linked below:
>
> https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
>
> Error:
> Exception Value:
>
> invalid syntax (__init__.py, line 43)
>
> Exception
> Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
> in , line 26 Python Executable:/home/tom/myvenv3/bin/pythonPython
> Version: 3.3.2
>
> On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
>>
>> Thanks so much!! now I know where to look..
>>
>> BTW Shouldn't both reportlab and pillow be in the requirements txt file??
>> They were the only two I needed to download separately..
>>
>> On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
>>>
>>> The error is coming from sx/pisa3/__init__.py, line 43 which says:
>>>
>>> {{{
>>> if not REPORTLAB22:
>>> raise ImportError, "Reportlab Toolkit Version 2.2 or higher
>>> needed"
>>> }}}
>>>
>>> Now, obviously you do have reportlab of a version higher than 2.2 but
>>> there was a bug mentioned on the cartridge issues a few weeks ago which
>>> seemed to indicate that reportlab 3.0 isn't reporting its version
>>> correctly as higher than 2.2.
>>>
>>> See https://github.com/stephenmcd/cartridge/issues/174#
>>> issuecomment-35755887
>>>
>>> It seems like it's a known bug in pisa.
>>>
>>> Hope this helps.
>>>
>>> Seeya. Danny.
>>>
>>> On 27/02/2014 9:52 AM, Tom Brander wrote:
>>> > Hmm did not have reportlab, so I installed it but no change, here is
>>> the
>>> > pip list
>>> > (myvenv3) tom@tom-sam:~/whiteplume$ pip list
>>> > bleach (1.4)
>>> > Cartridge (0.9.2)
>>> > Django (1.6.2)
>>> > filebrowser-safe (0.3.2)
>>> > future (0.9.0)
>>> > grappelli-safe (0.3.6)
>>> > html5lib (0.999)
>>> > Mezzanine (3.0.9)
>>> > oauthlib (0.6.1)
>>> > Pillow (2.3.0)
>>> > pip (1.5.4)
>>> > pisa (3.0.33)
>>> > pytz (2013.9)
>>> > reportlab (3.0)
>>> > requests (2.2.1)
>>> > requests-oauthlib (0.4.0)
>>> > setuptools (2.2)
>>> > six (1.5.2)
>>> > tzlocal (1.0)
>>> >
>>> >
>>> > On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
>>> >
>>> > On 27/02/2014 7:29 AM, Tom Brander wrote:
>>> > > Went to create a pdf invoice and got this error:
>>> > > I am using Python #.3 if that makes a diff??
>>> > > Does not give me much to go on the "view" invoice is working
>>> fine...
>>> >
>>> > Can you do a pip list for us?
>>> >
>>> > Do you have pisa and reportlab both installed? What versions?
>>> >
>>> >
>>> > >
>>> > > Traceback:
>>> > > File
>>> > >
>>> >
>>> > "/home/tom/myvenv3/lib/python3.3/site-packages/django/core/handlers/base.py"
>>>
>>> >
>>> > > in get_response
>>> > >107. response =
>>> middleware_method(request,
>>> > > callback, callback_args, callback_kwargs)
>>> > > File
>>> > >
>>> >
>>> > "/home/tom/myvenv3/lib/python3.3/site-packages/mezzanine/pages/middleware.py"
>>>
>>> >
>>> > > in process_view
>>> > >78. response = view_func(request, *view_args,
>>> > **view_kwargs)
>>> > > File
>>> > >
>>> >
>>> > "/home/tom/myvenv3/lib/python3.3/site-packages/cartridge/shop/views.py"
>>>
>>> > > in invoice
>>> > >358. import ho.pisa
>>> > > File
>>> > "/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py"
>>>
>>> > > in
>>> > >26. from sx.pisa3.pisa import *
>>> > >
>>> > > Exception Type: SyntaxError at /shop/invoice/1/
>>> > > Exception Value: invalid syntax (__init__.py, line 43)
>>> > >
>>> > > --
>>> > > 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/
>>> groups/opt_out
>>> > .
>>> >
>>> >
>>> >
>>> > --
>>> > Email: mol...@gmail.com
>>> >
>>>
>>>
>>>
>>> --
>>> Email: mol...@gmail.com
>>>
>>
--
molo...@gmail.com
--
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/groups/opt_out.
Re: [mezzanine-users] Error with Pisa? P3?
Thanks Danny - I'm not really across the issue, do you think we need to
specify that exact reportlab version in Cartridge's setup.py?
On Fri, Feb 28, 2014 at 11:17 AM, Danny wrote:
> Best option for now is to downgrade reportlab to 2.7 (I did that on my
> site this morning, after this discussion!)
>
> Just add reportlab==2.7 to your requirements/project.txt and do a pip
> install -U -r requirements/project.txt
>
> Seeya. Danny.
>
>
> On 28 February 2014 10:45, Tom Brander wrote:
>
>> Tried to used the fix suggested but still getting the same error (FWIW I
>> never did get the message version 2.2 or higher needed),, so I'm suspecting
>> pisa is a no go with Python 3 and that it is simply failing??
>>
>>
>>
>> Posted question in the xhtml2pdf group, linked below:
>>
>> https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
>>
>> Error:
>> Exception Value:
>>
>> invalid syntax (__init__.py, line 43)
>>
>> Exception
>> Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
>> in , line 26 Python Executable:/home/tom/myvenv3/bin/pythonPython
>> Version:
>> 3.3.2
>>
>> On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
>>>
>>> Thanks so much!! now I know where to look..
>>>
>>> BTW Shouldn't both reportlab and pillow be in the requirements txt
>>> file?? They were the only two I needed to download separately..
>>>
>>> On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
The error is coming from sx/pisa3/__init__.py, line 43 which says:
{{{
if not REPORTLAB22:
raise ImportError, "Reportlab Toolkit Version 2.2 or higher
needed"
}}}
Now, obviously you do have reportlab of a version higher than 2.2 but
there was a bug mentioned on the cartridge issues a few weeks ago which
seemed to indicate that reportlab 3.0 isn't reporting its version
correctly as higher than 2.2.
See https://github.com/stephenmcd/cartridge/issues/174#
issuecomment-35755887
It seems like it's a known bug in pisa.
Hope this helps.
Seeya. Danny.
On 27/02/2014 9:52 AM, Tom Brander wrote:
> Hmm did not have reportlab, so I installed it but no change, here is
the
> pip list
> (myvenv3) tom@tom-sam:~/whiteplume$ pip list
> bleach (1.4)
> Cartridge (0.9.2)
> Django (1.6.2)
> filebrowser-safe (0.3.2)
> future (0.9.0)
> grappelli-safe (0.3.6)
> html5lib (0.999)
> Mezzanine (3.0.9)
> oauthlib (0.6.1)
> Pillow (2.3.0)
> pip (1.5.4)
> pisa (3.0.33)
> pytz (2013.9)
> reportlab (3.0)
> requests (2.2.1)
> requests-oauthlib (0.4.0)
> setuptools (2.2)
> six (1.5.2)
> tzlocal (1.0)
>
>
> On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
>
> On 27/02/2014 7:29 AM, Tom Brander wrote:
> > Went to create a pdf invoice and got this error:
> > I am using Python #.3 if that makes a diff??
> > Does not give me much to go on the "view" invoice is working
fine...
>
> Can you do a pip list for us?
>
> Do you have pisa and reportlab both installed? What versions?
>
>
> >
> > Traceback:
> > File
> >
>
> "/home/tom/myvenv3/lib/python3.3/site-packages/django/core/handlers/base.py"
>
> > in get_response
> >107. response =
middleware_method(request,
> > callback, callback_args, callback_kwargs)
> > File
> >
>
> "/home/tom/myvenv3/lib/python3.3/site-packages/mezzanine/pages/middleware.py"
>
> > in process_view
> >78. response = view_func(request, *view_args,
> **view_kwargs)
> > File
> >
>
> "/home/tom/myvenv3/lib/python3.3/site-packages/cartridge/shop/views.py"
> > in invoice
> >358. import ho.pisa
> > File
> "/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py"
> > in
> >26. from sx.pisa3.pisa import *
> >
> > Exception Type: SyntaxError at /shop/invoice/1/
> > Exception Value: invalid syntax (__init__.py, line 43)
> >
> > --
> > 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/
groups/opt_out
> .
>
>
>
> --
> Email: mol...@gmail.com
>
--
Emai
Re: [mezzanine-users] Error with Pisa? P3?
I'd say so, Stephen, at least until cartridge can be updated to use
xhtml2pdf instead of pisa (which seems to be an abandoned project).
At the moment, there's no dependency on reportlab in cartridge (only pisa),
but because pisa doesn't have reportlab in its own dependency list, it
couldn't hurt specifying the versions that cartridge needs.
I'll create a pull request, if you like?
Seeya. Danny.
On 28 February 2014 10:49, Stephen McDonald wrote:
> Thanks Danny - I'm not really across the issue, do you think we need to
> specify that exact reportlab version in Cartridge's setup.py?
>
>
> On Fri, Feb 28, 2014 at 11:17 AM, Danny wrote:
>
>> Best option for now is to downgrade reportlab to 2.7 (I did that on my
>> site this morning, after this discussion!)
>>
>> Just add reportlab==2.7 to your requirements/project.txt and do a pip
>> install -U -r requirements/project.txt
>>
>> Seeya. Danny.
>>
>>
>> On 28 February 2014 10:45, Tom Brander wrote:
>>
>>> Tried to used the fix suggested but still getting the same error (FWIW
>>> I never did get the message version 2.2 or higher needed),, so I'm
>>> suspecting pisa is a no go with Python 3 and that it is simply failing??
>>>
>>>
>>>
>>> Posted question in the xhtml2pdf group, linked below:
>>>
>>> https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
>>>
>>> Error:
>>> Exception Value:
>>>
>>> invalid syntax (__init__.py, line 43)
>>>
>>> Exception
>>> Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
>>> in , line 26 Python Executable:/home/tom/myvenv3/bin/pythonPython
>>> Version:
>>> 3.3.2
>>>
>>> On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
Thanks so much!! now I know where to look..
BTW Shouldn't both reportlab and pillow be in the requirements txt
file?? They were the only two I needed to download separately..
On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
>
> The error is coming from sx/pisa3/__init__.py, line 43 which says:
>
> {{{
> if not REPORTLAB22:
> raise ImportError, "Reportlab Toolkit Version 2.2 or higher
> needed"
> }}}
>
> Now, obviously you do have reportlab of a version higher than 2.2 but
> there was a bug mentioned on the cartridge issues a few weeks ago
> which
> seemed to indicate that reportlab 3.0 isn't reporting its version
> correctly as higher than 2.2.
>
> See https://github.com/stephenmcd/cartridge/issues/174#
> issuecomment-35755887
>
> It seems like it's a known bug in pisa.
>
> Hope this helps.
>
> Seeya. Danny.
>
> On 27/02/2014 9:52 AM, Tom Brander wrote:
> > Hmm did not have reportlab, so I installed it but no change, here is
> the
> > pip list
> > (myvenv3) tom@tom-sam:~/whiteplume$ pip list
> > bleach (1.4)
> > Cartridge (0.9.2)
> > Django (1.6.2)
> > filebrowser-safe (0.3.2)
> > future (0.9.0)
> > grappelli-safe (0.3.6)
> > html5lib (0.999)
> > Mezzanine (3.0.9)
> > oauthlib (0.6.1)
> > Pillow (2.3.0)
> > pip (1.5.4)
> > pisa (3.0.33)
> > pytz (2013.9)
> > reportlab (3.0)
> > requests (2.2.1)
> > requests-oauthlib (0.4.0)
> > setuptools (2.2)
> > six (1.5.2)
> > tzlocal (1.0)
> >
> >
> > On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
> >
> > On 27/02/2014 7:29 AM, Tom Brander wrote:
> > > Went to create a pdf invoice and got this error:
> > > I am using Python #.3 if that makes a diff??
> > > Does not give me much to go on the "view" invoice is working
> fine...
> >
> > Can you do a pip list for us?
> >
> > Do you have pisa and reportlab both installed? What versions?
> >
> >
> > >
> > > Traceback:
> > > File
> > >
> >
> > "/home/tom/myvenv3/lib/python3.3/site-packages/django/core/handlers/base.py"
>
> >
> > > in get_response
> > >107. response =
> middleware_method(request,
> > > callback, callback_args, callback_kwargs)
> > > File
> > >
> >
> > "/home/tom/myvenv3/lib/python3.3/site-packages/mezzanine/pages/middleware.py"
>
> >
> > > in process_view
> > >78. response = view_func(request, *view_args,
> > **view_kwargs)
> > > File
> > >
> >
> > "/home/tom/myvenv3/lib/python3.3/site-packages/cartridge/shop/views.py"
>
> > > in invoice
> > >358. import ho.pisa
> > > File
> > "/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py"
>
> > > in
> > >26. from sx.pisa3.pisa import *
> > >
> > > Exception Type: SyntaxError at /shop/invoice/1/
> > > Exception Value: inva
Re: [mezzanine-users] Error with Pisa? P3?
Thanks a lot that'd be great!
On Fri, Feb 28, 2014 at 11:23 AM, Danny wrote:
> I'd say so, Stephen, at least until cartridge can be updated to use
> xhtml2pdf instead of pisa (which seems to be an abandoned project).
>
> At the moment, there's no dependency on reportlab in cartridge (only
> pisa), but because pisa doesn't have reportlab in its own dependency list,
> it couldn't hurt specifying the versions that cartridge needs.
>
> I'll create a pull request, if you like?
>
> Seeya. Danny.
>
>
>
> On 28 February 2014 10:49, Stephen McDonald wrote:
>
>> Thanks Danny - I'm not really across the issue, do you think we need to
>> specify that exact reportlab version in Cartridge's setup.py?
>>
>>
>> On Fri, Feb 28, 2014 at 11:17 AM, Danny wrote:
>>
>>> Best option for now is to downgrade reportlab to 2.7 (I did that on my
>>> site this morning, after this discussion!)
>>>
>>> Just add reportlab==2.7 to your requirements/project.txt and do a pip
>>> install -U -r requirements/project.txt
>>>
>>> Seeya. Danny.
>>>
>>>
>>> On 28 February 2014 10:45, Tom Brander wrote:
>>>
Tried to used the fix suggested but still getting the same error (FWIW
I never did get the message version 2.2 or higher needed),, so I'm
suspecting pisa is a no go with Python 3 and that it is simply failing??
Posted question in the xhtml2pdf group, linked below:
https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
Error:
Exception Value:
invalid syntax (__init__.py, line 43)
Exception
Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
in , line 26 Python Executable:/home/tom/myvenv3/bin/pythonPython
Version:
3.3.2
On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
>
> Thanks so much!! now I know where to look..
>
> BTW Shouldn't both reportlab and pillow be in the requirements txt
> file?? They were the only two I needed to download separately..
>
> On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
>>
>> The error is coming from sx/pisa3/__init__.py, line 43 which says:
>>
>> {{{
>> if not REPORTLAB22:
>> raise ImportError, "Reportlab Toolkit Version 2.2 or higher
>> needed"
>> }}}
>>
>> Now, obviously you do have reportlab of a version higher than 2.2 but
>> there was a bug mentioned on the cartridge issues a few weeks ago
>> which
>> seemed to indicate that reportlab 3.0 isn't reporting its version
>> correctly as higher than 2.2.
>>
>> See https://github.com/stephenmcd/cartridge/issues/174#
>> issuecomment-35755887
>>
>> It seems like it's a known bug in pisa.
>>
>> Hope this helps.
>>
>> Seeya. Danny.
>>
>> On 27/02/2014 9:52 AM, Tom Brander wrote:
>> > Hmm did not have reportlab, so I installed it but no change, here
>> is the
>> > pip list
>> > (myvenv3) tom@tom-sam:~/whiteplume$ pip list
>> > bleach (1.4)
>> > Cartridge (0.9.2)
>> > Django (1.6.2)
>> > filebrowser-safe (0.3.2)
>> > future (0.9.0)
>> > grappelli-safe (0.3.6)
>> > html5lib (0.999)
>> > Mezzanine (3.0.9)
>> > oauthlib (0.6.1)
>> > Pillow (2.3.0)
>> > pip (1.5.4)
>> > pisa (3.0.33)
>> > pytz (2013.9)
>> > reportlab (3.0)
>> > requests (2.2.1)
>> > requests-oauthlib (0.4.0)
>> > setuptools (2.2)
>> > six (1.5.2)
>> > tzlocal (1.0)
>> >
>> >
>> > On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
>> >
>> > On 27/02/2014 7:29 AM, Tom Brander wrote:
>> > > Went to create a pdf invoice and got this error:
>> > > I am using Python #.3 if that makes a diff??
>> > > Does not give me much to go on the "view" invoice is working
>> fine...
>> >
>> > Can you do a pip list for us?
>> >
>> > Do you have pisa and reportlab both installed? What versions?
>> >
>> >
>> > >
>> > > Traceback:
>> > > File
>> > >
>> >
>> > "/home/tom/myvenv3/lib/python3.3/site-packages/django/core/handlers/base.py"
>>
>> >
>> > > in get_response
>> > >107. response =
>> middleware_method(request,
>> > > callback, callback_args, callback_kwargs)
>> > > File
>> > >
>> >
>> > "/home/tom/myvenv3/lib/python3.3/site-packages/mezzanine/pages/middleware.py"
>>
>> >
>> > > in process_view
>> > >78. response = view_func(request, *view_args,
>> > **view_kwargs)
>> > > File
>> > >
>> >
>> > "/home/tom/myvenv3/lib/python3.3/site-packages/cartridge/shop/views.py"
>>
>> > > in invoice
>> > >358. import ho.pisa
>> > > File
>> > "/home/tom/myv
Re: [mezzanine-users] Error with Pisa? P3?
Tom's pointed out in a private email that he's working with Python 3, and
reportlab 2.7 won't work on Python 3.
I'm still using python 2.7, so using an older reportlab is fine for me.
Should I still go ahead with the change to cartridge's setup.py (adding
reportlab==2.7 as a dependency) or should we look at trying and solving the
larger issue?
Seeya. Danny.
On 28 February 2014 10:55, Stephen McDonald wrote:
> Thanks a lot that'd be great!
>
>
> On Fri, Feb 28, 2014 at 11:23 AM, Danny wrote:
>
>> I'd say so, Stephen, at least until cartridge can be updated to use
>> xhtml2pdf instead of pisa (which seems to be an abandoned project).
>>
>> At the moment, there's no dependency on reportlab in cartridge (only
>> pisa), but because pisa doesn't have reportlab in its own dependency list,
>> it couldn't hurt specifying the versions that cartridge needs.
>>
>> I'll create a pull request, if you like?
>>
>> Seeya. Danny.
>>
>>
>>
>> On 28 February 2014 10:49, Stephen McDonald wrote:
>>
>>> Thanks Danny - I'm not really across the issue, do you think we need to
>>> specify that exact reportlab version in Cartridge's setup.py?
>>>
>>>
>>> On Fri, Feb 28, 2014 at 11:17 AM, Danny wrote:
>>>
Best option for now is to downgrade reportlab to 2.7 (I did that on my
site this morning, after this discussion!)
Just add reportlab==2.7 to your requirements/project.txt and do a pip
install -U -r requirements/project.txt
Seeya. Danny.
On 28 February 2014 10:45, Tom Brander wrote:
> Tried to used the fix suggested but still getting the same error
> (FWIW I never did get the message version 2.2 or higher needed),, so I'm
> suspecting pisa is a no go with Python 3 and that it is simply failing??
>
>
>
> Posted question in the xhtml2pdf group, linked below:
>
> https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
>
> Error:
> Exception Value:
>
> invalid syntax (__init__.py, line 43)
>
> Exception
> Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
> in , line 26 Python Executable:/home/tom/myvenv3/bin/pythonPython
> Version:
> 3.3.2
>
> On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
>>
>> Thanks so much!! now I know where to look..
>>
>> BTW Shouldn't both reportlab and pillow be in the requirements txt
>> file?? They were the only two I needed to download separately..
>>
>> On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
>>>
>>> The error is coming from sx/pisa3/__init__.py, line 43 which says:
>>>
>>> {{{
>>> if not REPORTLAB22:
>>> raise ImportError, "Reportlab Toolkit Version 2.2 or higher
>>> needed"
>>> }}}
>>>
>>> Now, obviously you do have reportlab of a version higher than 2.2
>>> but
>>> there was a bug mentioned on the cartridge issues a few weeks ago
>>> which
>>> seemed to indicate that reportlab 3.0 isn't reporting its version
>>> correctly as higher than 2.2.
>>>
>>> See https://github.com/stephenmcd/cartridge/issues/174#
>>> issuecomment-35755887
>>>
>>> It seems like it's a known bug in pisa.
>>>
>>> Hope this helps.
>>>
>>> Seeya. Danny.
>>>
>>> On 27/02/2014 9:52 AM, Tom Brander wrote:
>>> > Hmm did not have reportlab, so I installed it but no change, here
>>> is the
>>> > pip list
>>> > (myvenv3) tom@tom-sam:~/whiteplume$ pip list
>>> > bleach (1.4)
>>> > Cartridge (0.9.2)
>>> > Django (1.6.2)
>>> > filebrowser-safe (0.3.2)
>>> > future (0.9.0)
>>> > grappelli-safe (0.3.6)
>>> > html5lib (0.999)
>>> > Mezzanine (3.0.9)
>>> > oauthlib (0.6.1)
>>> > Pillow (2.3.0)
>>> > pip (1.5.4)
>>> > pisa (3.0.33)
>>> > pytz (2013.9)
>>> > reportlab (3.0)
>>> > requests (2.2.1)
>>> > requests-oauthlib (0.4.0)
>>> > setuptools (2.2)
>>> > six (1.5.2)
>>> > tzlocal (1.0)
>>> >
>>> >
>>> > On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
>>> >
>>> > On 27/02/2014 7:29 AM, Tom Brander wrote:
>>> > > Went to create a pdf invoice and got this error:
>>> > > I am using Python #.3 if that makes a diff??
>>> > > Does not give me much to go on the "view" invoice is
>>> working fine...
>>> >
>>> > Can you do a pip list for us?
>>> >
>>> > Do you have pisa and reportlab both installed? What versions?
>>> >
>>> >
>>> > >
>>> > > Traceback:
>>> > > File
>>> > >
>>> >
>>> > "/home/tom/myvenv3/lib/python3.3/site-packages/django/core/handlers/base.py"
>>>
>>> >
>>> > > in get_response
>>> > >107. response =
>>> middleware_method(request,
>>> > > callback, callback_args,
Re: [mezzanine-users] Error with Pisa? P3?
Yep sounds good
On Fri, Feb 28, 2014 at 11:33 AM, Danny wrote:
> Tom's pointed out in a private email that he's working with Python 3, and
> reportlab 2.7 won't work on Python 3.
>
> I'm still using python 2.7, so using an older reportlab is fine for me.
>
> Should I still go ahead with the change to cartridge's setup.py (adding
> reportlab==2.7 as a dependency) or should we look at trying and solving the
> larger issue?
>
> Seeya. Danny.
>
>
>
> On 28 February 2014 10:55, Stephen McDonald wrote:
>
>> Thanks a lot that'd be great!
>>
>>
>> On Fri, Feb 28, 2014 at 11:23 AM, Danny wrote:
>>
>>> I'd say so, Stephen, at least until cartridge can be updated to use
>>> xhtml2pdf instead of pisa (which seems to be an abandoned project).
>>>
>>> At the moment, there's no dependency on reportlab in cartridge (only
>>> pisa), but because pisa doesn't have reportlab in its own dependency list,
>>> it couldn't hurt specifying the versions that cartridge needs.
>>>
>>> I'll create a pull request, if you like?
>>>
>>> Seeya. Danny.
>>>
>>>
>>>
>>> On 28 February 2014 10:49, Stephen McDonald wrote:
>>>
Thanks Danny - I'm not really across the issue, do you think we need to
specify that exact reportlab version in Cartridge's setup.py?
On Fri, Feb 28, 2014 at 11:17 AM, Danny wrote:
> Best option for now is to downgrade reportlab to 2.7 (I did that on my
> site this morning, after this discussion!)
>
> Just add reportlab==2.7 to your requirements/project.txt and do a pip
> install -U -r requirements/project.txt
>
> Seeya. Danny.
>
>
> On 28 February 2014 10:45, Tom Brander wrote:
>
>> Tried to used the fix suggested but still getting the same error
>> (FWIW I never did get the message version 2.2 or higher needed),, so I'm
>> suspecting pisa is a no go with Python 3 and that it is simply failing??
>>
>>
>>
>> Posted question in the xhtml2pdf group, linked below:
>>
>> https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
>>
>> Error:
>> Exception Value:
>>
>> invalid syntax (__init__.py, line 43)
>>
>> Exception
>> Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
>> in , line 26 Python
>> Executable:/home/tom/myvenv3/bin/pythonPython Version:
>> 3.3.2
>>
>> On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
>>>
>>> Thanks so much!! now I know where to look..
>>>
>>> BTW Shouldn't both reportlab and pillow be in the requirements txt
>>> file?? They were the only two I needed to download separately..
>>>
>>> On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
The error is coming from sx/pisa3/__init__.py, line 43 which says:
{{{
if not REPORTLAB22:
raise ImportError, "Reportlab Toolkit Version 2.2 or
higher needed"
}}}
Now, obviously you do have reportlab of a version higher than 2.2
but
there was a bug mentioned on the cartridge issues a few weeks ago
which
seemed to indicate that reportlab 3.0 isn't reporting its version
correctly as higher than 2.2.
See https://github.com/stephenmcd/cartridge/issues/174#
issuecomment-35755887
It seems like it's a known bug in pisa.
Hope this helps.
Seeya. Danny.
On 27/02/2014 9:52 AM, Tom Brander wrote:
> Hmm did not have reportlab, so I installed it but no change, here
is the
> pip list
> (myvenv3) tom@tom-sam:~/whiteplume$ pip list
> bleach (1.4)
> Cartridge (0.9.2)
> Django (1.6.2)
> filebrowser-safe (0.3.2)
> future (0.9.0)
> grappelli-safe (0.3.6)
> html5lib (0.999)
> Mezzanine (3.0.9)
> oauthlib (0.6.1)
> Pillow (2.3.0)
> pip (1.5.4)
> pisa (3.0.33)
> pytz (2013.9)
> reportlab (3.0)
> requests (2.2.1)
> requests-oauthlib (0.4.0)
> setuptools (2.2)
> six (1.5.2)
> tzlocal (1.0)
>
>
> On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
>
> On 27/02/2014 7:29 AM, Tom Brander wrote:
> > Went to create a pdf invoice and got this error:
> > I am using Python #.3 if that makes a diff??
> > Does not give me much to go on the "view" invoice is
working fine...
>
> Can you do a pip list for us?
>
> Do you have pisa and reportlab both installed? What versions?
>
>
> >
> > Traceback:
> > File
> >
>
> "/home/tom/myvenv3/lib/python3.3/s
Re: [mezzanine-users] Error with Pisa? P3?
Ok, so I've created a pull request adding reportlab 2.7 as a dependency for
cartridge:
https://github.com/stephenmcd/cartridge/pull/181
And also opened an issue so we can potentially work on upgrading to use
xhtml2pdf in future:
https://github.com/stephenmcd/cartridge/issues/180
Hope this helps.
Seeya. Danny.
PS. Tom, feel free to work on that issue, if you want!
On 28 February 2014 11:05, Stephen McDonald wrote:
> Yep sounds good
>
>
> On Fri, Feb 28, 2014 at 11:33 AM, Danny wrote:
>
>> Tom's pointed out in a private email that he's working with Python 3, and
>> reportlab 2.7 won't work on Python 3.
>>
>> I'm still using python 2.7, so using an older reportlab is fine for me.
>>
>> Should I still go ahead with the change to cartridge's setup.py (adding
>> reportlab==2.7 as a dependency) or should we look at trying and solving the
>> larger issue?
>>
>> Seeya. Danny.
>>
>>
>>
>> On 28 February 2014 10:55, Stephen McDonald wrote:
>>
>>> Thanks a lot that'd be great!
>>>
>>>
>>> On Fri, Feb 28, 2014 at 11:23 AM, Danny wrote:
>>>
I'd say so, Stephen, at least until cartridge can be updated to use
xhtml2pdf instead of pisa (which seems to be an abandoned project).
At the moment, there's no dependency on reportlab in cartridge (only
pisa), but because pisa doesn't have reportlab in its own dependency list,
it couldn't hurt specifying the versions that cartridge needs.
I'll create a pull request, if you like?
Seeya. Danny.
On 28 February 2014 10:49, Stephen McDonald wrote:
> Thanks Danny - I'm not really across the issue, do you think we need
> to specify that exact reportlab version in Cartridge's setup.py?
>
>
> On Fri, Feb 28, 2014 at 11:17 AM, Danny wrote:
>
>> Best option for now is to downgrade reportlab to 2.7 (I did that on
>> my site this morning, after this discussion!)
>>
>> Just add reportlab==2.7 to your requirements/project.txt and do a pip
>> install -U -r requirements/project.txt
>>
>> Seeya. Danny.
>>
>>
>> On 28 February 2014 10:45, Tom Brander wrote:
>>
>>> Tried to used the fix suggested but still getting the same error
>>> (FWIW I never did get the message version 2.2 or higher needed),, so I'm
>>> suspecting pisa is a no go with Python 3 and that it is simply failing??
>>>
>>>
>>>
>>> Posted question in the xhtml2pdf group, linked below:
>>>
>>> https://groups.google.com/d/msg/xhtml2pdf/mihS51DtZkU/P5zuIvLlC-0J
>>>
>>> Error:
>>> Exception Value:
>>>
>>> invalid syntax (__init__.py, line 43)
>>>
>>> Exception
>>> Location:/home/tom/myvenv3/lib/python3.3/site-packages/ho/pisa/__init__.py
>>> in , line 26 Python
>>> Executable:/home/tom/myvenv3/bin/pythonPython Version:
>>> 3.3.2
>>>
>>> On Thursday, February 27, 2014 8:05:02 AM UTC-6, Tom Brander wrote:
Thanks so much!! now I know where to look..
BTW Shouldn't both reportlab and pillow be in the requirements txt
file?? They were the only two I needed to download separately..
On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
>
> The error is coming from sx/pisa3/__init__.py, line 43 which says:
>
> {{{
> if not REPORTLAB22:
> raise ImportError, "Reportlab Toolkit Version 2.2 or
> higher needed"
> }}}
>
> Now, obviously you do have reportlab of a version higher than 2.2
> but
> there was a bug mentioned on the cartridge issues a few weeks ago
> which
> seemed to indicate that reportlab 3.0 isn't reporting its version
> correctly as higher than 2.2.
>
> See https://github.com/stephenmcd/cartridge/issues/174#
> issuecomment-35755887
>
> It seems like it's a known bug in pisa.
>
> Hope this helps.
>
> Seeya. Danny.
>
> On 27/02/2014 9:52 AM, Tom Brander wrote:
> > Hmm did not have reportlab, so I installed it but no change,
> here is the
> > pip list
> > (myvenv3) tom@tom-sam:~/whiteplume$ pip list
> > bleach (1.4)
> > Cartridge (0.9.2)
> > Django (1.6.2)
> > filebrowser-safe (0.3.2)
> > future (0.9.0)
> > grappelli-safe (0.3.6)
> > html5lib (0.999)
> > Mezzanine (3.0.9)
> > oauthlib (0.6.1)
> > Pillow (2.3.0)
> > pip (1.5.4)
> > pisa (3.0.33)
> > pytz (2013.9)
> > reportlab (3.0)
> > requests (2.2.1)
> > requests-oauthlib (0.4.0)
> > setuptools (2.2)
> > six (1.5.2)
> > tzlocal (1.0)
> >
> >
> > On Wednesday, February 26, 2014 3:43:49 PM UTC-6, Danny S wrote:
> >
> > On 27/02/2014 7:
