Martin v. Löwis wrote:
The poll is now closed, with these results
Allow ratings and comments on all packages (status quo) 237
Allow package owners to disallow comments (ratings unmodified). 139
Allow comments, but only send them to package owners (ratings
unmodified). 33
Hello
As suggested here, then discussed at Distutils-SIG, I would like to
propose the addition of two more fields for the
upcoming Metadata 1.2 (PEP 345) that could be used at PyPI on projects pages.
Repository-Browse-URL
A string containing the URL for the package's browsable
repository.
On Sat, Oct 10, 2009 at 2:07 AM, Martin v. Löwis mar...@v.loewis.de wrote:
Any idea how to test rst so it renders properly. This rst displays
just fine in moinmoin, so is there anything special about Pypi as far
as rendering?
You can try rendering it locally, with the function
Any help on this would be welcomed.
I took your setup.py, renamed the package, and uploaded it to
http://pypi.python.org/pypi/datahub_mvl
What exactly is incorrect about this page?
Regards,
Martin
___
Catalog-SIG mailing list
Catalog-SIG@python.org
What exactly is incorrect about this page?
nothing in yours...
http://pypi.python.org/pypi/datahub_mvl
but mine?
http://pypi.python.org/pypi/datahub/0.8.90dev
Well, I used your setup.py literally, and just did python setup.py
register. How did you get the release registered?
Regards,
This looks a lot like a bug I opened against distutils:
http://bugs.python.org/issue1923
here's the related post: http://markmail.org/message/us3aqqixgqmzv3tv
It would be *fantastic* to finally tackle this problem.
Stephen Emslie
On Wed, Dec 2, 2009 at 3:43 PM, Martin v. Löwis
ps. I'm not sure why python setup.py register works but Or upload
your PKG-INFO file (generated by distutils) here:
PKG-INFO file: does not.
setup.py register doesn't use the PKG-INFO file at all.
ISTM that PKG-INFO files don't support ReST, period.
Regards,
Martin
That might be the difference then...
I only did python setup.py register the first time and then I was just
using the python setup.py sdist upload.
python setup.py register
python setup.py sdist upload
Hmm. When I do sdist upload, it also works fine for me.
Regards,
Martin
On Wed, Dec 2, 2009 at 10:32 AM, Martin v. Löwis mar...@v.loewis.de wrote:
That might be the difference then...
I only did python setup.py register the first time and then I was just
using the python setup.py sdist upload.
python setup.py register
python setup.py sdist upload
Hmm. When I
Martin v. Löwis wrote:
But I think that getting rid of the ratings is is also important.
I don't think this is consensus.
That's because the poll didn't really allow people to clearly express
their views, which was the point of what Laura was saying.
I, too, would like to see ratings be
Tarek Ziadé wrote:
Hello
As suggested here, then discussed at Distutils-SIG, I would like to
propose the addition of two more fields for the
upcoming Metadata 1.2 (PEP 345) that could be used at PyPI on projects pages.
Repository-Browse-URL
A string containing the URL for the package's
Tarek Ziadé wrote:
Hello
As suggested here, then discussed at Distutils-SIG, I would like to
propose the addition of two more fields for the
upcoming Metadata 1.2 (PEP 345) that could be used at PyPI on projects pages.
Repository-Browse-URL
A string containing the URL for the
On Wed, Dec 2, 2009 at 11:28 AM, Chris Withers ch...@simplistix.co.uk wrote:
The only controversial ones were Change-Log-URL and, at a push,
Documentation-URL (although it was only you who even queried that ;-), so
why have Repository-URL and Mailing-List-URL been abandoned?
I didn't notice
On 2009-12-02 11:43 AM, M.-A. Lemburg wrote:
While more structured meta-data is generally better than less,
I wonder why we have to add URLs for all these things.
The home page of a project will usually provide the URLs
in some form already and if there is no home page, the
long description
I'd like to see how the PyPI UI works out. I can also imagine a more
extensible setup, like:
Project-URLs: documentation=http://myproject.org/docs/
repository=http://myproject.org/svn/
mailing list=http://googlegroups.com/groups/myproject
I think this also points to an important
On Wed, Dec 2, 2009 at 9:21 PM, Martin v. Löwis mar...@v.loewis.de wrote:
I'd like to see how the PyPI UI works out. I can also imagine a more
extensible setup, like:
Project-URLs: documentation=http://myproject.org/docs/
repository=http://myproject.org/svn/
mailing
But the project always wants to display the newest urls.
Not at all. For some projects, it's more important to be conscious about
documentation versions than for others. For example
http://www.postgresql.org/docs/
asks you to make an explicit choice of version, and the URLs reflect
that.
Tarek Ziadé wrote:
2009/12/2 Martin v. Löwis mar...@v.loewis.de:
[..]
For Python, it somewhat unfortunate that there is a tradition of
newest documentation. When the documentation format changed, many
URLs broke - something that would not have happened when all URLs
had been versioned.
Robert Kern wrote:
On 2009-12-02 11:43 AM, M.-A. Lemburg wrote:
While more structured meta-data is generally better than less,
I wonder why we have to add URLs for all these things.
The home page of a project will usually provide the URLs
in some form already and if there is no home page, the
2009/12/3 Martin v. Löwis mar...@v.loewis.de:
On the long_description front, the default behavior is to display the
latest one
That's not true. If there are multiple visible releases, no release
is singled out.
What ? the statement the default behavior is to display the latest
one *is* true
20 matches
Mail list logo
