2009/9/19 P.J. Eby p...@telecommunity.com
If they use the package's __path__ attribute, they'll find its contents,
whether someone is using pkgutil.extend_path, .pth files, or setuptools.
They don't have to support setuptools to support namespace packages, just pay
attention to the
2009/9/20 Kyle MacFarlane kylemacfarl...@gmail.com:
I was hoping more if anybody knew a recipe to get round my problem but
I had a look inside Django to see how it looks through packages.
The problem is caused by line 58 at this link raising an ImportError:
It is not mentioned in Fedora guidelines
http://fedoraproject.org/wiki/Packaging/Guidelines#Packaging_Guidelines
Neither is explicitly said on any other linux distro: it is experience coming
from building rpms that span across distros and releases.
If you type rpm -qa --scripts on a running
Symlink is pointing to x86_64 arch file, i would like to have noarch rpm.
It is pointing to /usr/bin/consolehelper as application needs to be run
with root rights.
I might be doing something wrong here but this is my first package.
Although the target (/usr/bin/consolehelper) of the
Dnia piątek 18 września 2009 o 23:43:08 David Malcolm napisał(a):
On Fri, 2009-09-18 at 22:22 +0200, Michał Klich wrote:
Dnia piątek 18 września 2009 o 22:00:17 David Malcolm napisał(a):
On Fri, 2009-09-18 at 21:55 +0200, Michał Klich wrote:
Dnia czwartek 17 września 2009 o 23:07:17 A.
Dnia niedziela 20 września 2009 o 12:30:15 A. Cavallo napisał(a):
Symlink is pointing to x86_64 arch file, i would like to have noarch
rpm. It is pointing to /usr/bin/consolehelper as application needs to
be run with root rights.
I might be doing something wrong here but this is my
2009/9/20 Jim Fulton j...@zope.com:
That's BS. This discussion is is happening because Django is using
buildout, which I think qualifies as non-Django stuff.
OK, maybe that was not the right wording.
Even if this argument had a shred of reason, it is totally
inappropriate to use a response
On Sun, Sep 20, 2009 at 4:56 AM, Lennart Regebro rege...@gmail.com wrote:
2009/9/20 Kyle MacFarlane kylemacfarl...@gmail.com:
I was hoping more if anybody knew a recipe to get round my problem but
I had a look inside Django to see how it looks through packages.
The problem is caused by line
Hello,
The next Distribute version will be released soon, with python 3
support (thanks to Martin, Lennart, and Alex !)
and more bug fixed. (you can follow that in the issue tracker)
If you want to give a hand on testing the next Distribute version,
I've uploaded a dev version of the trunk of
On Sun, Sep 20, 2009 at 3:03 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
- a modified bootstrap.py file that will let you bootstrap a
zc.buildout environment with this version
link: http://nightly.ziade.org/bootstrap.py
___
Distutils-SIG maillist
2009/9/20 Kyle MacFarlane kylemacfarl...@gmail.com
2009/9/19 P.J. Eby p...@telecommunity.com
If they use the package's __path__ attribute, they'll find its contents,
whether someone is using pkgutil.extend_path, .pth files, or setuptools.
They don't have to support setuptools to support
At 09:17 AM 9/20/2009 +0100, Kyle MacFarlane wrote:
2009/9/19 P.J. Eby p...@telecommunity.com
If they use the package's __path__ attribute, they'll find its
contents, whether someone is using pkgutil.extend_path, .pth files,
or setuptools. Â They don't have to support setuptools to support
Gerry Reno wrote:
In my setup.py I have my own install:
from distutils.command.install import install
...
class myinstall(install):
...
and when we call dpkg-buildpackage this local install seems to maybe
be causing the problem with the error: option
--single-version-externally-managed
Andrew Straw wrote:
Gerry Reno wrote:
In my setup.py I have my own install:
from distutils.command.install import install
...
class myinstall(install):
...
and when we call dpkg-buildpackage this local install seems to maybe
be causing the problem with the error: option
In my setup.py I have my own install:
from distutils.command.install import install
...
class myinstall(install):
...
and when we call dpkg-buildpackage this local install seems to maybe
be causing the problem with the error: option
--single-version-externally-managed not recognized.
How
Gerry Reno wrote:
Andrew Straw wrote:
Gerry Reno wrote:
In my setup.py I have my own install:
from distutils.command.install import install
...
class myinstall(install):
...
and when we call dpkg-buildpackage this local install seems to maybe
be causing the problem with the error:
Hi Tarek,
When do you plan to make a 'final' release of this version (0.6.2)?
Attila
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
Andrew Straw wrote:
Gerry Reno wrote:
Andrew Straw wrote:
Gerry Reno wrote:
In my setup.py I have my own install:
from distutils.command.install import install
...
class myinstall(install):
...
and when we call dpkg-buildpackage this local install seems to maybe
be causing
Gerry Reno wrote:
How do I get stdeb 0.4?
The easiest way:
git clone git://github.com/astraw/stdeb.git
cd stdeb
sudo python setup.py install
If you want a tarball, please look at my email 09/19/2009 09:36 PM -0700.
For bdist_rpm the way that you get pre and postpackage install scripts
to
Andrew Straw wrote:
Gerry Reno wrote:
How do I get stdeb 0.4?
The easiest way:
git clone git://github.com/astraw/stdeb.git
cd stdeb
sudo python setup.py install
If you want a tarball, please look at my email 09/19/2009 09:36 PM -0700.
Ok, I'll install 0.4 using one of these
Gerry Reno wrote:
Andrew Straw wrote:
Gerry Reno wrote:
How do I get stdeb 0.4?
The easiest way:
git clone git://github.com/astraw/stdeb.git
cd stdeb
sudo python setup.py install
If you want a tarball, please look at my email 09/19/2009 09:36 PM
-0700.
Ok, I'll install 0.4 using one of
Gerry Reno wrote:
It's going to be tough to get stdeb running on Ubuntu 8.0.4 LTS.
Well, I'd qualify that with stdeb version 0.4 may be more tough to get
running. It is the bleeding edge, after all. :) 0.3 works as well as it
ever did, but new features are going into 0.4.
But now that you
Andrew Straw wrote:
Gerry Reno wrote:
It's going to be tough to get stdeb running on Ubuntu 8.0.4 LTS.
Well, I'd qualify that with stdeb version 0.4 may be more tough to get
running. It is the bleeding edge, after all. :) 0.3 works as well as it
ever did, but new features are going
Gerry Reno wrote:
Andrew Straw wrote:
Gerry Reno wrote:
It's going to be tough to get stdeb running on Ubuntu 8.0.4 LTS.
Well, I'd qualify that with stdeb version 0.4 may be more tough to get
running. It is the bleeding edge, after all. :) 0.3 works as well as it
ever did, but new
Andrew Straw wrote:
Gerry Reno wrote:
Andrew Straw wrote:
Gerry Reno wrote:
It's going to be tough to get stdeb running on Ubuntu 8.0.4 LTS.
Well, I'd qualify that with stdeb version 0.4 may be more tough to get
running. It is the bleeding edge, after all. :)
On Fri, 18 Sep 2009 11:17:40 +0100, Chris Withers ch...@simplistix.co.uk
wrote:
A lot of these problems would go away if we could just treat Python as
a package like every other package when it comes to dependencies.
Why is that so hard to do?
It's not hard at all.
But somebody needs to
On Wed, 16 Sep 2009 23:34:07 -0400, P.J. Eby p...@telecommunity.com
wrote:
An application needs to know what directory it has been installed
in and where it can find configuration files and so forth.
It appears I was unclear: it is not the application's business to
*decide* what the
Gerry Reno wrote:
Ok, here is the simplest way that I got stdeb working on Hardy:
$ easy_install stdeb # installs 0.3
copied stdeb egg to workarea and edited util.py and removed all
--single-version-externally-managed options
repackaged egg
copied egg back to site-packages
OK, but now your
At 10:26 PM 9/20/2009 -0400, David Lyon wrote:
Eh? It's *possible* to specify it in those places now, but
well-behaved packages never do.
Not on windows, outside of the c:\pythonXY directory.
Create a setup.cfg with an [install] section and you can make it
install wherever you tell it
On Sun, 20 Sep 2009 23:58:06 -0400, P.J. Eby p...@telecommunity.com
wrote:
If you are saying that Python observes all microsofts
recommendations under windows and is well-behaved I think
I'd have some comments about that.
Well behaved is installing a python program to Program Files
but distutils
Gerry Reno wrote:
Andrew Straw wrote:
Gerry Reno wrote:
Ok, here is the simplest way that I got stdeb working on Hardy:
$ easy_install stdeb # installs 0.3
copied stdeb egg to workarea and edited util.py and removed all
--single-version-externally-managed options
repackaged egg
copied
31 matches
Mail list logo
