if anybody would *not* want to have a "Documentation" link automatically
generated that points to packages.python.org/, please speak up.
That would only make sense if there's something uploaded to
the PyPI docs dir.
If PyPI can detect that, +1.
Yes, the link would certainly be conditional.
R
On Mon, Mar 7, 2011 at 9:18 AM, M.-A. Lemburg wrote:
> "Martin v. Löwis" wrote:
>> if anybody would *not* want to have a "Documentation" link automatically
>> generated that points to packages.python.org/, please speak up.
>
> That would only make sense if there's something uploaded to
> the PyPI
"Martin v. Löwis" wrote:
>>> As for a big link: if you think your page should have one, you are free
>>> to make it yourself already.
>>
>> Sure but,
>>
>> 1/ I have never asked for the "Downloads ↓" link either, but the UI
>> did add it, and it's really more ergonomic.
>>
>> 2/ I have never asked
2011/3/6 "Martin v. Löwis"
> What particular clause strikes you as particularly unfriendly?
>>> Please understand that it may sound harsh, but is necessary - better
>>> be safe than sorry.
>>>
>>
>> Nothing wrong about the warning itself, but about landing on a plain
>> condensed text page.
>> I
As for a big link: if you think your page should have one, you are free
to make it yourself already.
Sure but,
1/ I have never asked for the "Downloads ↓" link either, but the UI
did add it, and it's really more ergonomic.
2/ I have never asked for "Latest Version: 0.6.14" on this page : hit
t
2011/3/6 Tarek Ziadé :
...
> and you also say for 2/ "if you think your page should have links to
s/ you also / you could have also /
(not clear otherwise)
___
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/
2011/3/6 "Martin v. Löwis" :
>>> What particular clause strikes you as particularly unfriendly?
>>> Please understand that it may sound harsh, but is necessary - better
>>> be safe than sorry.
>>
>> Nothing wrong about the warning itself, but about landing on a plain
>> condensed text page.
>> I th
On Sun, Mar 6, 2011 at 22:05, "Martin v. Löwis" wrote:
>> I guess either http://pypi.python.org/pypi/distribute/docs or
>> http://pypi.python.org/docs/distribute would be acceptable.
>
> The former won't work - it tries to get a version labeled "docs"
> from "distribute". As for the latter, see
>
What particular clause strikes you as particularly unfriendly?
Please understand that it may sound harsh, but is necessary - better
be safe than sorry.
Nothing wrong about the warning itself, but about landing on a plain
condensed text page.
I think we should make it a html page. And maybe displ
Since mercurial makes me annoyed I decided to use it. I'll have to
learn it someday anyway, so why not now?
https://bitbucket.org/regebro/pyroma
Helpers welcome (although you'll probably have to wait to after PyCon).
//Lennart
On Sun, Mar 6, 2011 at 20:40, Lennart Regebro wrote:
> The winner i
Lennart Regebro wrote:
But, before I move this to a public repository and upload it to PyPI,
there is one important thing to be determined: What should it be
called?
Inspector Tiger?
http://www.youtube.com/watch?v=UDdCghQYvDY
--
Greg
___
Distutils-
2011/3/6 Tarek Ziadé
> On Sun, Mar 6, 2011 at 9:42 PM, "Martin v. Löwis"
> wrote:
> >> One thing I find weird is the root page of packages.python.org -- This
> >> warning is not super user friendly.
> >
> > What particular clause strikes you as particularly unfriendly?
> > Please understand that
I guess either http://pypi.python.org/pypi/distribute/docs or
http://pypi.python.org/docs/distribute would be acceptable.
The former won't work - it tries to get a version labeled "docs"
from "distribute". As for the latter, see
http://mail.python.org/pipermail/catalog-sig/2008-August/001723.ht
On Sun, Mar 6, 2011 at 9:42 PM, "Martin v. Löwis" wrote:
>> One thing I find weird is the root page of packages.python.org -- This
>> warning is not super user friendly.
>
> What particular clause strikes you as particularly unfriendly?
> Please understand that it may sound harsh, but is necessary
On Sun, Mar 6, 2011 at 10:53 PM, "Martin v. Löwis" wrote:
> I think it's less about the content and more about the form. I think
>> this warning belongs in a little `legal` section at the bottom, not as
>> the first thing that a visitor sees.
>>
>
> Are we talking about the same document? On
>
> h
On Sun, Mar 6, 2011 at 21:42, "Martin v. Löwis" wrote:
>> One thing I find weird is the root page of packages.python.org -- This
>> warning is not super user friendly.
>
> What particular clause strikes you as particularly unfriendly?
It's rather the lack of design and just a link that seems a bi
I think it's less about the content and more about the form. I think
this warning belongs in a little `legal` section at the bottom, not as
the first thing that a visitor sees.
Are we talking about the same document? On
http://packages.python.org/
the warning *is* in the bottom of the page (no
On Sun, Mar 6, 2011 at 10:42 PM, "Martin v. Löwis" wrote:
> One thing I find weird is the root page of packages.python.org -- This
>> warning is not super user friendly.
>>
>
> What particular clause strikes you as particularly unfriendly?
> Please understand that it may sound harsh, but is necess
One thing I find weird is the root page of packages.python.org -- This
warning is not super user friendly.
What particular clause strikes you as particularly unfriendly?
Please understand that it may sound harsh, but is necessary - better
be safe than sorry.
That said, maybe projects documenta
On Sun, Mar 6, 2011 at 9:10 PM, Lennart Regebro wrote:
> On Sun, Mar 6, 2011 at 20:49, cool-RR wrote:
>> Speaking of names, I would rename PyPI to packages.python.org, maybe move
>> the existing documentation center to docs.python.org, and then move the docs
>> of Python itself to a `/python` fol
On Sun, Mar 6, 2011 at 10:10 PM, Lennart Regebro wrote:
> On Sun, Mar 6, 2011 at 20:49, cool-RR wrote:
> > Speaking of names, I would rename PyPI to packages.python.org, maybe
> move
> > the existing documentation center to docs.python.org, and then move the
> docs
> > of Python itself to a `/py
On Sun, Mar 6, 2011 at 20:49, cool-RR wrote:
> Speaking of names, I would rename PyPI to packages.python.org, maybe move
> the existing documentation center to docs.python.org, and then move the docs
> of Python itself to a `/python` folder...
> But that's just me.
No, I do think docs.python.org
On Sun, Mar 6, 2011 at 2:46 PM, Benji York wrote:
> On Sun, Mar 6, 2011 at 10:34 AM, Jim Fulton wrote:
>> An annoyance in buildout configurations, resulting from it's use of
>> ConfigParser, is that configuration data lines are stripped of leading
>> spaces.
>
> +1
>
> How should we handle the de
Speaking of names, I would rename PyPI to packages.python.org, maybe move
the existing documentation center to docs.python.org, and then move the docs
of Python itself to a `/python` folder...
But that's just me.
On Sun, Mar 6, 2011 at 9:40 PM, Lennart Regebro wrote:
> The winner is Wichert, wi
On Sun, Mar 6, 2011 at 10:34 AM, Jim Fulton wrote:
> An annoyance in buildout configurations, resulting from it's use of
> ConfigParser, is that configuration data lines are stripped of leading
> spaces.
+1
How should we handle the dedenting?
Would both of these assignments produce the same res
The winner is Wichert, with "pyroma".
I do like the "stickler" name, and the cheeseshop namespace, but since
there is nothing else in that namespace I'll wait with it. It can
easily be moved to a "cheeseshop.compliance" or whatever in the
future, but that the moment it's "pyroma". I'll check it in
Excellent idea Lennart...
On Mar 06, 2011, at 03:51 PM, Brad Allen wrote:
>cheeseshop.critic
>pypi.stickler
I like the cheeseshop namespace used for this. Or maybe wenslydale :)
http://orangecow.org/pythonet/sketches/cheese.htm
-Barry
signature.asc
Description: PGP signature
___
On Sun, Mar 6, 2011 at 17:00, Tarek Ziadé wrote:
> Reminds me a bit about "CheeseCake" http://pycheesecake.org/
Indeed, it's a lot like CheeseCake, which I had forgot about and
didn't find either by google, pypi or asking on #plone and #python.
:-)
However, there are a significant difference. C
On Sun, Mar 6, 2011 at 9:46 AM, Lennart Regebro wrote:
> I've started working on a little utility to give a quality rating on
> packages, expressed in 0-10 points, and also in cheese types,
> according to smellyness.
>
> It's going to check for things like that it has all meta data it
> should hav
On Sun, Mar 06, 2011 at 10:34:01AM -0500, Jim Fulton wrote:
> An annoyance in buildout configurations, resulting from it's use of
> ConfigParser, is that configuration data lines are stripped of leading
> spaces.
...
> I propose to give buildout it's own parser that begaves like
> ConfigParser, wit
On Sun, Mar 6, 2011 at 2:38 PM, Benji York wrote:
> On Mar 6, 2011 3:47 AM, "Lennart Regebro" wrote:
>>
>> I've started working on a little utility to give a quality rating on
>> packages, expressed in 0-10 points, and also in cheese types,
>> according to smellyness.
>
> How about "cheese inspec
An annoyance in buildout configurations, resulting from it's use of
ConfigParser, is that configuration data lines are stripped of leading
spaces. This means configurations like this:
[paste.ini]
recipe = zc.recipe.deployment:configuration
text =
[app:main]
use = egg:bobo
bobo_resources = cm
On Mar 6, 2011 3:47 AM, "Lennart Regebro" wrote:
>
> I've started working on a little utility to give a quality rating on
> packages, expressed in 0-10 points, and also in cheese types,
> according to smellyness.
How about "cheese inspecter"?
--
Benji York
___
I've started working on a little utility to give a quality rating on
packages, expressed in 0-10 points, and also in cheese types,
according to smellyness.
It's going to check for things like that it has all meta data it
should have, such as author_email, specifies Python versions via the
trove cl
34 matches
Mail list logo
