On Thu, Apr 30, 2009 at 8:18 AM, Mihamina Rakotomandimby (R12y)
wrote:
> Hi all
> More and more python projects are "switching" to buildout.
> The one I face directly is Plone.
>
> I also administer servers and really love using their package management
> tools: If I use a Fedora (resp. Debian, Ge
Hi,
I have reworked the PEP a little bit with people feedback.
It needs more feedback : http://svn.python.org/projects/peps/trunk/pep-0376.txt
- install/uninstall script
I think the best solution is not to provide an install script since
third-party tool do it. Furthermore,
there's already
Hello,
I would like to make some decisions and move forward on three topics
for Distutils :
1/ version comparison : http://wiki.python.org/moin/Distutils/VersionComparison
2/ standardization of egg-info : PEP 376 +
http://wiki.python.org/moin/Distutils/StandardizeEggInfo
3/ changes in PKG-INFO
On Thu, 30 Apr 2009 09:16:15 +0200, Tarek Ziadé
wrote:
> The fact that this application might have a package present elsewhere
> on your system, maybe another version, is unavoidable today and your
> packager might say that it's a security whole, and that it makes it
harder
> for him to upgrade
On Thu, 30 Apr 2009 09:34:26 +0200, Tarek Ziadé
wrote:
> - install/uninstall script
>
> I think the best solution is not to provide an install script since
> third-party tool do it. Furthermore,
> there's already the simplest install script available today: you can
> run "python setup.py in
On Thu, Apr 30, 2009 at 2:11 PM, David Lyon wrote:
> As far as I can see, it's just so much better to have a
> package uninstaller in a seperate gui tool. That can be
> installed over an existing installation.
We are planning to propose a backport for previous versions
> The big problem with us
On Thu, 30 Apr 2009 14:23:41 +0200, Tarek Ziadé
wrote:
> We are planning to propose a backport for previous versions
ok
>> Not neccessary - recursively delete the whole package directory or
>> .egg file.
>
> No because you can have files installed anywhere
That's true that they can be insta
On Thu, Apr 30, 2009 at 2:35 PM, David Lyon wrote:
>>
>> No because you can have files installed anywhere
>
> That's true that they can be installed anywhere. But there always
> needs to be an entry in a .PTH file along the python path to
> specify where the files were installed to.
You don't spe
On Thu, 30 Apr 2009 14:43:42 +0200, Tarek Ziadé
wrote:
>> That's true that they can be installed anywhere. But there always
>> needs to be an entry in a .PTH file along the python path to
>> specify where the files were installed to.
>
> You don't specify in this pth file that the package "foo"
David Lyon wrote:
> If you have a deinstallation facility, then it must work for new
> packages as well as old. Otherwise, imho there's just no point.
>
It is impossible to uninstall a package if you don't have a recording of
what was installed. Removing every directories is a bad idea, as it m
On Thu, Apr 30, 2009 at 3:32 PM, David Lyon wrote:
>
>
> On Thu, 30 Apr 2009 14:43:42 +0200, Tarek Ziadé
> wrote:
>>> That's true that they can be installed anywhere. But there always
>>> needs to be an entry in a .PTH file along the python path to
>>> specify where the files were installed to.
>
Hi David,
On Thu, 30 Apr 2009 22:24:07 +0900, David Cournapeau
wrote:
> It is impossible to uninstall a package if you don't have a recording of
> what was installed.
Not true.
> Removing every directories is a bad idea, as it may
> remove files which were not installed by the package.
In
Hi Tarek,
On Thu, 30 Apr 2009 15:50:19 +0200, Tarek Ziadé
wrote:
>> But during package installation, this information will be written
>> into a .PTH file somewhere along the python path...
>
> No, you just have a list of relative paths to installed package there
> that's it.
It means the same t
On Thu, Apr 30, 2009 at 4:34 PM, David Lyon wrote:
> Hi Tarek,
>
> On Thu, 30 Apr 2009 15:50:19 +0200, Tarek Ziadé
> wrote:
>>> But during package installation, this information will be written
>>> into a .PTH file somewhere along the python path...
>>
>> No, you just have a list of relative path
On Thu, 30 Apr 2009 16:48:32 +0200, Tarek Ziadé
wrote:
> No, you don't have the exaustive list of the files installed.
My testing indicates that pkg_resources works ok.
>> --code---
>>
>> import pkg_resources
>>
>> ws = pkg_resources.WorkingSet()
>>
>> for i in ws:
>> s = str(i)
>>
On Thu, Apr 30, 2009 at 5:08 PM, David Lyon wrote:
> A typical user just wants to install package x,y and z from
> pypi. They want them to go "into python" and it is as simple
> as that. Those packages will probably end up in site-packages
> but as likely as not, the user won't care where they go
At 10:17 AM 4/30/2009 -0400, David Lyon wrote:
In summary... packages are just directories with an __init__.py
file in them. Sometimes they are zipped into eggs.
You are confusing "Python package" with "Python project". Projects
are zipped into eggs, and may contain zero or more
packages. P
On Thu, 30 Apr 2009 14:01:31 -0400, "P.J. Eby"
wrote:
> A distribution found on PyPI such as "FooBar-2.79" is the 2.79
> release of the *project* "FooBar"... this tells you absolutely
> nothing about the names of packages or modules contained in that project.
Ok - but that's hardly my fault...
Tarek,
On Thu, 30 Apr 2009 17:29:40 +0200, Tarek Ziadé
wrote:
> And then, as we said earlier, it will be impossible to uninstall packages
> that were previously uninstalled with some other techniques since we
won't have
> the info required.
Let's just accept this as your final position..
I'm l
David Lyon wrote:
>
> Let's just accept this as your final position..
>
> I'm led to believe that pip and enstaller both claim deinstallation of
> packages.
>
Yes - packages they have installed *themselves*. Nobody has ever claimed
that uninstallation is impossible - uninstallation of something
20 matches
Mail list logo
