From my experience in building all the pypi packages, I can confirm that a
significant number of packages (> 10 at least), fail to build[1] because
it cannot read a file (usually LICENSE.txt, version.txt, README.txt in the
sdist root) using __file__.
It is unfortunate that we have this mess
Hey Guys,
I guess nobody knows or cares. Where do the Win32 python guys hang
out?
J.D.
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
The following file gives the list of all packages in PyPI and their
'install_requires' (or 'requires').
http://files.getdropbox.com/u/87045/x/pypi-dependency.txt
This list does not include (most of the) packages that have external
downloads.
-srid
2009/7/15 Sridhar Ratnakumar :
> On Wed, 15 Jul 2009 02:01:24 -0700, Tarek Ziadé
> wrote:
>
get_installed_files(local=False) -> iterator of (path, md5, size)
>>>
>>> Will this also return the directories /created/ during the installation?
>>> For example, will it also contain the entry "docut
Hello,
We have started a new project called 'Distribute'. It's a fork of
setuptools and its initial purpose will be to tackle
the most annoying bugs found in setuptools 0.6c9 version.
A first version will be released as soon as possible (probably next
monday) and a document will explain how to mi
On Wed, 15 Jul 2009 13:47:35 -0400, Chris McDonough
wrote:
> I've been trying to follow this discussion now for weeks. The signal to
> noise ratio is pretty low.
I'm -1 on that..
As a relative newcomer to python packaging I'm finding all these
discussions very informative. :-)
> I'd love to hav
2009/7/15 Chris McDonough :
> I've been trying to follow this discussion now for weeks. The signal to
> noise ratio is pretty low.
I agree :-(
> I'd love to have an stdlib solution for distribution packaging and
> installation. But I think we might as well pack it up and go home if the
> folks w
On Wed, Jul 15, 2009 at 01:43:19PM -0400, Terry Reedy wrote:
> Paul Moore wrote:
>
>
>> - how do I import version 0.7.1 of package foo, rather than 0.7.2?
>
> Augment import to recognize versioned names?
>
> import foo_0_7_1
If people just renamed their modules/packages when they made API
incompat
On Wed, 15 Jul 2009 at 16:14, Paul Moore wrote:
Bluntly, as Python stands, import and sys.path do not offer any core
support for multiple versions. Custom solutions can be built on top of
that - that's what setuptools does. But they are precisely that -
custom solutions, and should be supported a
On Wed, Jul 15, 2009 at 11:00 PM, Tarek Ziadé wrote:
> On Wed, Jul 15, 2009 at 12:10 PM, Paul Moore wrote:
>>
>> Disclaimer: I've only read the short version, so if some of this is
>> covered in the longer explanation, I apologise now.
>
> Next time I won't put a short version ;)
>
>
>>
>> PEP 376
Hi all.
As you probably know:
http://www.mail-archive.com/debian-pyt...@lists.debian.org/msg05456.html
I would like to unofficially package Plone 3.3+ for Debian.
Unofficially, because I would like to package from the buildout/egg.
That way, it will never comply with the Debian policy.
Good idea
I've been trying to follow this discussion now for weeks. The signal to noise
ratio is pretty low.
I'd love to have an stdlib solution for distribution packaging and installation.
But I think we might as well pack it up and go home if the folks whom are
contributing to the discussion "recreat
At 06:40 PM 7/15/2009 +0100, Paul Moore wrote:
And of course, someone has to do the clean-up. It seems to me that the
fact that people are more inclined to reinvent the code than to try to
understand the existing codebase and pick out the relevant bits, says
something important about how easy it
At 07:07 PM 7/15/2009 +0200, Tarek Ziadé wrote:
Part of the rejection of setuptools is because of that and
because you don't
bless anyone to maintain the project code base, or do releases,
neither to communicate clearly
on what's its roadmap.
Jim Fulton and Ian Bicking have been official
On Wed, 15 Jul 2009 08:22:03 -0700, David Cournapeau
wrote:
if docutils 0.5 is installed, Foo is broken, unless docutils 0.4 is
shipped with it.
As was stated by Debian packagers on the distutils ML, the problem is
that docutils 0.5 breaks packages which work with docutils 0.4 in the
first p
Tarek Ziadé wrote:
In any case I don't see any use case to have a "site-packages"
remaining in Python itself.
I have and am using it. Where else would you have me put library
packages meant to be accessible by any Python program?
Terry Jan Reedy
___
Paul Moore wrote:
- how do I import version 0.7.1 of package foo, rather than 0.7.2?
Augment import to recognize versioned names?
import foo_0_7_1
- how do I use foo 0.8 at my interactive prompt, and import bar 0.2
which relies on foo 0.7.1?
bar does import foo_0_7_2
- what happens if
2009/7/15 P.J. Eby :
> At 11:10 AM 7/15/2009 +0100, Paul Moore wrote:
>>
>> I propose that before the current prototype is turned into a final
>> (spec and) implementation, the PEP 302 extensions are extracted and
>> documented as an independent protocol, purely part of PEP 376. (This
>> *helps* im
On Wed, 15 Jul 2009 02:01:24 -0700, Tarek Ziadé
wrote:
get_installed_files(local=False) -> iterator of (path, md5, size)
Will this also return the directories /created/ during the installation?
For example, will it also contain the entry "docutils" .. along with
"docutils/__init__.py"?
I
2009/7/15 P.J. Eby :
[...]
> So if politics demands that it be rejected by association with "setuptools",
> then just search-and-replace the API, PEP 8-ify it, call it something
> different, and lie to everyone about where it came from. I won't tell if
> you won't. ;-)
While setuptools did addre
At 04:59 PM 7/15/2009 +0100, Paul Moore wrote:
- Virtualenv isn't a workaround (I don't know virtualenv, I'll take
your word for it)
It's not one for system package maintainers because it would
effectively be managing multiple instances of 'python'. Really not a
suitable solution.
- I do
At 05:16 PM 7/15/2009 +0200, Joachim König wrote:
f you have m different versions of n packages then
you could have n**m different combinations for an application so you need a
possiblilty to select one combination from n**m possible ones at application
startup time. Is this really worth it?
Ob
At 04:14 PM 7/15/2009 +0100, Paul Moore wrote:
Look - I really, really don't mind if people use setuptools. Honest.
But I do mind if core python gets changed to support little bits of
what setuptools does, adding complexity to deal with issues that
setuptools handles, but without making it possib
At 11:10 AM 7/15/2009 +0100, Paul Moore wrote:
I propose that before the current prototype is turned into a final
(spec and) implementation, the PEP 302 extensions are extracted and
documented as an independent protocol, purely part of PEP 376. (This
*helps* implementers, as they can write suppor
On Wed, Jul 15, 2009 at 5:16 PM, Joachim König wrote:
> Tarek Ziadé wrote:
>>
>> So basically "site-packages" is a distribution location that is
>> avoided by everyone because it doesn't
>> know how to handle multiple versions.
>
> I think you overrate the importance of having multiple versions of
2009/7/15 David Cournapeau :
> As was stated by Debian packagers on the distutils ML, the problem is
> that docutils 0.5 breaks packages which work with docutils 0.4 in the
> first place.
>
> http://www.mail-archive.com/distutils-sig@python.org/msg05775.html
>
> And current hacks to work around lac
On Wed, Jul 15, 2009 at 5:14 PM, Paul Moore wrote:
> 2009/7/15 Tarek Ziadé :
>> On Wed, Jul 15, 2009 at 12:17 PM, Michael
>> Foord wrote:
Disclaimer: I've only read the short version, so if some of this is
covered in the longer explanation, I apologise now.
-1.
>>>
>>> I ag
At 07:43 AM 7/15/2009 -0700, Peter Bengtsson wrote:
Crap!
That didn't work either!
IOError: [Errno 20] Not a directory: '/home/peterbe/virtualenvs/
djangopeoplenet/lib/python2.5/site-packages/premailer-1.2-py2.5.egg/
premailer/version.txt'
This must be because of some egg magic that I don't unde
Tarek Ziadé wrote:
So basically "site-packages" is a distribution location that is
avoided by everyone because it doesn't
know how to handle multiple versions.
I think you overrate the importance of having multiple versions of a
package available
for the same python interpreter. If you have m d
2009/7/15 Tarek Ziadé :
> On Wed, Jul 15, 2009 at 12:17 PM, Michael
> Foord wrote:
>>> Disclaimer: I've only read the short version, so if some of this is
>>> covered in the longer explanation, I apologise now.
>>>
>>> -1.
>>>
>>
>> I agree. People with versioning issues *should* be using virtualen
Crap!
That didn't work either!
IOError: [Errno 20] Not a directory: '/home/peterbe/virtualenvs/
djangopeoplenet/lib/python2.5/site-packages/premailer-1.2-py2.5.egg/
premailer/version.txt'
This must be because of some egg magic that I don't understand.
What I did was this (in premailer.py):
__vers
On Jul 15, 2:16 pm, Jean-Paul Calderone wrote:
> On Wed, 15 Jul 2009 04:29:05 -0700 (PDT), Peter Bengtsson
> wrote:
> >I've just made a package
> >http://pypi.python.org/pypi/premailer
>
> >To figure out if I've got it right I've tried installing it like
> >this::
>
> > [snip - install failure
On Wed, Jul 15, 2009 at 12:17 PM, Michael
Foord wrote:
>> Disclaimer: I've only read the short version, so if some of this is
>> covered in the longer explanation, I apologise now.
>>
>> -1.
>>
>
> I agree. People with versioning issues *should* be using virtualenv.
>
Let's remove site-packages fr
On Wed, Jul 15, 2009 at 12:10 PM, Paul Moore wrote:
>
> Disclaimer: I've only read the short version, so if some of this is
> covered in the longer explanation, I apologise now.
Next time I won't put a short version ;)
>
> PEP 376 support has added a requirement for 3 additional methods to
> the
On Wed, 15 Jul 2009 04:29:05 -0700 (PDT), Peter Bengtsson
wrote:
I've just made a package
http://pypi.python.org/pypi/premailer
To figure out if I've got it right I've tried installing it like
this::
[snip - install failure log]
The setup.py
(see http://github.com/peterbe/premailer/tree/mast
I've just made a package
http://pypi.python.org/pypi/premailer
To figure out if I've got it right I've tried installing it like
this::
$ cd /tmp
$ mkvirtualenv --no-site-packages test_premailer
$ easy_install premailer
Searching for premailer
Reading http://pypi.python.org/simple/premailer/
Page
Paul Moore wrote:
2009/7/15 Tarek Ziadé :
On Tue, Jul 14, 2009 at 2:12 AM, Sridhar
Ratnakumar wrote:
Here are my comments regarding PEP 376 with respect to PyPM (the Python
package manager being developd at ActiveState)
Multiple versions: I understand that the PEP does not support
ins
2009/7/15 Tarek Ziadé :
> On Tue, Jul 14, 2009 at 2:12 AM, Sridhar
> Ratnakumar wrote:
>> Here are my comments regarding PEP 376 with respect to PyPM (the Python
>> package manager being developd at ActiveState)
>>
>>
>> Multiple versions: I understand that the PEP does not support
>> installation
New submission from raybaut :
Tested on Windows XP with setuptools 0.6c9:
1. Open a Python intepreter in "C:\Python25\Lib\site-packages":
a) run cmd.exe
b) change directory to "C:\Python25\Lib\site-packages"
c) run python.exe
2. type "from pkg_resources import resource_stream"
3. type
On Tue, Jul 14, 2009 at 2:12 AM, Sridhar
Ratnakumar wrote:
> Here are my comments regarding PEP 376 with respect to PyPM (the Python
> package manager being developd at ActiveState)
>
>
> Multiple versions: I understand that the PEP does not support
> installation (thus uninstallation) of multiple
Ross Patterson wrote:
I often end up doing development on the same distribution for multiple
projects and have long wished for a simple way to share the same
clone/checkout between these multiple buildouts.
What's stopping you from just putting the same checkout path in the
develop line of you
41 matches
Mail list logo
