Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
To answer your last question Tom, fabric isn't intended to be used for development, it is intended for production and will take a hosting environment from blank OS to ready to serve your site automagically. On Mon, Mar 3, 2014 at 9:25 PM, Stephen McDonald wrote: > As for the original issue, there's a clear note early on in Mezzanine's > README covering the very steps necessary to avoid the problem you've hit: > https://github.com/stephenmcd/mezzanine/#dependencies > > Ken's point was that if you spend the time up front understanding vagrant > and fabric, you'll find that these very steps are automatically handled for > you. > > As for the introductory questions asked just now around how these tools > work, any reply given here would do an injustice to the excellent > documentation these projects have, as well as the tutorials that exist - > seek them out! Ken has posted references to this topic countless times on > the list before. > > > > > > On Tue, Mar 4, 2014 at 3:06 PM, Tom Brander wrote: > >> So.. Are you suggesting using Fabric instead of Pip for an initial >> development install?? (seems to be at variance with the doc) but I'm trying >> too understand... >> >> >> On Monday, March 3, 2014 9:57:56 PM UTC-6, Kenneth Bolton wrote: >> >>> One great thing about the fabfile.py that ships with Mezzanine is that >>> it contains the best practices of a bunch of developers across a half-dozen >>> technologies - with no cruft - that can immediately go into version control >>> and grow with your application. If you opt not to use Fabric to manage your >>> deploy, use the default fabfile to guide whatever deployment or >>> provisioning solution you choose. >>> >>> The lines from the fabfile that should help Tabs: >>> https://github.com/stephenmcd/mezzanine/blob/master/ >>> mezzanine/project_template/fabfile.py#L351-L352 >>> >>> >>> >>> >>> On Mon, Mar 3, 2014 at 10:31 PM, Stephen McDonald wrote: >>> Mezzanine's fabric recipe was entirely developed using vagrant - it's actually a perfect match. On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander wrote: > Ken, he is just trying to install on a vagrant instance, presumably to > give him a Linux VM on Windows?? Fabric doe not apply (yet) > I was going to recommend Anaconda on Windows (to eliminate vagrant ) > but it seems from a quick check, Anaconda has some issues with Pillows as > well (surprise..) I'm a bit out of touch with the PIL/Pillows state of the > art on Windows... > > On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote: > >> "Use Fabric for repeatable installations", I repeat. >> >> >> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote: >> >>> Looks like you are missing the C compiler and perhaps the associated >>> dev tools library... >>> >>> >>> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote: Hi Mezzanine community, I am new to the Framework and I am trying to Setup a simple site using it. I am following the instructions posted here () and Setting up everything using Vagrant as virtualization Environment. Everything was going fine until I tried to install Mezzanine. When running (sudo) pip install Mezzanine, I get an error on Pillow. This is the last part of the log where the error appears. Any ideas on how to fix it? Requirement already satisfied (use --upgrade to upgrade): future==0.9.0 in /home /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine) Downloading/unpacking pillow (from mezzanine) Running setup.py egg_info for package pillow Downloading/unpacking pytz (from tzlocal==1.0->mezzanine) Running setup.py egg_info for package pytz warning: no files found matching '*.pot' under directory 'pytz' warning: no previously-included files found matching 'test_zdump.py' Requirement already satisfied (use --upgrade to upgrade): six in /home/vagrant/. virtualenvs/blog/lib/python2.7/site-packages (from bleach>=1.4->mezzanine) Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine) Running setup.py egg_info for package html5lib Downloading/unpacking oauthlib>=0.4.2 (from requests- oauthlib>=0.4->mezzanine) Running setup.py egg_info for package oauthlib Installing collected packages: pillow, pytz, html5lib, oauthlib Running setup.py install for pillow building 'PIL._imaging' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-pro totypes -fPIC -DHAVE_LIBZ -I/home/vagrant/.virtualenvs/blog/build/pillow/libIma
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
As for the original issue, there's a clear note early on in Mezzanine's README covering the very steps necessary to avoid the problem you've hit: https://github.com/stephenmcd/mezzanine/#dependencies Ken's point was that if you spend the time up front understanding vagrant and fabric, you'll find that these very steps are automatically handled for you. As for the introductory questions asked just now around how these tools work, any reply given here would do an injustice to the excellent documentation these projects have, as well as the tutorials that exist - seek them out! Ken has posted references to this topic countless times on the list before. On Tue, Mar 4, 2014 at 3:06 PM, Tom Brander wrote: > So.. Are you suggesting using Fabric instead of Pip for an initial > development install?? (seems to be at variance with the doc) but I'm trying > too understand... > > > On Monday, March 3, 2014 9:57:56 PM UTC-6, Kenneth Bolton wrote: > >> One great thing about the fabfile.py that ships with Mezzanine is that it >> contains the best practices of a bunch of developers across a half-dozen >> technologies – with no cruft – that can immediately go into version control >> and grow with your application. If you opt not to use Fabric to manage your >> deploy, use the default fabfile to guide whatever deployment or >> provisioning solution you choose. >> >> The lines from the fabfile that should help Tabs: >> https://github.com/stephenmcd/mezzanine/blob/master/ >> mezzanine/project_template/fabfile.py#L351-L352 >> >> >> >> >> On Mon, Mar 3, 2014 at 10:31 PM, Stephen McDonald wrote: >> >>> Mezzanine's fabric recipe was entirely developed using vagrant - it's >>> actually a perfect match. >>> >>> >>> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander wrote: >>> Ken, he is just trying to install on a vagrant instance, presumably to give him a Linux VM on Windows?? Fabric doe not apply (yet) I was going to recommend Anaconda on Windows (to eliminate vagrant ) but it seems from a quick check, Anaconda has some issues with Pillows as well (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art on Windows... On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote: > "Use Fabric for repeatable installations", I repeat. > > > On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote: > >> Looks like you are missing the C compiler and perhaps the associated >> dev tools library... >> >> >> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote: >>> >>> Hi Mezzanine community, >>> >>> I am new to the Framework and I am trying to Setup a simple site >>> using it. >>> I am following the instructions posted here () and Setting up >>> everything >>> using Vagrant as virtualization Environment. Everything was going >>> fine >>> until I tried to install Mezzanine. >>> >>> When running (sudo) pip install Mezzanine, I get an error on Pillow. >>> This >>> is the last part of the log where the error appears. Any ideas on >>> how to >>> fix it? >>> >>> Requirement already satisfied (use --upgrade to upgrade): >>> future==0.9.0 >>> in /home >>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from >>> mezzanine) >>> Downloading/unpacking pillow (from mezzanine) >>> Running setup.py egg_info for package pillow >>> >>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine) >>> Running setup.py egg_info for package pytz >>> >>> warning: no files found matching '*.pot' under directory 'pytz' >>> warning: no previously-included files found matching >>> 'test_zdump.py' >>> Requirement already satisfied (use --upgrade to upgrade): six >>> in /home/vagrant/. >>> virtualenvs/blog/lib/python2.7/site-packages (from >>> bleach>=1.4->mezzanine) >>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine) >>> Running setup.py egg_info for package html5lib >>> >>> Downloading/unpacking oauthlib>=0.4.2 (from requests- >>> oauthlib>=0.4->mezzanine) >>> Running setup.py egg_info for package oauthlib >>> >>> Installing collected packages: pillow, pytz, html5lib, oauthlib >>> Running setup.py install for pillow >>> >>> building 'PIL._imaging' extension >>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall >>> -Wstrict-pro >>> totypes -fPIC -DHAVE_LIBZ >>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag >>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include >>> -I/usr/includ >>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux- >>> i686-2.7/_imaging.o >>> >>> _imaging.c:76:20: fatal error: Python.h: No such file or >>> directory >>> compilation terminated. >>> error: command 'gcc' failed with exit status 1 >>>
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
So.. Are you suggesting using Fabric instead of Pip for an initial
development install?? (seems to be at variance with the doc) but I'm trying
too understand...
On Monday, March 3, 2014 9:57:56 PM UTC-6, Kenneth Bolton wrote:
>
> One great thing about the fabfile.py that ships with Mezzanine is that it
> contains the best practices of a bunch of developers across a half-dozen
> technologies – with no cruft – that can immediately go into version control
> and grow with your application. If you opt not to use Fabric to manage your
> deploy, use the default fabfile to guide whatever deployment or
> provisioning solution you choose.
>
> The lines from the fabfile that should help Tabs:
>
> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L351-L352
>
>
>
>
> On Mon, Mar 3, 2014 at 10:31 PM, Stephen McDonald
> > wrote:
>
>> Mezzanine's fabric recipe was entirely developed using vagrant - it's
>> actually a perfect match.
>>
>>
>> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander
>> > wrote:
>>
>>> Ken, he is just trying to install on a vagrant instance, presumably to
>>> give him a Linux VM on Windows?? Fabric doe not apply (yet)
>>> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but
>>> it seems from a quick check, Anaconda has some issues with Pillows as well
>>> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art
>>> on Windows...
>>>
>>> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>>>
"Use Fabric for repeatable installations", I repeat.
On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote:
> Looks like you are missing the C compiler and perhaps the associated
> dev tools library...
>
>
> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>>
>> Hi Mezzanine community,
>>
>> I am new to the Framework and I am trying to Setup a simple site
>> using it.
>> I am following the instructions posted here () and Setting up
>> everything
>> using Vagrant as virtualization Environment. Everything was going
>> fine
>> until I tried to install Mezzanine.
>>
>> When running (sudo) pip install Mezzanine, I get an error on Pillow.
>> This
>> is the last part of the log where the error appears. Any ideas on
>> how to
>> fix it?
>>
>> Requirement already satisfied (use --upgrade to upgrade):
>> future==0.9.0
>> in /home
>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from
>> mezzanine)
>> Downloading/unpacking pillow (from mezzanine)
>> Running setup.py egg_info for package pillow
>>
>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
>> Running setup.py egg_info for package pytz
>>
>> warning: no files found matching '*.pot' under directory 'pytz'
>> warning: no previously-included files found matching
>> 'test_zdump.py'
>> Requirement already satisfied (use --upgrade to upgrade): six
>> in /home/vagrant/.
>> virtualenvs/blog/lib/python2.7/site-packages (from
>> bleach>=1.4->mezzanine)
>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
>> Running setup.py egg_info for package html5lib
>>
>> Downloading/unpacking oauthlib>=0.4.2 (from requests-
>> oauthlib>=0.4->mezzanine)
>> Running setup.py egg_info for package oauthlib
>>
>> Installing collected packages: pillow, pytz, html5lib, oauthlib
>> Running setup.py install for pillow
>>
>> building 'PIL._imaging' extension
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
>> -Wstrict-pro
>> totypes -fPIC -DHAVE_LIBZ
>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>> -I/usr/includ
>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
>> i686-2.7/_imaging.o
>>
>> _imaging.c:76:20: fatal error: Python.h: No such file or
>> directory
>> compilation terminated.
>> error: command 'gcc' failed with exit status 1
>> Complete output from command
>> /home/vagrant/.virtualenvs/blog/bin/python
>>
>> -c "
>> import
>> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>>
>>
>> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
>> __file__, 'exec'))"
>> install --single-version-externally-managed --record
>> /tmp/pip-gXn3KB-
>> record/ins
>> tall-record.txt --install-
>> headers /home/vagrant/.virtualenvs/blog/include/site/p
>> ython2.7:
>> running install
>>
>> running build
>>
>> running build_py
>>
>> running egg_info
>>
>> writing Pillow.egg-info/PKG-INFO
>>
>> writing top-level names to Pillow.eg
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
One great thing about the fabfile.py that ships with Mezzanine is that it
contains the best practices of a bunch of developers across a half-dozen
technologies – with no cruft – that can immediately go into version control
and grow with your application. If you opt not to use Fabric to manage your
deploy, use the default fabfile to guide whatever deployment or
provisioning solution you choose.
The lines from the fabfile that should help Tabs:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L351-L352
On Mon, Mar 3, 2014 at 10:31 PM, Stephen McDonald wrote:
> Mezzanine's fabric recipe was entirely developed using vagrant - it's
> actually a perfect match.
>
>
> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander wrote:
>
>> Ken, he is just trying to install on a vagrant instance, presumably to
>> give him a Linux VM on Windows?? Fabric doe not apply (yet)
>> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but
>> it seems from a quick check, Anaconda has some issues with Pillows as well
>> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art
>> on Windows...
>>
>> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>>
>>> "Use Fabric for repeatable installations", I repeat.
>>>
>>>
>>> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote:
>>>
Looks like you are missing the C compiler and perhaps the associated
dev tools library...
On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>
> Hi Mezzanine community,
>
> I am new to the Framework and I am trying to Setup a simple site using
> it.
> I am following the instructions posted here () and Setting up
> everything
> using Vagrant as virtualization Environment. Everything was going
> fine
> until I tried to install Mezzanine.
>
> When running (sudo) pip install Mezzanine, I get an error on Pillow.
> This
> is the last part of the log where the error appears. Any ideas on how
> to
> fix it?
>
> Requirement already satisfied (use --upgrade to upgrade):
> future==0.9.0
> in /home
> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from
> mezzanine)
> Downloading/unpacking pillow (from mezzanine)
> Running setup.py egg_info for package pillow
>
> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
> Running setup.py egg_info for package pytz
>
> warning: no files found matching '*.pot' under directory 'pytz'
> warning: no previously-included files found matching
> 'test_zdump.py'
> Requirement already satisfied (use --upgrade to upgrade): six
> in /home/vagrant/.
> virtualenvs/blog/lib/python2.7/site-packages (from
> bleach>=1.4->mezzanine)
> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
> Running setup.py egg_info for package html5lib
>
> Downloading/unpacking oauthlib>=0.4.2 (from requests-
> oauthlib>=0.4->mezzanine)
> Running setup.py egg_info for package oauthlib
>
> Installing collected packages: pillow, pytz, html5lib, oauthlib
> Running setup.py install for pillow
>
> building 'PIL._imaging' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-pro
> totypes -fPIC -DHAVE_LIBZ
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
> -I/usr/includ
> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
> i686-2.7/_imaging.o
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory
> compilation terminated.
> error: command 'gcc' failed with exit status 1
> Complete output from command
> /home/vagrant/.virtualenvs/blog/bin/python
>
> -c "
> import
> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>
> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
> __file__, 'exec'))"
> install --single-version-externally-managed --record
> /tmp/pip-gXn3KB-
> record/ins
> tall-record.txt --install-
> headers /home/vagrant/.virtualenvs/blog/include/site/p
> ython2.7:
> running install
>
> running build
>
> running build_py
>
> running egg_info
>
> writing Pillow.egg-info/PKG-INFO
>
> writing top-level names to Pillow.egg-info/top_level.txt
>
> writing dependency_links to Pillow.egg-info/dependency_links.txt
>
> warning: manifest_maker: standard file '-c' not found
>
>
>
> reading manifest file 'Pillow.egg-info/SOURCES.txt'
>
> reading manifest template 'MANIFEST.in'
>
> writing manifest file 'Pillow.egg-info/SOURCES.txt'
>
> running build_ext
>
> building 'PIL._imaging' extension
>
> gcc -pthread -fno-strict-al
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
But doesn't he have to 1st get a PIP install somewhere?
On Monday, March 3, 2014 9:31:17 PM UTC-6, Stephen McDonald wrote:
>
> Mezzanine's fabric recipe was entirely developed using vagrant - it's
> actually a perfect match.
>
>
> On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander
> > wrote:
>
>> Ken, he is just trying to install on a vagrant instance, presumably to
>> give him a Linux VM on Windows?? Fabric doe not apply (yet)
>> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but
>> it seems from a quick check, Anaconda has some issues with Pillows as well
>> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art
>> on Windows...
>>
>> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>>
>>> "Use Fabric for repeatable installations", I repeat.
>>>
>>>
>>> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote:
>>>
Looks like you are missing the C compiler and perhaps the associated
dev tools library...
On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>
> Hi Mezzanine community,
>
> I am new to the Framework and I am trying to Setup a simple site using
> it.
> I am following the instructions posted here () and Setting up
> everything
> using Vagrant as virtualization Environment. Everything was going
> fine
> until I tried to install Mezzanine.
>
> When running (sudo) pip install Mezzanine, I get an error on Pillow.
> This
> is the last part of the log where the error appears. Any ideas on how
> to
> fix it?
>
> Requirement already satisfied (use --upgrade to upgrade):
> future==0.9.0
> in /home
> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from
> mezzanine)
> Downloading/unpacking pillow (from mezzanine)
> Running setup.py egg_info for package pillow
>
> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
> Running setup.py egg_info for package pytz
>
> warning: no files found matching '*.pot' under directory 'pytz'
> warning: no previously-included files found matching
> 'test_zdump.py'
> Requirement already satisfied (use --upgrade to upgrade): six
> in /home/vagrant/.
> virtualenvs/blog/lib/python2.7/site-packages (from
> bleach>=1.4->mezzanine)
> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
> Running setup.py egg_info for package html5lib
>
> Downloading/unpacking oauthlib>=0.4.2 (from requests-
> oauthlib>=0.4->mezzanine)
> Running setup.py egg_info for package oauthlib
>
> Installing collected packages: pillow, pytz, html5lib, oauthlib
> Running setup.py install for pillow
>
> building 'PIL._imaging' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-pro
> totypes -fPIC -DHAVE_LIBZ
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
> -I/usr/includ
> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
> i686-2.7/_imaging.o
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory
> compilation terminated.
> error: command 'gcc' failed with exit status 1
> Complete output from command
> /home/vagrant/.virtualenvs/blog/bin/python
>
> -c "
> import
> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>
> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
> __file__, 'exec'))"
> install --single-version-externally-managed --record
> /tmp/pip-gXn3KB-
> record/ins
> tall-record.txt --install-
> headers /home/vagrant/.virtualenvs/blog/include/site/p
> ython2.7:
> running install
>
> running build
>
> running build_py
>
> running egg_info
>
> writing Pillow.egg-info/PKG-INFO
>
> writing top-level names to Pillow.egg-info/top_level.txt
>
> writing dependency_links to Pillow.egg-info/dependency_links.txt
>
> warning: manifest_maker: standard file '-c' not found
>
>
>
> reading manifest file 'Pillow.egg-info/SOURCES.txt'
>
> reading manifest template 'MANIFEST.in'
>
> writing manifest file 'Pillow.egg-info/SOURCES.txt'
>
> running build_ext
>
> building 'PIL._imaging' extension
>
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-
> prototy
> pes -fPIC -DHAVE_LIBZ
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
> -I/usr/include -I
> /usr/include/python2.7 -c _imaging.c -o
> build/temp.linux-i686-2.7/_imaging.o
>
>
> _imaging.c:76:20: fatal error:
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
Mezzanine's fabric recipe was entirely developed using vagrant - it's
actually a perfect match.
On Tue, Mar 4, 2014 at 2:29 PM, Tom Brander wrote:
> Ken, he is just trying to install on a vagrant instance, presumably to
> give him a Linux VM on Windows?? Fabric doe not apply (yet)
> I was going to recommend Anaconda on Windows (to eliminate vagrant ) but
> it seems from a quick check, Anaconda has some issues with Pillows as well
> (surprise..) I'm a bit out of touch with the PIL/Pillows state of the art
> on Windows...
>
> On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>
>> "Use Fabric for repeatable installations", I repeat.
>>
>>
>> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote:
>>
>>> Looks like you are missing the C compiler and perhaps the associated dev
>>> tools library...
>>>
>>>
>>> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
Hi Mezzanine community,
I am new to the Framework and I am trying to Setup a simple site using
it.
I am following the instructions posted here () and Setting up
everything
using Vagrant as virtualization Environment. Everything was going fine
until I tried to install Mezzanine.
When running (sudo) pip install Mezzanine, I get an error on Pillow.
This
is the last part of the log where the error appears. Any ideas on how
to
fix it?
Requirement already satisfied (use --upgrade to upgrade): future==0.9.0
in /home
/vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from
mezzanine)
Downloading/unpacking pillow (from mezzanine)
Running setup.py egg_info for package pillow
Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
Running setup.py egg_info for package pytz
warning: no files found matching '*.pot' under directory 'pytz'
warning: no previously-included files found matching
'test_zdump.py'
Requirement already satisfied (use --upgrade to upgrade): six
in /home/vagrant/.
virtualenvs/blog/lib/python2.7/site-packages (from
bleach>=1.4->mezzanine)
Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
Running setup.py egg_info for package html5lib
Downloading/unpacking oauthlib>=0.4.2 (from requests-
oauthlib>=0.4->mezzanine)
Running setup.py egg_info for package oauthlib
Installing collected packages: pillow, pytz, html5lib, oauthlib
Running setup.py install for pillow
building 'PIL._imaging' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-pro
totypes -fPIC -DHAVE_LIBZ
-I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
-I/usr/includ
e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
i686-2.7/_imaging.o
_imaging.c:76:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1
Complete output from command /home/vagrant/.virtualenvs/blog/bin/python
-c "
import
setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
__file__, 'exec'))"
install --single-version-externally-managed --record /tmp/pip-gXn3KB-
record/ins
tall-record.txt --install-
headers /home/vagrant/.virtualenvs/blog/include/site/p
ython2.7:
running install
running build
running build_py
running egg_info
writing Pillow.egg-info/PKG-INFO
writing top-level names to Pillow.egg-info/top_level.txt
writing dependency_links to Pillow.egg-info/dependency_links.txt
warning: manifest_maker: standard file '-c' not found
reading manifest file 'Pillow.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'Pillow.egg-info/SOURCES.txt'
running build_ext
building 'PIL._imaging' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-
prototy
pes -fPIC -DHAVE_LIBZ
-I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
-I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
-I/usr/include -I
/usr/include/python2.7 -c _imaging.c -o
build/temp.linux-i686-2.7/_imaging.o
_imaging.c:76:20: fatal error: Python.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1
Command /home/vagrant/.virtualenvs/blog/bin/python -c "import
setuptools;__file_
_='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open
(__fi
le__).read(
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
Ken, he is just trying to install on a vagrant instance, presumably to give
him a Linux VM on Windows?? Fabric doe not apply (yet)
I was going to recommend Anaconda on Windows (to eliminate vagrant ) but it
seems from a quick check, Anaconda has some issues with Pillows as well
(surprise..) I'm a bit out of touch with the PIL/Pillows state of the art
on Windows...
On Monday, March 3, 2014 9:09:41 PM UTC-6, Kenneth Bolton wrote:
>
> "Use Fabric for repeatable installations", I repeat.
>
>
> On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander
> > wrote:
>
>> Looks like you are missing the C compiler and perhaps the associated dev
>> tools library...
>>
>>
>> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>>>
>>> Hi Mezzanine community,
>>>
>>> I am new to the Framework and I am trying to Setup a simple site using
>>> it.
>>> I am following the instructions posted here () and Setting up everything
>>> using Vagrant as virtualization Environment. Everything was going fine
>>> until I tried to install Mezzanine.
>>>
>>> When running (sudo) pip install Mezzanine, I get an error on Pillow.
>>> This
>>> is the last part of the log where the error appears. Any ideas on how
>>> to
>>> fix it?
>>>
>>> Requirement already satisfied (use --upgrade to upgrade): future==0.9.0
>>> in /home
>>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine)
>>> Downloading/unpacking pillow (from mezzanine)
>>> Running setup.py egg_info for package pillow
>>>
>>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
>>> Running setup.py egg_info for package pytz
>>>
>>> warning: no files found matching '*.pot' under directory 'pytz'
>>> warning: no previously-included files found matching 'test_zdump.py'
>>> Requirement already satisfied (use --upgrade to upgrade): six
>>> in /home/vagrant/.
>>> virtualenvs/blog/lib/python2.7/site-packages (from
>>> bleach>=1.4->mezzanine)
>>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
>>> Running setup.py egg_info for package html5lib
>>>
>>> Downloading/unpacking oauthlib>=0.4.2 (from requests-
>>> oauthlib>=0.4->mezzanine)
>>> Running setup.py egg_info for package oauthlib
>>>
>>> Installing collected packages: pillow, pytz, html5lib, oauthlib
>>> Running setup.py install for pillow
>>>
>>> building 'PIL._imaging' extension
>>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
>>> -Wstrict-pro
>>> totypes -fPIC -DHAVE_LIBZ
>>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
>>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>>> -I/usr/includ
>>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
>>> i686-2.7/_imaging.o
>>>
>>> _imaging.c:76:20: fatal error: Python.h: No such file or directory
>>> compilation terminated.
>>> error: command 'gcc' failed with exit status 1
>>> Complete output from command /home/vagrant/.virtualenvs/blog/bin/python
>>>
>>> -c "
>>> import
>>> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>>>
>>> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
>>> __file__, 'exec'))"
>>> install --single-version-externally-managed --record /tmp/pip-gXn3KB-
>>> record/ins
>>> tall-record.txt --install-
>>> headers /home/vagrant/.virtualenvs/blog/include/site/p
>>> ython2.7:
>>> running install
>>>
>>> running build
>>>
>>> running build_py
>>>
>>> running egg_info
>>>
>>> writing Pillow.egg-info/PKG-INFO
>>>
>>> writing top-level names to Pillow.egg-info/top_level.txt
>>>
>>> writing dependency_links to Pillow.egg-info/dependency_links.txt
>>>
>>> warning: manifest_maker: standard file '-c' not found
>>>
>>>
>>>
>>> reading manifest file 'Pillow.egg-info/SOURCES.txt'
>>>
>>> reading manifest template 'MANIFEST.in'
>>>
>>> writing manifest file 'Pillow.egg-info/SOURCES.txt'
>>>
>>> running build_ext
>>>
>>> building 'PIL._imaging' extension
>>>
>>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
>>> -Wstrict-
>>> prototy
>>> pes -fPIC -DHAVE_LIBZ
>>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
>>> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>>> -I/usr/include -I
>>> /usr/include/python2.7 -c _imaging.c -o
>>> build/temp.linux-i686-2.7/_imaging.o
>>>
>>>
>>> _imaging.c:76:20: fatal error: Python.h: No such file or directory
>>>
>>> compilation terminated.
>>>
>>> error: command 'gcc' failed with exit status 1
>>>
>>>
>>> Command /home/vagrant/.virtualenvs/blog/bin/python -c "import
>>> setuptools;__file_
>>> _='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open
>>>
>>> (__fi
>>> le__).read().replace('\r\n', '\n'), __file__, 'exec'))" install
>>> --single-
>>> version
>>> -externally-managed --record /tmp/pip-gXn3KB-record/install-record.txt
>>> --install
>>> -headers /home/vagrant/.virtualenvs/bl
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
"Use Fabric for repeatable installations", I repeat.
On Mon, Mar 3, 2014 at 9:47 PM, Tom Brander wrote:
> Looks like you are missing the C compiler and perhaps the associated dev
> tools library...
>
>
> On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>>
>> Hi Mezzanine community,
>>
>> I am new to the Framework and I am trying to Setup a simple site using
>> it.
>> I am following the instructions posted here () and Setting up everything
>> using Vagrant as virtualization Environment. Everything was going fine
>> until I tried to install Mezzanine.
>>
>> When running (sudo) pip install Mezzanine, I get an error on Pillow.
>> This
>> is the last part of the log where the error appears. Any ideas on how to
>> fix it?
>>
>> Requirement already satisfied (use --upgrade to upgrade): future==0.9.0
>> in /home
>> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine)
>> Downloading/unpacking pillow (from mezzanine)
>> Running setup.py egg_info for package pillow
>>
>> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
>> Running setup.py egg_info for package pytz
>>
>> warning: no files found matching '*.pot' under directory 'pytz'
>> warning: no previously-included files found matching 'test_zdump.py'
>> Requirement already satisfied (use --upgrade to upgrade): six
>> in /home/vagrant/.
>> virtualenvs/blog/lib/python2.7/site-packages (from
>> bleach>=1.4->mezzanine)
>> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
>> Running setup.py egg_info for package html5lib
>>
>> Downloading/unpacking oauthlib>=0.4.2 (from requests-
>> oauthlib>=0.4->mezzanine)
>> Running setup.py egg_info for package oauthlib
>>
>> Installing collected packages: pillow, pytz, html5lib, oauthlib
>> Running setup.py install for pillow
>>
>> building 'PIL._imaging' extension
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
>> -Wstrict-pro
>> totypes -fPIC -DHAVE_LIBZ
>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
>> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>> -I/usr/includ
>> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
>> i686-2.7/_imaging.o
>>
>> _imaging.c:76:20: fatal error: Python.h: No such file or directory
>> compilation terminated.
>> error: command 'gcc' failed with exit status 1
>> Complete output from command /home/vagrant/.virtualenvs/blog/bin/python
>>
>> -c "
>> import
>> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
>>
>> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
>> __file__, 'exec'))"
>> install --single-version-externally-managed --record /tmp/pip-gXn3KB-
>> record/ins
>> tall-record.txt --install-
>> headers /home/vagrant/.virtualenvs/blog/include/site/p
>> ython2.7:
>> running install
>>
>> running build
>>
>> running build_py
>>
>> running egg_info
>>
>> writing Pillow.egg-info/PKG-INFO
>>
>> writing top-level names to Pillow.egg-info/top_level.txt
>>
>> writing dependency_links to Pillow.egg-info/dependency_links.txt
>>
>> warning: manifest_maker: standard file '-c' not found
>>
>>
>>
>> reading manifest file 'Pillow.egg-info/SOURCES.txt'
>>
>> reading manifest template 'MANIFEST.in'
>>
>> writing manifest file 'Pillow.egg-info/SOURCES.txt'
>>
>> running build_ext
>>
>> building 'PIL._imaging' extension
>>
>> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-
>> prototy
>> pes -fPIC -DHAVE_LIBZ
>> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
>> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
>> -I/usr/include -I
>> /usr/include/python2.7 -c _imaging.c -o build/temp.linux-i686-2.7/_imaging.o
>>
>>
>> _imaging.c:76:20: fatal error: Python.h: No such file or directory
>>
>> compilation terminated.
>>
>> error: command 'gcc' failed with exit status 1
>>
>>
>> Command /home/vagrant/.virtualenvs/blog/bin/python -c "import
>> setuptools;__file_
>> _='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open
>>
>> (__fi
>> le__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-
>> version
>> -externally-managed --record /tmp/pip-gXn3KB-record/install-record.txt
>> --install
>> -headers /home/vagrant/.virtualenvs/blog/include/site/python2.7 failed
>> with
>> erro
>> r code 1 in /home/vagrant/.virtualenvs/blog/build/pillow
>> Storing complete log in /home/vagrant/.pip/pip.log
>> (blog)vagrant@precise32:~/.virtualenvs/blog/bin$ dpkg-query -l *python*
>> Desired=Unknown/Install/Remove/Purge/Hold
>> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-
>>
>> pend
>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>> ||/ Name VersionDescription
>> +++-==-==-
>>
>> ii python 2.7.3-0ubuntu2 interactive high-level object-oriented
>> langu
>> (blog)vagrant@precise32:~
[mezzanine-users] Re: Installing Mezzanine on Vagrant
Looks like you are missing the C compiler and perhaps the associated dev
tools library...
On Monday, March 3, 2014 2:40:17 PM UTC-6, Tabs wrote:
>
> Hi Mezzanine community,
>
> I am new to the Framework and I am trying to Setup a simple site using it.
> I am following the instructions posted here () and Setting up everything
> using Vagrant as virtualization Environment. Everything was going fine
> until I tried to install Mezzanine.
>
> When running (sudo) pip install Mezzanine, I get an error on Pillow. This
> is the last part of the log where the error appears. Any ideas on how to
> fix it?
>
> Requirement already satisfied (use --upgrade to upgrade): future==0.9.0
> in /home
> /vagrant/.virtualenvs/blog/lib/python2.7/site-packages (from mezzanine)
> Downloading/unpacking pillow (from mezzanine)
> Running setup.py egg_info for package pillow
>
> Downloading/unpacking pytz (from tzlocal==1.0->mezzanine)
> Running setup.py egg_info for package pytz
>
> warning: no files found matching '*.pot' under directory 'pytz'
> warning: no previously-included files found matching 'test_zdump.py'
> Requirement already satisfied (use --upgrade to upgrade): six
> in /home/vagrant/.
> virtualenvs/blog/lib/python2.7/site-packages (from bleach>=1.4->mezzanine)
> Downloading/unpacking html5lib>=0.999 (from bleach>=1.4->mezzanine)
> Running setup.py egg_info for package html5lib
>
> Downloading/unpacking oauthlib>=0.4.2 (from requests-
> oauthlib>=0.4->mezzanine)
> Running setup.py egg_info for package oauthlib
>
> Installing collected packages: pillow, pytz, html5lib, oauthlib
> Running setup.py install for pillow
>
> building 'PIL._imaging' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-pro
> totypes -fPIC -DHAVE_LIBZ
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImag
> ing -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
> -I/usr/includ
> e -I/usr/include/python2.7 -c _imaging.c -o build/temp.linux-
> i686-2.7/_imaging.o
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory
> compilation terminated.
> error: command 'gcc' failed with exit status 1
> Complete output from command
> /home/vagrant/.virtualenvs/blog/bin/python
> -c "
> import
> setuptools;__file__='/home/vagrant/.virtualenvs/blog/build/pillow/setup.p
> y';exec(compile(open(__file__).read().replace('\r\n', '\n'),
> __file__, 'exec'))"
> install --single-version-externally-managed --record /tmp/pip-gXn3KB-
> record/ins
> tall-record.txt --install-
> headers /home/vagrant/.virtualenvs/blog/include/site/p
> ython2.7:
> running install
>
> running build
>
> running build_py
>
> running egg_info
>
> writing Pillow.egg-info/PKG-INFO
>
> writing top-level names to Pillow.egg-info/top_level.txt
>
> writing dependency_links to Pillow.egg-info/dependency_links.txt
>
> warning: manifest_maker: standard file '-c' not found
>
>
>
> reading manifest file 'Pillow.egg-info/SOURCES.txt'
>
> reading manifest template 'MANIFEST.in'
>
> writing manifest file 'Pillow.egg-info/SOURCES.txt'
>
> running build_ext
>
> building 'PIL._imaging' extension
>
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-
> prototy
> pes -fPIC -DHAVE_LIBZ
> -I/home/vagrant/.virtualenvs/blog/build/pillow/libImaging
> -I/home/vagrant/.virtualenvs/blog/include -I/usr/local/include
> -I/usr/include -I
> /usr/include/python2.7 -c _imaging.c -o
> build/temp.linux-i686-2.7/_imaging.o
>
> _imaging.c:76:20: fatal error: Python.h: No such file or directory
>
> compilation terminated.
>
> error: command 'gcc' failed with exit status 1
>
>
> Command /home/vagrant/.virtualenvs/blog/bin/python -c "import
> setuptools;__file_
> _='/home/vagrant/.virtualenvs/blog/build/pillow/setup.py';exec(compile(open
>
> (__fi
> le__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-
> version
> -externally-managed --record /tmp/pip-gXn3KB-record/install-record.txt
> --install
> -headers /home/vagrant/.virtualenvs/blog/include/site/python2.7 failed
> with
> erro
> r code 1 in /home/vagrant/.virtualenvs/blog/build/pillow
> Storing complete log in /home/vagrant/.pip/pip.log
> (blog)vagrant@precise32:~/.virtualenvs/blog/bin$ dpkg-query -l *python*
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-
> pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name VersionDescription
> +++-==-==-
>
> ii python 2.7.3-0ubuntu2 interactive high-level object-oriented
> langu
> (blog)vagrant@precise32:~/.virtualenvs/blog/bin$
>
> By any case, is there any other site that instructs how to Setup the whole
> Thing using Windows? I think it would be faster for
