Hi,
I'm used to virtualenvs and I think I understood the general idea of build out.
I need to build a pice of software out of several independent Python packages
and I think buildout is the tool to use. But I don't get how buildout and
virtualenv are related to each other. Asking Google, I
On Mon, Nov 11, 2013 at 10:26 AM, Achim Domma do...@procoders.net wrote:
Hi,
I'm used to virtualenvs and I think I understood the general idea of build
out. I need to build a pice of software out of several independent Python
packages and I think buildout is the tool to use. But I don't get
I'm trying to convert a setup.py to use setuptools (specifically the
docutils build, FWIW). The existing setup.py has some custom command
stuff to run 2to3 on build.
As I understand it, setuptools should do this automatically by using
use_2to3=True.
So, I've changed the code to just do:
setup(
On Mon, Nov 11, 2013 at 04:29:32PM +, Paul Moore wrote:
I'm trying to convert a setup.py to use setuptools (specifically the
docutils build, FWIW). The existing setup.py has some custom command
stuff to run 2to3 on build.
Aside: I believe there's consensus now that 2to3 is not the best
On 11 November 2013 17:26, Marius Gedminas mar...@pov.lt wrote:
On Mon, Nov 11, 2013 at 04:29:32PM +, Paul Moore wrote:
I'm trying to convert a setup.py to use setuptools (specifically the
docutils build, FWIW). The existing setup.py has some custom command
stuff to run 2to3 on build.
Achim Domma domma at procoders.net writes:
Any starting guidance would be very appreciated!
As of 2.0, Buildout no longer provides isolation so you should do something
like:
$ bin/virtualenv .
$ bin/pip install zc.buildout
$ bin/buildout init
Then start writing your buildout.cfg.
On Mon, Nov 11, 2013 at 6:26 PM, Marius Gedminas mar...@pov.lt wrote:
Aside: I believe there's consensus now that 2to3 is not the best way to
support Python 2.x and 3.x. It's not that hard to have a single source
tree in a portable subset of Python 2.x and 3.x. See python3porting.com
and
On 11 November 2013 20:45, Lennart Regebro rege...@gmail.com wrote:
If 2to3 is being run you'll get quite a lot of fairly obvious output
to that effect. So it sounds like it's not.
A quick look at bdist_egg seems to indicate that it never runs the
build_py step, which is what runs 2to3. So
