stdeb (setuptools debian) produces Debian source packages from Python
packages via a new distutils command, sdist_dsc. Automatic defaults are
provided for the Debian package, but many aspects of the resulting
package can be customized via a configuration file.
This new release, 0.2.2, adds
I'd be delighted to see someone working on this. However, in my ideal
world, this would be something that integrated with IDLE. I know tk is
not a patch on wx, but it is an included battery.
On Wed, Jan 28, 2009 at 10:11 PM, david.l...@preisshare.net wrote:
Hi All,
I am a developer from
What's the safe way of detecting plugins in a package that is potentially
zipped?
Thanks,
Arve
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
Le mercredi 28 janvier 2009 à 07:44 -0700, zooko a écrit :
3. It would be okay for this process to be automated (or semi-
automated), but there's some flaw in the design of stdeb which means
it will never be able to do it right unless stdeb is rewritten with a
new design.
This is the
Le mercredi 28 janvier 2009 à 13:16 -0600, Ian Bicking a écrit :
As you mention, there would have to be some extension to pkg_resources
(or an equivalent library) to handle finding these files at runtime.
Getting a runtime in place is probably the harder thing, as it is more
intrusive for the
Le mercredi 28 janvier 2009 à 08:07 -0500, Barry Warsaw a écrit :
I'd like to make a radical suggestion: upstream authors should never
have to worry about building distribution blobs.
This is just silly. You don’t have to worry about the distribution’s
internals, and what is specific to each
Le mercredi 28 janvier 2009 à 21:18 -0500, david.l...@preisshare.net a
écrit :
Sometimes it is easier under linux to get an operating system python
package (from debian for example) installed than it is to get a pure python
package...
That seems very wrong to me.
So I am agreeing...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 8:57 AM, Josselin Mouette wrote:
Le mercredi 28 janvier 2009 à 08:07 -0500, Barry Warsaw a écrit :
I'd like to make a radical suggestion: upstream authors should never
have to worry about building distribution blobs.
This is
On Thu, Jan 29, 2009 at 15:35, Barry Warsaw ba...@python.org wrote:
That's not what I'm saying. What I'm really saying is that I don't want to
have to run 5 different setup.py commands every time I do a release in order
to upload all the possible distribution formats that my users may want.
Lennart Regebro wrote:
On Thu, Jan 29, 2009 at 15:35, Barry Warsaw ba...@python.org wrote:
That's not what I'm saying. What I'm really saying is that I don't want to
have to run 5 different setup.py commands every time I do a release in order
to upload all the possible distribution formats
On Thu, 29 Jan 2009 09:35:18 -0500, Barry Warsaw ba...@python.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 8:57 AM, Josselin Mouette wrote:
Le mercredi 28 janvier 2009 à 08:07 -0500, Barry Warsaw a écrit :
I'd like to make a radical suggestion: upstream authors
On Thu, Jan 29, 2009 at 15:55, Eric Smith e...@trueblade.com wrote:
Someone should, true. But it need not be the original author, who might not
have the ability to test (or even produce) every desirable distribution
format.
Absolutely. But this is already the case, you don't have to make and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 10:03 AM, Jean-Paul Calderone wrote:
Barry, just have your buildbot do it for you - and not just when you
do a
release, but every time you commit. As a bonus, it can then install
the
packages and run your test suite and tell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 9:51 AM, Lennart Regebro wrote:
On Thu, Jan 29, 2009 at 15:35, Barry Warsaw ba...@python.org wrote:
That's not what I'm saying. What I'm really saying is that I don't
want to
have to run 5 different setup.py commands every
Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 10:03 AM, Jean-Paul Calderone wrote:
Barry, just have your buildbot do it for you - and not just when you do a
release, but every time you commit. As a bonus, it can then install the
packages and run your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry Warsaw wrote:
On Jan 29, 2009, at 8:57 AM, Josselin Mouette wrote:
Le mercredi 28 janvier 2009 à 08:07 -0500, Barry Warsaw a écrit :
I'd like to make a radical suggestion: upstream authors should never
have to worry about building
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 12:17 PM, Tres Seaver wrote:
Barry Warsaw wrote:
On Jan 29, 2009, at 8:57 AM, Josselin Mouette wrote:
Le mercredi 28 janvier 2009 à 08:07 -0500, Barry Warsaw a écrit :
I'd like to make a radical suggestion: upstream authors
On Thu, Jan 29, 2009 at 16:49, Barry Warsaw ba...@python.org wrote:
That's what users, continuous integration, and and bug reports are for!
Yes, and if you have that, then you also have automatically generated
packages, which you can upload to pypi.
--
Lennart Regebro: Zope and Plone
On Thu, Jan 29, 2009 at 7:53 AM, Josselin Mouette j...@debian.org wrote:
Le mercredi 28 janvier 2009 à 13:16 -0600, Ian Bicking a écrit :
As you mention, there would have to be some extension to pkg_resources
(or an equivalent library) to handle finding these files at runtime.
Getting a
On Thu, Jan 29, 2009 at 12:20:22PM -0500, Barry Warsaw wrote:
On Jan 29, 2009, at 12:17 PM, Tres Seaver wrote:
Barry Warsaw wrote:
On Jan 29, 2009, at 8:57 AM, Josselin Mouette wrote:
Le mercredi 28 janvier 2009 à 08:07 -0500, Barry Warsaw a écrit :
I'd like to make a radical suggestion:
david.l...@preisshare.net wrote:
I don't think that the missing of a gui is what is the problem today
for python. Package uninstall is something that bothers some (maybe a
lot) of users.
Yeah. Me too. Possibly made easier by having a GUI.
The biggest problem is that the installer
On Jan 29, 2009, at 7:01 PM, Mark Sienkiewicz wrote:
david.l...@preisshare.net wrote:
I don't think that the missing of a gui is what is the problem today
for python. Package uninstall is something that bothers some
(maybe a
lot) of users.
Yeah. Me too. Possibly made easier by having a
Josselin Mouette j...@debian.org writes:
Le mercredi 28 janvier 2009 à 13:16 -0600, Ian Bicking a écrit :
As you mention, there would have to be some extension to
pkg_resources (or an equivalent library) to handle finding these
files at runtime. Getting a runtime in place is probably the
On Thu, Jan 29, 2009 at 10:51 PM, Ben Finney ben+pyt...@benfinney.id.au wrote:
Josselin Mouette j...@debian.org writes:
Le mercredi 28 janvier 2009 à 13:16 -0600, Ian Bicking a écrit :
As you mention, there would have to be some extension to
pkg_resources (or an equivalent library) to
I very much dislike things that automatically download and install
software. An automatic installer may find a different version of a
supporting package every time I install software on another machine.
if the application asks for the different version then yes it should
download the
On Jan 29, 2009, at 8:29 PM, Mark Sienkiewicz wrote:
I very much dislike things that automatically download and install
software. An automatic installer may find a different version of
a supporting package every time I install software on another
machine.
if the application asks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Finney wrote:
Josselin Mouette j...@debian.org writes:
Le mercredi 28 janvier 2009 à 13:16 -0600, Ian Bicking a écrit :
As you mention, there would have to be some extension to
pkg_resources (or an equivalent library) to handle finding these
On Thu, Jan 29, 2009 at 11:50 PM, Tres Seaver tsea...@palladion.com wrote:
Perhaps 'setup_config.py'? Something that makes it clear that the
configuration is intended for the setup and installation, *not* the
running Python package.
I would argue against making it a .py file at all: make it
Tarek Ziadé ziade.ta...@gmail.com writes:
On Thu, Jan 29, 2009 at 10:51 PM, Ben Finney ben+pyt...@benfinney.id.au
wrote:
Perhaps 'setup_config.py'? Something that makes it clear that the
configuration is intended for the setup and installation, *not*
the running Python package.
what
On Thu, Jan 29, 2009 at 11:54:38PM +0100, Tarek Ziadé wrote:
On Thu, Jan 29, 2009 at 11:50 PM, Tres Seaver tsea...@palladion.com wrote:
Perhaps 'setup_config.py'? Something that makes it clear that the
configuration is intended for the setup and installation, *not* the
running Python
On Fri, Jan 30, 2009 at 12:34 AM, Floris Bruynooghe
floris.bruynoo...@gmail.com wrote:
setup.cfg could be used in that case.
setup.cfg is a configuration file to be edited by developers. Going
to modify that at build time is guaranteed to result in unhappy people
at some stage I reckon.
On Thu, 29 Jan 2009 12:17:16 +, phil jones inters...@gmail.com wrote:
I'd be delighted to see someone working on this. However, in my ideal
world, this would be something that integrated with IDLE. I know tk is
not a patch on wx, but it is an included battery.
Thanks Phil.
My skills
On Thu, 29 Jan 2009 17:29:28 -0500, Mark Sienkiewicz sienk...@stsci.edu
wrote:
I very much dislike things that automatically download and install
software. An automatic installer may find a different version of a
supporting package every time I install software on another machine.
..
..
Hello
Many people are asking for an uninstall command. While there are
possible side-effects when removing all installed files,
I think it worths it...
I would like to introduce an uninstall command in distutils, using
Marc-André Lemburg's mxSetup tool
(see
david.l...@preisshare.net writes:
What I need for myself, is a package manifest, tracking all the
packages that I have installed. Then when I go set up on a new
machine, I can load the manifest, and the tool will go get me all my
packages.
So I totally agree with your comments... that is
Hi Ben,
On Fri, 30 Jan 2009 13:04:30 +1100, Ben Finney ben+pyt...@benfinney.id.au
wrote:
An interface is premature if the manifest doesn't yet exist. Let's
solve that problem before thinking of a GUI for it.
I can see your point there..
From the other perspective, it is a fairly trivial task
Enthought has a package called Enstaller which includes a modified
version of setuptools + an enstaller package that adds some different
functionality. One of the modifications to setuptools adds an uninstall
command which works well with our .egg's. Dealing with eggs allows us
to do some
On Thu, Jan 29, 2009 at 6:49 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Next, (in a second step) I was wondering if a uninstall registery
could not be a good thing to have,
to store a record of the installed files so there's no need to keep
the source for uninstallation.
This would
Ian Bicking schrieb:
On Thu, Jan 29, 2009 at 6:49 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
Next, (in a second step) I was wondering if a uninstall registery
could not be a good thing to have,
to store a record of the installed files so there's no need to keep
the source for
39 matches
Mail list logo
