On Feb 28, 2013, at 7:39 AM, Mark McLoughlin mar...@redhat.com wrote:
I always felt that the Python community tended more towards the former
approach, but there always exceptions to the rule - to unfairly pick one
one project, sqlalchemy seems to have an API that often changes
incompatibly.
Hey folks,
butt_covering
I've googled around, hit IRC, and tried a bunch of stuff to fix this. Even so,
maybe I missed something obvious. Sorry if this question is redundant.
/butt_covering
I'm using buildout to install a series of python modules, each of which is
dependent on the others *at
On 28-02-13 20:31, Ben Acland wrote:
tl;dr: how to handle build time dependencies between python modules
using buildout, without looking stupid or including .tar.gz files in my
repo.
numpy and scipy are a hell to install. I basically install them in the
OS and use the syseggrecipe to get the
On Mar 1, 2013 5:54 AM, Reinout van Rees rein...@vanrees.org wrote:
On 28-02-13 20:31, Ben Acland wrote:
tl;dr: how to handle build time dependencies between python modules
using buildout, without looking stupid or including .tar.gz files in my
repo.
numpy and scipy are a hell to install.
Where should these go / be defined?
The wheel project understands some setup.cfg extensions that are
important for Metadata 2.0 and wheel. The [metadata] section allows
you to override the setup(install_requires=[...]) with values
containing environment markers.
[metadata] also lets you specify
