On 11-02-13 08:46, Adam GROSZER wrote:
That caused a severe heartattack on winbot. :-S
Any advices what to do?
I *think* the basic solution is to use a newer bootstrap.
buildout 1.7 and 2.0 include a build-in version restriction to 2.0 and
=2.0 respectively to prevent accidental updates. The
On 11/02/2013 09:02, Reinout van Rees wrote:
On 11-02-13 08:46, Adam GROSZER wrote:
That caused a severe heartattack on winbot. :-S
Any advices what to do?
I *think* the basic solution is to use a newer bootstrap.
buildout 1.7 and 2.0 include a build-in version restriction to 2.0 and
=2.0
On 11-02-13 10:29, Chris Withers wrote:
I *think* the basic solution is to use a newer bootstrap.
buildout 1.7 and 2.0 include a build-in version restriction to 2.0 and
=2.0 respectively to prevent accidental updates. The latest bootstraps
use that.
On 10-02-13 19:24, Jim Fulton wrote:
I'm very happy, finally, to have released buildout 2.0.0.
What's being picked:
zc.buildout = 2.0.0
zc.recipe.egg = 2.0.0a3
Shouldn't zc.recipe.egg be tagged as 2.0.0 final, too?
Reinout
--
Reinout van Reeshttp://reinout.vanrees.org/
On Sun, Feb 10, 2013 at 09:09:12AM -0600, Skip Montanaro wrote:
At work we use encap to create packages to distribute to our desktops
and server. Creating a package involves installing it into an
isolated directory, then creating an encap package from the
directory's contents. Packages which
On Mon, Feb 11, 2013 at 4:46 AM, Reinout van Rees rein...@vanrees.org wrote:
On 10-02-13 19:24, Jim Fulton wrote:
I'm very happy, finally, to have released buildout 2.0.0.
What's being picked:
zc.buildout = 2.0.0
zc.recipe.egg = 2.0.0a3
Shouldn't zc.recipe.egg be tagged as 2.0.0 final,
On Mon, Feb 11, 2013 at 2:46 AM, Adam GROSZER agroszer...@gmail.com wrote:
Hello,
That caused a severe heartattack on winbot. :-S
Could you be more specific?
Jim
--
Jim Fulton
http://www.linkedin.com/in/jimfulton
Jerky is better than bacon! http://zo.pe/Kqm
On 02/11/2013 10:02 AM, Reinout van Rees wrote:
On 11-02-13 08:46, Adam GROSZER wrote:
That caused a severe heartattack on winbot. :-S
Any advices what to do?
I *think* the basic solution is to use a newer bootstrap.
buildout 1.7 and 2.0 include a build-in version restriction to 2.0 and
On 02/11/2013 01:54 PM, Jim Fulton wrote:
On Mon, Feb 11, 2013 at 2:46 AM, Adam GROSZER agroszer...@gmail.com wrote:
Hello,
That caused a severe heartattack on winbot. :-S
Could you be more specific?
Jim
nm, Reinout's solution worked. Was an old bootstrap.py
--
Best regards,
Adam
On 2013-02-06 08:15:15 +, Nick Coghlan said:
As folks may be aware, I am moderating a panel called Directions in
Packaging on the Saturday afternoon at PyCon US.
Excellent - looking forward to join you!
Christian
___
Distutils-SIG maillist -
Jim Fulton j...@zope.com writes:
I'm very happy, finally, to have released buildout 2.0.0.
I'm happy too, congrats to everybody contributed!
Much has changed from buildout 1:
http://pypi.python.org/pypi/zc.buildout/2.0.0#id3
* Buildout no-longer tries to provide full or partial isolation
Projects which wish to use non-compliant version identifiers must
restrict themselves to metadata v1.1
currently, Projects don't have control over this, right?
setuptools/distutils just writes 1.0 or 1.1 metadata, period.
maybe that can be clarified for me and others.
what can a project really
Hi everybody,
I think I pretty much read all of the
http://docs.python.org/2/distutils/and started to create a pypi
repository for my project (
http://pypi.python.org/pypi/monk_tf). Now there are some things that are
not so clear from the documentation, with the most important being
requirement
On Mon, Feb 11, 2013 at 1:10 PM, Erik Bernoth erik.bern...@gmail.comwrote:
Hi everybody,
I think I pretty much read all of the http://docs.python.org/2/distutils/and
started to create a pypi repository for my project (
http://pypi.python.org/pypi/monk_tf). Now there are some things that are
This is a common mistake. The parenthesis are a Metadata 1.2+ thing. Omit
them for distutils.
On Mon, Feb 11, 2013 at 2:22 PM, Erik Bernoth erik.bern...@gmail.comwrote:
On Mon, Feb 11, 2013 at 8:07 PM, Daniel Holth dho...@gmail.com wrote:
On Mon, Feb 11, 2013 at 1:10 PM, Erik Bernoth
Try install_requires = [ the list you have already without () ]
Daniel
On Mon, Feb 11, 2013 at 2:32 PM, Erik Bernoth erik.bern...@gmail.comwrote:
I basically follow the tutorial in the distutils docs, which is a little
unclear to me in some points.
If I do as you say it looks like this:
Not really. Install_requires is a setup tools/distribute feature.
On Feb 11, 2013 2:52 PM, Erik Bernoth erik.bern...@gmail.com wrote:
Yes, now it works! Thanks a lot! Last but not least, could you point me in
the correct direction to add a patch for the distutils documentation,
explaining this
On Mon, Feb 11, 2013 at 8:07 PM, Daniel Holth dho...@gmail.com wrote:
On Mon, Feb 11, 2013 at 1:10 PM, Erik Bernoth erik.bern...@gmail.comwrote:
Hi everybody,
I think I pretty much read all of the http://docs.python.org/2/distutils/and
started to create a pypi repository for my project (
I basically follow the tutorial in the distutils docs, which is a little
unclear to me in some points.
If I do as you say it looks like this:
--
[...]
package_dir = { '' : src_path },
requires = [
'pylibssh2==1.0.1',
Yes, now it works! Thanks a lot! Last but not least, could you point me in
the correct direction to add a patch for the distutils documentation,
explaining this more clearly?
On Mon, Feb 11, 2013 at 8:34 PM, Daniel Holth dho...@gmail.com wrote:
Try install_requires = [ the list you have
Sorry, I didn't know that this is not part of distutils. In my
understanding pip, setup.py and so on is all part of distutils. Should I
have asked my question on another mailing list? Then even more thanks for
the great help!
On Mon, Feb 11, 2013 at 8:55 PM, Daniel Holth dho...@gmail.com wrote:
Marius Gedminas marius at pov.lt writes:
Not distutils, but setuptools (or its fork distribute).
The EASY-INSTALL-ENTRY-SCRIPT comment is a hint.
...
Thanks for the hint. I will admit to just using this stuff blindly.
I am certainly no packaging or distutils (or setuptools) expert.
A
On Mon, Feb 11, 2013 at 11:40 AM, Alessandro Dentella san...@e-den.it wrote:
I believe that this issue belongs to this list, please let me know if I'm
wrong.
Suppose I have 2 packages:
jmb.foo
jmb.bar
distributed separately. Each has in jmb's __init__ a standard:
On Mon, Feb 11, 2013 at 1:06 PM, Skip Montanaro s...@pobox.com wrote:
Marius Gedminas marius at pov.lt writes:
Not distutils, but setuptools (or its fork distribute).
The EASY-INSTALL-ENTRY-SCRIPT comment is a hint.
...
Thanks for the hint. I will admit to just using this stuff blindly.
I
On 12 Feb 2013 07:56, Alessandro Dentella san...@e-den.it wrote:
On Mon, Feb 11, 2013 at 04:11:38PM -0500, PJ Eby wrote:
On Mon, Feb 11, 2013 at 11:40 AM, Alessandro Dentella san...@e-den.it
wrote:
I believe that this issue belongs to this list, please let me know if
I'm
wrong.
On Mon, Feb 11, 2013 at 1:37 PM, Marcus Smith qwc...@gmail.com wrote:
Projects which wish to use non-compliant version identifiers must
restrict themselves to metadata v1.1
currently, Projects don't have control over this, right?
setuptools/distutils just writes 1.0 or 1.1 metadata, period.
Projects which wish to use non-compliant version identifiers must
restrict themselves to metadata v1.1
currently, Projects don't have control over this, right?
setuptools/distutils just writes 1.0 or 1.1 metadata, period.
maybe that can be clarified for me and others.
what can a project
On Mon, Feb 11, 2013 at 10:18 PM, Daniel Holth dho...@gmail.com wrote:
On Mon, Feb 11, 2013 at 1:37 PM, Marcus Smith qwc...@gmail.com wrote:
Projects which wish to use non-compliant version identifiers must
restrict themselves to metadata v1.1
currently, Projects don't have control over
On Mon, Feb 11, 2013 at 8:01 PM, Daniel Holth dho...@gmail.com wrote:
On Mon, Feb 11, 2013 at 10:18 PM, Daniel Holth dho...@gmail.com wrote:
On Mon, Feb 11, 2013 at 1:37 PM, Marcus Smith qwc...@gmail.com wrote:
Projects which wish to use non-compliant version identifiers must
restrict
On Mon, Feb 11, 2013 at 4:56 PM, Alessandro Dentella san...@e-den.it wrote:
thanks for the answer but this way I need to really import jmb while
imp.find_module doesn't really import it.
If you want to know whether the module 'jmb' exists, you can certainly
do that by using
Le 11/02/2013 13:37, Marcus Smith a écrit :
Projects which wish to use non-compliant version identifiers must
restrict themselves to metadata v1.1
currently, Projects don't have control over this, right?
setuptools/distutils just writes 1.0 or 1.1 metadata, period.
Yep, but projects can
On Tuesday, February 12, 2013 at 12:13 AM, Éric Araujo wrote:
Le 11/02/2013 13:37, Marcus Smith a écrit :
Projects which wish to use non-compliant version identifiers must
restrict themselves to metadata v1.1
currently, Projects don't have control over this, right?
On Mon, Feb 11, 2013 at 9:36 PM, Donald Stufft donald.stu...@gmail.comwrote:
On Tuesday, February 12, 2013 at 12:13 AM, Éric Araujo wrote:
Le 11/02/2013 13:37, Marcus Smith a écrit :
Projects which wish to use non-compliant version identifiers must
restrict themselves to metadata v1.1
33 matches
Mail list logo
