On 17 jun 2010, at 22:44, Martin v. Löwis wrote:
In web app land, supported browsers usually means the ones the
designer targets: e.g., including IE= 7 in the list means that
the
designer doesn't have to include workarounds for stupid glitches in
earlier IEs (or even test the design against
Simon de Vlieger wrote:
On 17 jun 2010, at 22:44, Martin v. Löwis wrote:
In web app land, supported browsers usually means the ones the
designer targets: e.g., including IE= 7 in the list means that the
designer doesn't have to include workarounds for stupid glitches in
earlier IEs (or
On Thu, Jun 17, 2010 at 16:59, Tres Seaver tsea...@palladion.com wrote:
All of which make it impossible to reliably and repeatably deploy
arbitrary software configurations (directly) from PyPI. Managing your
own project-specific index is the only real solution.
When I provide buildout
On Fri, Jun 18, 2010 at 4:10 AM, M.-A. Lemburg m...@egenix.com wrote:
If you think the package owner is opening up a security threat by
including the links in the first place - yes, that's indeed a risk.
Is this feature still needed for setuptools ?
It's fairly regularly used to link to
With all the reliability discussion, I thought I'd offer a kind of
counterproposal, that we rewrite PyPI to use App Engine.
Of course, this means writing code, etc., but I believe this is a reasonable
goal. I think if we (Catalog-SIG? PyPI maintainers?) committed to using
such an implementation
On Thu, Jun 17, 2010 at 5:36 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Now, please tell me what you would do if sourceforge changes its url and
returns a
404 on the old download page. Would you update all release informations?
Well, at this point if sourceforge 404'ed on an old download
On Fri, Jun 18, 2010 at 11:47 AM, Mark Ramm m...@geek.net wrote:
On Thu, Jun 17, 2010 at 5:41 PM, Martin v. Löwis mar...@v.loewis.de
wrote:
It does? I thought PyPI kept everything around (but hidden) unless the
author went in and manually deleted old stuff. You just need to go to a
deep
On Fri, Jun 18, 2010 at 12:44 PM, Ian Bicking i...@colorstudy.com wrote:
With all the reliability discussion, I thought I'd offer a kind of
counterproposal, that we rewrite PyPI to use App Engine.
Of course, this means writing code, etc., but I believe this is a reasonable
goal. I think if
On Thu, Jun 17, 2010 at 6:30 AM, Ian Bicking i...@colorstudy.com wrote:
On Wed, Jun 16, 2010 at 1:37 PM, Martin v. Löwis mar...@v.loewis.de
wrote:
It is likely that some people will setup a mirror and then forget to
take care
about it. Like our buildbots really.
The same can happen to any
On 09:39 pm, ziade.ta...@gmail.com wrote:
On Thu, Jun 17, 2010 at 6:30 AM, Ian Bicking i...@colorstudy.com
wrote:
On Wed, Jun 16, 2010 at 1:37 PM, Martin v. Löwis
mar...@v.loewis.de
wrote:
It is likely that some people will setup a mirror and then forget
to
take care
about it. Like our
a question from me. Does setuptools browse the main pypi pages or does
it use the simple version?
Both. Old versions (which still need to be supported) go to the main
pages; new versions to the simple index. IOW, you need to maintain all
links on the main pages that also exist on the simple
I would very much like to see pypi start using chishop. I've been
working to implement the complete set of features that pypi supports
(including the mirroring PEP) for use inside of the company I work
for. The code is in reasonably good shape and I would love to see that
become the official
On Fri, Jun 18, 2010 at 6:47 PM, Martin v. Löwis mar...@v.loewis.de wrote:
I would very much like to see pypi start using chishop. I've been
working to implement the complete set of features that pypi supports
(including the mirroring PEP) for use inside of the company I work
for. The code is
On Fri, Jun 18, 2010 at 11:47 PM, exar...@twistedmatrix.com wrote:
[..]
There are (multiple!) open source implementations of the Amazon API. If
Amazon decides to discontinue their cloud services (something I doubt should
really be one of the top ten concerns here), then anyone else can set
On Fri, Jun 18, 2010 at 6:44 PM, Ian Bicking i...@colorstudy.com wrote:
With all the reliability discussion, I thought I'd offer a kind of
counterproposal, that we rewrite PyPI to use App Engine.
Of course, this means writing code, etc., but I believe this is a reasonable
goal. I think if we
I'm maintaining a todo list within my fork at
http://github.com/mcrute/chishop/blob/master/TODO and would very much
appreciate any input you might have as to which features are most
important for official compatibility and what is missing from that
list.
The absolute requirement is that any
At 01:07 AM 6/19/2010 +0200, Martin v. Löwis wrote:
Am 18.06.2010 18:47, schrieb Mark Ramm:
On Thu, Jun 17, 2010 at 5:41 PM, Martin v.
Löwismar...@v.loewis.de wrote:
It does? I thought PyPI kept everything around (but hidden) unless the
author went in and manually deleted old stuff. You
On Fri, Jun 18, 2010 at 6:27 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Fri, Jun 18, 2010 at 6:44 PM, Ian Bicking i...@colorstudy.com wrote:
With all the reliability discussion, I thought I'd offer a kind of
counterproposal, that we rewrite PyPI to use App Engine.
Of course, this
Am 19.06.2010 01:57, schrieb P.J. Eby:
At 01:07 AM 6/19/2010 +0200, Martin v. Löwis wrote:
Am 18.06.2010 18:47, schrieb Mark Ramm:
On Thu, Jun 17, 2010 at 5:41 PM, Martin v.
Löwismar...@v.loewis.de wrote:
It does? I thought PyPI kept everything around (but hidden) unless the
author went in
On Jun 18, 2010, at 7:27 PM, Tarek Ziadé ziade.ta...@gmail.com wrote:
On Fri, Jun 18, 2010 at 6:44 PM, Ian Bicking i...@colorstudy.com wrote:
Of course, this means writing code, etc., but I believe this is a reasonable
goal. I think if we (Catalog-SIG? PyPI maintainers?) committed to using
On Jun 18, 2010, at 7:51 PM, Martin v. Löwis mar...@v.loewis.de wrote:
I'm maintaining a todo list within my fork at
http://github.com/mcrute/chishop/blob/master/TODO and would very much
appreciate any input you might have as to which features are most
important for official compatibility
21 matches
Mail list logo
