<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Picklebytes &#187; Maven</title>
	<atom:link href="http://shane.willowrise.com/archives/tag/maven/feed/" rel="self" type="application/rss+xml" />
	<link>http://shane.willowrise.com</link>
	<description>Tech Notes from Shane Hathaway</description>
	<lastBuildDate>Thu, 22 Jul 2010 17:58:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Easy Workaround for zc.buildout</title>
		<link>http://shane.willowrise.com/archives/easy-workaround-for-zcbuildout/</link>
		<comments>http://shane.willowrise.com/archives/easy-workaround-for-zcbuildout/#comments</comments>
		<pubDate>Thu, 22 Jan 2009 19:05:19 +0000</pubDate>
		<dc:creator>Shane Hathaway</dc:creator>
				<category><![CDATA[Python]]></category>
		<category><![CDATA[Zope]]></category>
		<category><![CDATA[Buildout]]></category>
		<category><![CDATA[Maven]]></category>

		<guid isPermaLink="false">http://shane.willowrise.com/?p=76</guid>
		<description><![CDATA[Problem: running &#8220;python bootstrap.py&#8221; or &#8220;bin/buildout&#8221; often produces scripts that mix up the Python package search path due to some packages being installed system-wide.  Version conflicts result.
Workaround: use &#8220;python -S bootstrap.py&#8221; and &#8220;python -S bin/buildout&#8221;.  Magically, no more version conflicts.
I wish I had thought of that before.  Duh!
Update: Another tip for new zc.buildout users I&#8217;ve [...]]]></description>
			<content:encoded><![CDATA[<p>Problem: running &#8220;python bootstrap.py&#8221; or &#8220;bin/buildout&#8221; often produces scripts that mix up the Python package search path due to some packages being installed system-wide.  Version conflicts result.</p>
<p>Workaround: use &#8220;python -S bootstrap.py&#8221; and &#8220;python -S bin/buildout&#8221;.  Magically, no more version conflicts.</p>
<p>I wish I had thought of that before.  Duh!</p>
<p><strong>Update:</strong> Another tip for new zc.buildout users I&#8217;ve been meaning to mention is that you should create a preferences file in your home directory so that downloads and eggs are cached centrally.  This makes zc.buildout much friendlier.  Do this:</p>
<pre>mkdir ~/.buildout
echo "[buildout]" &gt;&gt; ~/.buildout/default.cfg
echo "eggs-directory = $HOME/.buildout/eggs" &gt;&gt; ~/.buildout/default.cfg
echo "download-cache = $HOME/.buildout/cache" &gt;&gt; ~/.buildout/default.cfg</pre>
<p>It seems a bit silly that zc.buildout doesn&#8217;t have these settings by default.  They make zc.buildout behave a lot like Apache Maven, which is what a lot of Java shops are using these days.  Both zc.buildout and Maven are great tools once you get to know them, but both are a real pain to understand at first.</p>
]]></content:encoded>
			<wfw:commentRss>http://shane.willowrise.com/archives/easy-workaround-for-zcbuildout/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
