Hi All,
I have the following buildout:
[buildout]
...
zeo_address = 127.0.0.1:2000
...
...
[zeo.conf]
recipe = collective.recipe.template
input = etc/zeo.conf.in
output = etc/zeo.conf
...and buildout complains that the zeo_address line isn't used, except
that it is, but collective.recipe.temp
2009/4/9 Lennart Regebro :
> On Wed, Apr 8, 2009 at 12:27, Paul Moore wrote:
>> 1. (Meta-requirement) I want to be able to download a Windows
>> installer[1] for *every* package I need.
>
> I would like to know why you have this requirement. Some sort of
> Windows binary, absolutely. But an instal
2009/4/9 zooko :
> On Apr 8, 2009, at 4:27 AM, Paul Moore wrote:
>
>> 1. (Meta-requirement) I want to be able to download a Windows installer[1]
>> for *every* package I need.
>> 1a. This means that the barrier for packagers building Windows installers
>> should be as low as possible.
>> 1b. It als
2009/4/9 David Cournapeau :
> Paul Moore wrote:
>> If not, why do people distribute eggs rather than bdist_wininst
>> installers?
>
> For python only code, I can see one obvious reason: you can build one
> egg on your platform, and it is supposed to work everywhere. I may be
> wrong, but I don't th
2009/4/9 Lennart Regebro :
> 2009/4/9 Paul Moore :
>> Don't they? I have to admit that I'm baffled by how the features in
>> setuptools/eggs/easy_install all hang together. What about the magic
>> that creates executables from scripts? Entry points? Stuff like that.
>> Don't you need to use eggs to
Paul Moore wrote:
Can any packager step up and explain why they execute "python setup.py
bdist_egg" rather than "python setup.py bdist_wininst" when creating
distributions for their Windows users?
I use both. If I'm installing a single package into a site-wide python,
I use bdist_wininst. If I
2009/4/9 Paul Moore :
> Don't they? I have to admit that I'm baffled by how the features in
> setuptools/eggs/easy_install all hang together. What about the magic
> that creates executables from scripts? Entry points? Stuff like that.
> Don't you need to use eggs to make them work?
No? Entry p
2009/4/9 Paul Moore :
> Personally, I'd be happy if every package that currently distributes
> any form of Windows binaries, distributed a Windows installer. That's
> about the same level of coverage as existed before setuptools
> appeared, so I don't think that's impossible to achieve. I agree tha
Paul Moore wrote:
> If not, why do people distribute eggs rather than bdist_wininst
> installers?
For python only code, I can see one obvious reason: you can build one
egg on your platform, and it is supposed to work everywhere. I may be
wrong, but I don't think packagers who care about windows a
2009/4/9 David Cournapeau :
> Ben Finney wrote:
>>
>> I presume, by “meta-requirement”, you're showing awareness that this
>> is something very much dependent on motivating people to actually
>> create those installers for each and every package.
>>
>
> Yes, and eggs decreases this motivation, as e
2009/4/9 Lennart Regebro :
> 2009/4/9 Paul Moore :
>> Personally, I'd be happy if every package that currently distributes
>> any form of Windows binaries, distributed a Windows installer. That's
>> about the same level of coverage as existed before setuptools
>> appeared, so I don't think that's i
Paul Moore wrote:
An
egg->bdist_wininst converter would fix this issue. As would everyone
standardising on bdist_wininst (which, as per the previous message,
appears to be prefectly feasible given that bdist_wininst seems to be
a strict superset of egg...)
I don't think this is true. I don't th
2009/4/9 Eric Smith :
> Paul Moore wrote:
>>
>> An
>> egg->bdist_wininst converter would fix this issue. As would everyone
>> standardising on bdist_wininst (which, as per the previous message,
>> appears to be prefectly feasible given that bdist_wininst seems to be
>> a strict superset of egg...)
On Apr 9, 2009, at 4:49 AM, Chris Withers wrote:
Hi All,
I have the following buildout:
[buildout]
...
zeo_address = 127.0.0.1:2000
...
...
[zeo.conf]
recipe = collective.recipe.template
input = etc/zeo.conf.in
output = etc/zeo.conf
...and buildout complains that the zeo_address line isn't
At 07:43 AM 4/9/2009 +0200, Lennart Regebro wrote:
I noticed when installing setuptools on Python 2.3 that easy_install
fails because it tries to import subprocess, which is a new module in
2.4. I personally do not need Python 2.3 support any longer, but the
docs say it should be supported, which
At 03:03 PM 4/9/2009 +0100, Paul Moore wrote:
2009/4/9 Eric Smith :
> Paul Moore wrote:
>>
>> An
>> egg->bdist_wininst converter would fix this issue. As would everyone
>> standardising on bdist_wininst (which, as per the previous message,
>> appears to be prefectly feasible given that bdist_wini
Jim Fulton wrote:
[buildout]
...
zeo_address = 127.0.0.1:2000
...
...
[zeo.conf]
recipe = collective.recipe.template
input = etc/zeo.conf.in
output = etc/zeo.conf
...and buildout complains that the zeo_address line isn't used, except
that it is, but collective.recipe.template.
I see no evi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I haven't heard back from Richard Jones, who is the PEP owner, but have
perpared to update PEP 345[1] in line with what to be the majority view
(at PyCon) for adding "distribution-level" dependency metadata (as
opposed to importable package / module de
Jim started a branch during Pycon, maybe you can push your work over
there for review here ?
Also, I am wondering if we shouldn't merge it with PEP 376, where we
might want to add a REQUIRES file
into the egg.info structure, besides the PKG-INFO file.
Cheers
Tarek
On Thu, Apr 9, 2009 at 6:55 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Moore wrote:
> 2009/4/9 Lennart Regebro :
>> 2009/4/9 Paul Moore :
>>> Don't they? I have to admit that I'm baffled by how the features in
>>> setuptools/eggs/easy_install all hang together. What about the magic
>>> that creates executables from s
Btw we also need to add some metadata that should be described in PEP
345 and added in PKG-INFO:
- maintainer and maintainer_email
see: http://bugs.python.org/issue3686
On Thu, Apr 9, 2009 at 7:05 PM, Tarek Ziadé wrote:
> Jim started a branch during Pycon, maybe you can push your work over
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tarek Ziadé wrote:
> Jim started a branch during Pycon, maybe you can push your work over
> there for review here ?
AFAICT, Jim hasn't checked anything into that branch:
> $ svndiff
> http://svn.python.org/projects/peps/{trunk,branches/jim-update-34
On Thu, Apr 9, 2009 at 7:31 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Tarek Ziadé wrote:
>> Jim started a branch during Pycon, maybe you can push your work over
>> there for review here ?
>
> AFAICT, Jim hasn't checked anything into that branch:
>
>> $ svndiff
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tarek Ziadé wrote:
> Btw we also need to add some metadata that should be described in PEP
> 345 and added in PKG-INFO:
>
> - maintainer and maintainer_email
>
> see: http://bugs.python.org/issue3686
Revised patch attached.
Tres.
- --
===
Hi,
I might be late and I haven't been to pycon but I've noted in this pep 345:
It is an attempt to re-invent the rpm spec file?
In this case how would you plan to integrate with the rpms dependecies?
Let me provide an usage scenario for packaging a generic rpm ("foobar"
from now on)
depending o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antonio Cavallo wrote:
> I might be late and I haven't been to pycon but I've noted in this
> pep 345:
>
> It is an attempt to re-invent the rpm spec file?
No, it is an attempt to provide Python-specific information about a
package in a machine-read
Tres Seaver schrieb:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Paul Moore wrote:
>> 2009/4/9 Lennart Regebro :
>>> 2009/4/9 Paul Moore :
Don't they? I have to admit that I'm baffled by how the features in
setuptools/eggs/easy_install all hang together. What about the magic
>>
Howdy,
Is there a recommended way to manage Debian system
packages with a buildout?
Thanks,
Kent
___
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
On Apr 9, 2009, at 3:37 PM, Kent Tenney wrote:
Howdy,
Is there a recommended way to manage Debian system
packages with a buildout?
I can't imagine why you would want to. I probably don't know what
you're asking.
Jim
--
Jim Fulton
Zope Corporation
_
On Thu, Apr 9, 2009 at 8:16 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Tarek Ziadé wrote:
>> Btw we also need to add some metadata that should be described in PEP
>> 345 and added in PKG-INFO:
>>
>> - maintainer and maintainer_email
>>
>> see: http://bugs.python.o
2009/4/9 Tres Seaver :
> Is there a technical reason why Windows users cannot build the
> installers themselves from "pure Python" sdists? I would rather
> distribute *no* binaries at all, myself, especially if "self-help"
> works. Stuff which requires a compiler is obviously a barrier for many
>
On Apr 9, 2009, at 11:34 AM, Chris Withers wrote:
Jim Fulton wrote:
[buildout]
...
zeo_address = 127.0.0.1:2000
...
...
[zeo.conf]
recipe = collective.recipe.template
input = etc/zeo.conf.in
output = etc/zeo.conf
...and buildout complains that the zeo_address line isn't used,
except that i
2009/4/9 Thomas Heller :
>> Is there a technical reason why Windows users cannot build the
>> installers themselves from "pure Python" sdists?
>
> No. There's even a script that automates the process completely. It allows
> to build bdist_wininst installers by drag and drop.
>
> http://code.active
Paul Moore wrote:
On that note, didn't ActiveState distribute their version of Python
with a package manager (PPM)? As far as I know, that was only ever
supported by ActiveState themselves, no-one else ever built PPM
packages for their extensions, and it's been quietly dropped in recent
versions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Moore wrote:
> 2009/4/9 Tres Seaver :
>> Is there a technical reason why Windows users cannot build the
>> installers themselves from "pure Python" sdists? I would rather
>> distribute *no* binaries at all, myself, especially if "self-help"
>> wo
On Thu, Apr 9, 2009 at 17:15, P.J. Eby wrote:
> There is no code in setuptools itself that uses subprocess. Are you sure
> it's not a plugin, or the package you're installing?
Yes, you are right, I got confused by the error message.
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.
On Thu, Apr 9, 2009 at 21:37, Kent Tenney wrote:
> Howdy,
>
> Is there a recommended way to manage Debian system
> packages with a buildout?
Do you mean make the buildout install .deb packages? You could build a
recipe, but it would only work on .deb systems, partly negating the
point of a buildo
On Thu, Apr 9, 2009 at 2:38 PM, Jim Fulton wrote:
>
> On Apr 9, 2009, at 3:37 PM, Kent Tenney wrote:
>
>> Howdy,
>>
>> Is there a recommended way to manage Debian system
>> packages with a buildout?
>
>
> I can't imagine why you would want to. I probably don't know what you're
> asking.
to get an
On Thu, Apr 9, 2009 at 3:24 PM, Lennart Regebro wrote:
> On Thu, Apr 9, 2009 at 21:37, Kent Tenney wrote:
>> Howdy,
>>
>> Is there a recommended way to manage Debian system
>> packages with a buildout?
>
> Do you mean make the buildout install .deb packages? You could build a
> recipe, but it wou
At 04:02 PM 4/9/2009 -0400, Tres Seaver wrote:
Warning: Can't read registry to find the necessary compiler setting
Make sure that Python modules _winreg, win32api or win32con are installed.
error:
/home/tseaver/projects/Zope-CVS/lib/python2.6/distutils/command/wininst-6.0ux-i686.exe:
No such file
On Apr 9, 2009, at 4:25 PM, Kent Tenney wrote:
On Thu, Apr 9, 2009 at 2:38 PM, Jim Fulton wrote:
On Apr 9, 2009, at 3:37 PM, Kent Tenney wrote:
Howdy,
Is there a recommended way to manage Debian system
packages with a buildout?
I can't imagine why you would want to. I probably don't kn
Hello,
This is a side discussion but quiet important ihmo.
== Problem ==
Some people complained about the fact that is was hard to extend
Distutils commands.
You end up rewriting the whole command most of the time.
So what's a command ? It's a class that is used by the distribution
instance whe
2009/4/9 Tres Seaver :
>> However, it's equally true (I believe) that "python setup.py
>> bdist_wininst" works fine on a Linux box. So it's not as if building
>> Windows installers is a huge chore for developers, either. (I accept
>> that there are other tasks, like distribution). It's a trade-off
Please fill an issue with this bug asap, so we can try to fix it
before Python 2.6.2 final is out
On Thu, Apr 9, 2009 at 10:29 PM, P.J. Eby wrote:
> At 04:02 PM 4/9/2009 -0400, Tres Seaver wrote:
>>
>> Warning: Can't read registry to find the necessary compiler setting
>> Make sure that Python m
Kent Tenney wrote:
> On Thu, Apr 9, 2009 at 3:24 PM, Lennart Regebro wrote:
>> On Thu, Apr 9, 2009 at 21:37, Kent Tenney wrote:
>>> Howdy,
>>>
>>> Is there a recommended way to manage Debian system
>>> packages with a buildout?
>> Do you mean make the buildout install .deb packages? You could bui
On Thu, Apr 9, 2009 at 4:26 PM, Kent Tenney wrote:
> On Thu, Apr 9, 2009 at 3:24 PM, Lennart Regebro wrote:
>> On Thu, Apr 9, 2009 at 21:37, Kent Tenney wrote:
>>> Howdy,
>>>
>>> Is there a recommended way to manage Debian system
>>> packages with a buildout?
>>
>> Do you mean make the buildout
2009/4/9 Tres Seaver :
> creating dist
> Warning: Can't read registry to find the necessary compiler setting
> Make sure that Python modules _winreg, win32api or win32con are installed.
This is a warning, so can be ignored.
> error:
> /home/tseaver/projects/Zope-CVS/lib/python2.6/distutils/comman
P.J. Eby wrote:
> At 04:02 PM 4/9/2009 -0400, Tres Seaver wrote:
>> Warning: Can't read registry to find the necessary compiler setting
>> Make sure that Python modules _winreg, win32api or win32con are
>> installed.
>> error:
>> /home/tseaver/projects/Zope-CVS/lib/python2.6/distutils/command/winin
On Thu, Apr 9, 2009 at 10:52 PM, Paul Moore wrote:
> 2009/4/9 Tres Seaver :
>> creating dist
>> Warning: Can't read registry to find the necessary compiler setting
>> Make sure that Python modules _winreg, win32api or win32con are installed.
>
> This is a warning, so can be ignored.
>
>> error:
>>
On Apr 9, 2009, at 3:37 AM, Paul Moore wrote:
I personally, as a consumer of other people's software, prefer to
acquire their packages as sdist .tar.gz's or as .eggs on all
platforms, including Windows, which I use regularly. So your and
my preferences as a consumer of packages differ on
>
> If I file a bug and it gets fixed, will you build installers for me? :-)
>
> (Seriously, thanks for trying this and locating the bug. I've raised
> it as http://bugs.python.org/issue5731).
fixed in the trunk, r71413,
I am now backporting it in the 2.6 maintenance branch, but I'd
appreciate an
At 01:54 PM 4/9/2009 -0700, Andrew Straw wrote:
P.J. Eby wrote:
> At 04:02 PM 4/9/2009 -0400, Tres Seaver wrote:
>> Warning: Can't read registry to find the necessary compiler setting
>> Make sure that Python modules _winreg, win32api or win32con are
>> installed.
>> error:
>>
/home/tseaver/proj
On Thu, Apr 09, 2009 at 10:24:18AM +0100, Paul Moore wrote:
> 2009/4/9 Lennart Regebro :
> > On Wed, Apr 8, 2009 at 12:27, Paul Moore wrote:
> >> 1. (Meta-requirement) I want to be able to download a Windows
> >> installer[1] for *every* package I need.
> >
> > I would like to know why you have th
On Apr 9, 2009, at 12:55 PM, Tres Seaver wrote:
...
I have backed off on the notion of overloading 'Requires:' /
'Provides:'
/ 'Obsoletes:', following Jim's notion of deprecating them in favor of
new fields. I named them 'Requires-Dist:', 'Provides-Dist:', and
'Obsoletes-Dist'.
"Stock" distu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> On Apr 9, 2009, at 12:55 PM, Tres Seaver wrote:
> ...
>> I have backed off on the notion of overloading 'Requires:' /
>> 'Provides:'
>> / 'Obsoletes:', following Jim's notion of deprecating them in favor of
>> new fields. I named
Paul Moore wrote:
If I have to guess at your reasons, my assumption would be:
- Consistent means of installing on all platforms
- ???
I can imagine that people for whom Windows is not their
primary platform might like to be able to install Python
packages the same way they do on other platform
Paul Moore wrote:
Personally, I'd be happy if every package that currently distributes
any form of Windows binaries, distributed a Windows installer. ...
> I agree that
expecting *everything* to have a Windows installer is unreasonable.
Would it be feasible to have a generic installer for
.e
Marius Gedminas wrote:
>
> But that list is for *programs*, not *libraries*.
>
The difference starts to be blurry for python (is numpy an application
or a library ?), and it does not make much sense for windows users, I think.
> I don't understand a desire of downloading twenty .exe files and
58 matches
Mail list logo
