On 5/31/2011 7:43 AM, Maurits van Rees wrote:
> Op 31-05-11 12:43, Tarek Ziadé schreef:
>> I think this regression could be related to this change:
>>
>>https://bitbucket.org/tarek/distribute/changeset/a3f0d30e94c2
>>
>> Would you mind trying to revert this change in your environment to see
>>
On 5/31/2011 5:50 AM, Maurits van Rees wrote:
> When I go in with a pdb in this utils.py everything seems fine but then
> the import error just happens a bit further on, failing to import
> plone.app.layout. On Plone 4 an import of Shared.DC.ZRDB.Search fails.
> Again, with distribute 0.6.16 it
On 4/6/2011 3:21 AM, Chris Withers wrote:
> On 05/04/2011 16:33, Eric Smith wrote:
>> Could you elaborate on this? How does buildout/setuptools/distribut
>> search for an sdist, lacking an index file? Does it look for .tgz only,
>> or other extensions as well? This would save
> On Mon, Apr 18, 2011 at 3:14 PM, Jim Fulton wrote:
>
>> On Mon, Apr 18, 2011 at 8:28 AM, Arve Knudsen
>> wrote:
>> > Hello
>> > I'm new to Buildout and need to figure out how to accomplish a
>> (seemingly)
>> > simple usecase: Install my project from source into an isolated
>> environment.
>> >
On 03/25/2011 03:24 PM, Chris Withers wrote:
> Hi Christian,
>
> On 25/03/2011 16:49, Christian Theune wrote:
>> the German speaking Zope Users Group (DZUG e.V.) organizes a series of 4
>> sprints this year to support feature development within the proximity of
>> the ZTK and solve problems encoun
On 3/7/2011 4:26 PM, "Martin v. Löwis" wrote:
- Generate the text "No documentation" in the place where the link would
be if there is no documentation.
-1. Saying "No documentation" would be wrong if the package, in fact,
does have documentation, but elsewhere.
"No documentation uploaded to P
I use buildout, which uses setuptools/distribute. So for that, the answer is
yes.
"Matt Chaput" wrote:
>On 03/02/2011 10:34 AM, Eric Smith wrote:
>> I use source distributions (python setup.py sdist) and then
>distribute
>> the resulting .tar.gz file. Sin
On 02/03/2011 10:17 AM, Matt Chaput wrote:
When I create an egg the Python version used to create the egg is encoded in
the egg filename, e.g. Whoosh-1.6.0-py2.7.egg.
Is this version number used to decide what egg a user gets from PyPI? I didn't
think it was, but a user is seeming to indicate
On 9/15/2010 9:53 AM, Chris Withers wrote:
Of course, the horse is already bolted on this. The only "sane" option
now would be for all distribution names to be lowercased by all tools
all of the time. How do others feel about this?
I have been bitten by this recently, with pinning versions via
On 9/8/10 7:34 AM, Doug Hellmann wrote:
I'm having some problems creating an sdist for a nested package where some of
the levels only include __init__.py and the subdirectories. The full list of
files is fairly long, but here's a snippet to give you an idea of the layout
for the inputs:
Tarek Ziadé wrote:
On Thu, Jan 7, 2010 at 12:48 PM, Eric Smith wrote:
[..]
Normally the word 'distribution' is reserved for what lands in the
'dist' directory, such as a tarball or an egg...right?
Right.
We should use the terminology as defined in
http://docs.
Brad Allen wrote:
This quote is taken from the distutils thread "current preferred way
to specify dependencies? future?",
On Wed, Jan 6, 2010 at 10:55 AM, Tarek Ziadé wrote:
On Wed, Jan 6, 2010 at 3:35 PM, John Gabriele wrote:
I'm a bit confused myself... PEP-345 says it "describes a mechani
Lennart Regebro wrote:
On Sat, Dec 26, 2009 at 05:03, David Cournapeau wrote:
The reasons I see for making some things, in
particular upload mandatory are as follows:
- file upload makes pure rsync-based mirroring. In the case of CRAN,
you mirror with one rsync command. No need for fancy schem
Benji York wrote:
On Tue, Dec 1, 2009 at 10:50 AM, Tarek Ziadé wrote:
[snip a reiteration of the perceived benefits]
So I guess you are also against the addition of "Repository-URL" and
"Bug-Tracker-URL" too ?
Since those can be links in the long_description as well.
I am.
Don't get me wron
Chris Withers wrote:
Tarek Ziadé wrote:
On Sat, Nov 28, 2009 at 11:33 PM, Chris Withers
wrote:
[..]
Yes to all of the above, could we also please have:
Mailing-List-URL
+1
Change-Log-URL
I don't see a lot of projects with a changelog file available online,
...except every single Zope
Ben Finney wrote:
Eric Smith writes:
Ben Finney wrote:
Since the specification is about version *comparison* semantics, I'd
need to know example version strings that should compare “prior” and
“subsequent” for the version string I'm to propose. Can you give
examples?
I want to i
Ben Finney wrote:
Eric Smith writes:
Ben Finney wrote:
the problem we have is to be able to sort those post and pre
releases with other versions. And this is not possible with a
simple alphanumerical comparison.
It is, if the version strings are chosen to fit within such a
comparison
Ben Finney wrote:
Yes, and others that have been proposed to be exceptions to alphanumeric
ordering.
the problem we have is to be able to sort those post and pre releases
with other versions. And this is not possible with a simple
alphanumerical comparison.
It is, if the version strings are c
Chris Withers wrote:
Fred Drake wrote:
I'd rather see the static data in setup.cfg and no setup.py if there's
no need for custom Python code.
Agreed.
I think "python setup.py install" is so idiomatic that it seems silly to
break it for the sake of two lines of python. There's also an eleme
Tarek Ziadé wrote:
What's unclear right now is what will be pushed in Distutils by the
time Python 2.7 and 3.3 are out.
Why 3.3 and not 3.2?
Eric.
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/dist
Tarek Ziadé wrote:
On Wed, Oct 21, 2009 at 10:42 AM, M.-A. Lemburg wrote:
Tarek Ziadé wrote:
On Tue, Oct 20, 2009 at 5:20 PM, M.-A. Lemburg wrote:
The micro-language should provide a limited number of
variables to use on the conditions:
python_version = sys.version
sys_platform = sys.platfo
Tarek Ziadé wrote:
but, notice that "python_version" here is: "%s.%s" %
sys.version_info[0], sys.version_info[1]
I think you mean:
"{0[0]}.{0[1]}".format(sys.version_info)
or better:
"{0.major}.{0.minor}".format(sys.version_info)
:)
On the odd occasion that .format is less verbose than %, I
David Lyon wrote:
On Tue, 13 Oct 2009 11:33:26 +0200, Tarek Ziadé
wrote:
The first one who mentioned the idea was Eric IIRC, then Matthias and
Tres worked on it.
Fine. They've been awfully quiet on distutils-sig lately :-)
Not so!
I just happen to be the one maintaining PEP 390 and I am t
Ronald Oussoren wrote:
On 11 Oct, 2009, at 20:58, Lennart Regebro wrote:
2009/10/11 Ronald Oussoren :
That is, I install "SuperWebFramework==1.0" which happens to depend on
peak-rules. I later start using peak-rules in my own simple scripts
(without
a setup.py or other explicit dependency inf
Gerry Reno wrote:
Tarek Ziadé wrote:
2009/9/23 Andrew Straw :
Well, it wouldn't be setting a precedent that importing a module would
extend the functionality of the stdlib's distutils commands -- the
setuptools and distribute projects already do this. For example, the
"sdist" command in setu
Floris Bruynooghe wrote:
On Wed, Sep 23, 2009 at 03:15:24PM +0200, Tarek Ziadé wrote:
On Wed, Sep 23, 2009 at 2:56 PM, Floris Bruynooghe
wrote:
[original mail from python-dev
http://mail.python.org/pipermail/python-dev/2009-September/091947.html]
On Tue, Sep 22, 2009 at 03:21:06PM +0200, Tare
Chris Withers wrote:
Tarek Ziadé wrote:
[setup.cfg]
long_description_path: README.txt
long_description_path can't be added in the final PKG-INFO because
we want a self-contained metadata static file that doesn't require an
extra resource (like an external file)
Why this requirement?
Where
Tarek Ziadé wrote:
On Tue, Sep 8, 2009 at 10:29 AM, Chris Withers wrote:
Tarek Ziadé wrote:
- an extra function called "long_description", to be able to point a
file for the long description field
I can't comment on the others, but this is unnecessary. Why do you need more
than:
long_decripti
David Lyon wrote:
That's why we need to keep it simple. Handle 85% of use cases with
config and the other 15% with the ability to use (python) code.
The part that needs to by "code-like" is only the stuff that's needed
when the config file is used by an installer, and is known only to the
tar
P.J. Eby wrote:
At 06:04 PM 7/9/2009 +0900, David Cournapeau wrote:
I too would like to see this kind of system, and have been thinking
quite a bit about it. Looks like I am not the only one.
For reference, here are some previous posts on this topic, suggesting
some requirements and approache
Zooko Wilcox-O'Hearn wrote:
Having an archive format that preserves such bits would probably be a
good way to solve all such problems -- by making it the packagers
problems to set the bits before packaging rather than setuptools's
problem to figure out which bits ought to be set after installat
It isn't so easy for setuptools to know which things ought to have +x
and which things ought not just based on their pathnames or other
metadata.
Unless you specify explicitly it in a metadata file.
Having an archive format that preserves such bits would probably be a
good way to solve all su
P.J. Eby wrote:
I can *almost* see a case for dropping "post" - I personally have not
used it, and Trent has shown evidence that its usage is relatively
rare. And I could *almost* see tacking on extra zeros to signify a post
tag, at the cost of readability, and the need for any tracked package
Ben Finney wrote:
If they are separate components (where each component from left to right
is entirely subordinate to the preceding component), then that
separation is implied. Version ‘1.2.3’ can have as many ‘.dev’ as
desired, all of which will compare previous to version ‘1.2.4’.
This de
Paul Moore wrote:
2009/6/11 P.J. Eby :
PyPI uploads aren't a suitable basis for analyzing "dev" use cases, since
the whole point of having a "dev" tag is for *non-released* versions.
(E.g., in-progress development via SVN.)
If it's non-released, I've yet to see a clear explanation of why the
Zooko Wilcox-O'Hearn wrote:
Trent Mick:
Thank you very much for the summary emails.
Indeed!
This gives us:
N.N.NaN# e.g. "1.0.0a2"
N.N.NbN# e.g. "2.6.0b1"
This is where we branch between the two ways that people do it. Some
people count up to a future release, other peop
I'll share my thoughts on the other points when I have some time, but
I'd like to address this one now:
Paul Moore wrote:
PS I have a paranoid feeling that there's a subtext somewhere here to
the effect that participants in the discussion don't see why there's
such a big deal, as everyone shoul
> 2009/6/8 Tarek Ziadé :
< plans and reasons to drop some commands from distutils, which I agree
with >
>> - we need to detect for each existing command (rpm, etc) a project
>> that can take over, prior to remove it from Distutils
>> when appliable .
>
> And a policy on what to do if no such proj
Paul Moore wrote:
2009/5/7 Tres Seaver :
Eric Smith wrote:
Yes. It creates a .exe wrapper [1]. By using entry points, I don't need
to care what the target system is. Also, /usr/bin/env might invoke the
wrong python.
Exactly: using entry points for console scripts guarantees that the
p
Doug Hellmann wrote:
On May 7, 2009, at 8:54 AM, Paul Moore wrote:
2009/5/7 Doug Hellmann :
I would argue the other way. Why force authors of console scripts to
deal
with entry points instead of just installing the script as-is?
Please explain "as-is" with reference to ensuring that the s
[Trent]
Or we could have:
RationalVersion(...version bits...)
RationalVersion.from_string(s) # this is a @classmethod
[Tres]
I would prefer keeping the string version of __init__, with the "I'm in
control, dammit" version reserved for the non-default factory method.
I'd tend to a
Ronald Oussoren wrote:
On 20 Apr, 2009, at 22:12, Lennart Regebro wrote:
I'm sorry you feel that way, as I've been *trying* to help. I just
still
don't get what the problem is. If I were porting setuptools to
Python 3, I
would *want* it to be circular, even if I had to hack on it a little
Tarek Ziadé wrote:
Please Greg, add your use case here with David's one, at the end of the page,
since we are trying to work on a solution.
http://wiki.python.org/moin/Distutils/ManifestPluginSystem/Draft
Could the people adding the use cases put their names by them, so if we
have questions
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
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
Martin v. Löwis wrote:
I just collected the version strings of versions that
got released to PyPI, and put up the list on
http://www.dcl.hpi.uni-potsdam.de/home/loewis/versions
That's excellent, thank you.
The following chunk of text is present. I don't really care, except that
it might mean
Lennart Regebro wrote:
On Thu, Jan 29, 2009 at 15:35, Barry Warsaw 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 wa
Akira Kitada wrote:
In my opinion, bdist_rpm and the like are "nice hacks" at best
and nothing more.
Peoplo who love rigorous distribution or control freaks would probably
prefer to
bother packaging themselves and that will leads them to use apt, yum...
I am both a control freak and love rigoro
Tarek Ziadé wrote:
On Sat, Oct 4, 2008 at 1:38 AM, Eric Smith <[EMAIL PROTECTED]> wrote:
I understand that --index-url is single valued, and --find-links is
multi-valued. But what's the semantic difference between them? From my
reading, it sounds like they both point to pages that co
I understand that --index-url is single valued, and --find-links is
multi-valued. But what's the semantic difference between them? From my
reading, it sounds like they both point to pages that contain links to
eggs (or other distributions).
What I'm really trying to do is set up my own server,
50 matches
Mail list logo
