Order PDF outputs not working
Darren Hollenbeck
Chris Moffitt
-Chris
--
You received this message because you are subscribed to the Google Groups "Satchmo users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/satchmo-users/-/F6PuzldN6ZQJ.
To post to this group, send email to satchm...@googlegroups.com.
To unsubscribe from this group, send email to satchmo-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
Darren Hollenbeck
On Thursday, April 19, 2012 6:56:04 PM UTC-5, Chris Moffitt wrote:
I suspect there is a problem with your PIL install. What OS are you using? I generally recommend installing PIL using your OS' package management not pip.
-Chris
On Thu, Apr 19, 2012 at 4:27 PM, Darren Hollenbeck wrote:
Error here:Using:ReportLab 2.3 (from my OS distro repos)TRML2PDF from the download link on the satchmo requirements page.PIL 1.1.7 (latest for install via pip)...and I don't think it is relevant, but sorl-thumbnail 11.12 (latest from pip)
--
You received this message because you are subscribed to the Google Groups "Satchmo users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/satchmo-users/-/F6PuzldN6ZQJ.
To post to this group, send email to satchm...@googlegroups.com.
To unsubscribe from this group, send email to satchmo-users+unsubscribe@googlegroups.com.
Ángel Velásquez
> I suspect there is a problem with your PIL install. What OS are you using? I
> generally recommend installing PIL using your OS' package management not
> pip.
>
> -Chris
I don't agree, that isn't the correct behaviour IMHO, the correct
behaviour is install the dev libraries required in order to compile
PIL on your venv with the needed support.
I had this issue in Arch Linux, because i didn't had freetype2
installed, then when I installed it and reinstalled PIL the problem
got solved. And honestly I prefeer to have my virtualenv with all the
libraries that I need isolated from the OS.
--
Ángel Velásquez
Jedi Master CTO
Bixti.com
an...@bixti.com
(00549)11.5980.7308
skype: angelvelasquez_ve
github: angvp
hynekcer
have problems with PIL, but only disagree is too simple. For me it is
much more complicated and unreliable to recommend a list of packages
important for compiling than list of some binary packages recommended
to be precompiled.
Dependencies of the source are not so clear, some are optional. The
first list necessary for compiling can be not enough for satisfactory
running. I would e.g. never configure and compile Crypto library by
myself because I am afraid that I would ommit strong ciphers or an
entropy generator and the program will work without them with unknown
security issues.
I remember that year or two ago there were different names of packages
in Debian a Fedora type ditsributions. For minimal installations is
the source dependency list long and for every distribution release can
be longer. Plus know other main linux distributions + Mac + win for
some developers... and people do not say in the first report what OS
they have.
-- Hynek
Ángel Velásquez
> Ángel: Do it if you can and provide advice regularly to people which
> have problems with PIL, but only disagree is too simple. For me it is
> much more complicated and unreliable to recommend a list of packages
> important for compiling than list of some binary packages recommended
> to be precompiled.
It's too hard to say "install PIL with freetype support"?, excuse me then.
>
> Dependencies of the source are not so clear, some are optional. The
> first list necessary for compiling can be not enough for satisfactory
> running. I would e.g. never configure and compile Crypto library by
> myself because I am afraid that I would ommit strong ciphers or an
> entropy generator and the program will work without them with unknown
> security issues.
>
> I remember that year or two ago there were different names of packages
> in Debian a Fedora type ditsributions. For minimal installations is
> the source dependency list long and for every distribution release can
> be longer. Plus know other main linux distributions + Mac + win for
> some developers... and people do not say in the first report what OS
> they have.
Again, it's too hard to say ... "the error is because the pil that
you've installed on your virtualenv wasn't compiled with freetype
support, probably cause you don't have it".
IMHO it's completely better to try to install / recompile PIL and
freetype instead to install packages (without knowing if this support
were included), and maybe break your OS entirely (if you broke
something on the python os installation, many of the linux OS will
complain ... a lot).
That said, I didn't disagree for "easy" reason, as I've explained I
thought it's common sense to use a virtualenv and don't break the OS,
specially for novel users it's better if they try to install
everything first on the virtualenv and then figure out if they need
something on the OS instead to send them directly to install stuff on
the OS.