On Thu, 23 Apr 2009 14:02:19 -0700, norseman wrote:
> If you think I'm somehow able to take a look at a plain piece of code
> you posted yesterday and know that it was written 26 years ago on a CP/M
> 2.0 dual HD DS 8" floppy drive system using Microsoft Assembly for the
> Z80 chip, intended as
David Stanek wrote:
On Thu, Apr 23, 2009 at 1:12 PM, norseman wrote:
BB's, User Lists, all repositories can make these required before
acceptance.
This is open source. I volunteer my time on the projects that I
maintain. If you don't like the quality or lack of documentations,
tests, etc. C
On Thu, Apr 23, 2009 at 1:12 PM, norseman wrote:
>
> BB's, User Lists, all repositories can make these required before
> acceptance.
>
>
This is open source. I volunteer my time on the projects that I
maintain. If you don't like the quality or lack of documentations,
tests, etc. Contribute. Or ju
David Lyon wrote:
On Thu, 23 Apr 2009 07:04:35 -0400, David Stanek
wrote:
If I use win32com how do you expect me to support Linux?
Of course not...
What about the many packages on PYPI containing C?
Exactly.
What if I decide to write only to Python 3?
Fair enough. But don't forget
Daniel Fetchinson wrote:
I don't think every package should work on every platform and with
every version of python. But I do think that many developers want to
support more platforms and versions than what they have access to.
Having a test farm would be beneficial to these developers and their
On 23 Apr, 17:46, Daniel Fetchinson wrote:
>
> You and I probably have a different approach to posts to c.l.p. I try
> to interpret things in the best possible light and get the most out of
> a suggestion.
There may be merit in the suggestion, but there also has to be
skepticism, even if it is re
>> The OP is just thinking out loud that it would be great if developers
>> could count on some help for testing various platforms and versions.
>> And I agree, it would indeed be great.
>>
>
> I think you interpreted the OP differently. As I said before the idea
> is not a bad one, but as a packag
> Why? Why should every package on PyPI need to support all those
> Python versions? That should be the decision of the package
> maintainer. If they want to support every version of Python back to
> 1.0, they can, and if they want to only support version 2.5 that's
> fine too.
David Lyon wrote:
What if I decide to write only to Python 3?
Fair enough. But don't forget it is open source.
So what?
Let me ask these two questions...
- What about the use case where somebody likes the code and wants
to use it on Python 2.5?
A patch, a fork, whatever.
- Should
On Thu, 23 Apr 2009 07:04:35 -0400, David Stanek
wrote:
> If I use win32com how do you expect me to support Linux?
Of course not...
> What about the many packages on PYPI containing C?
Exactly.
> What if I decide to write only to Python 3?
Fair enough. But don't forget it is open source
On Thu, Apr 23, 2009 at 12:33 AM, David Lyon wrote:
> Hi Steve,
>>> Why should the package developer dictacte which python version the
>>> package will run on ?
>>
>> Because they're the developer. Who else should decide what Python
>> versions to support?
> The developer shouldn't be making such
On Thu, Apr 23, 2009 at 2:47 AM, Daniel Fetchinson
wrote:
>
> The OP is just thinking out loud that it would be great if developers
> could count on some help for testing various platforms and versions.
> And I agree, it would indeed be great.
>
I think you interpreted the OP differently. As I sa
On Wed, 22 Apr 2009 23:47:08 -0700, Daniel Fetchinson wrote:
Why? Why should every package on PyPI need to support all those
Python versions? That should be the decision of the package
maintainer. If they want to support every version of Python back to
1.0, they can, and if the
>>> Why? Why should every package on PyPI need to support all those Python
>>> versions? That should be the decision of the package maintainer. If
>>> they want to support every version of Python back to 1.0, they can, and
>>> if they want to only support version 2.5 that's fine too.
>>
>> Why shou
On Wed, Apr 22, 2009 at 9:33 PM, David Lyon wrote:
> Hi Steve,
>>> Why should the package developer dictacte which python version the
>>> package will run on ?
>>
>> Because they're the developer. Who else should decide what Python
>> versions to support?
> The developer shouldn't be making such d
Hi Steve,
>> Why should the package developer dictacte which python version the
>> package will run on ?
>
> Because they're the developer. Who else should decide what Python
> versions to support?
The developer shouldn't be making such decisions at all
What hardware or operating systems we
On Wed, 22 Apr 2009 23:27:23 -0400, David Lyon wrote:
>> Why? Why should every package on PyPI need to support all those Python
>> versions? That should be the decision of the package maintainer. If
>> they want to support every version of Python back to 1.0, they can, and
>> if they want to only
Hi Steven,
You make some good points...
Let me try to answer them..
> Why is it the responsibility of the Python language to provide such a
> testing infrastructure?
First define "Python language".
Ok... we know it as the core interpretor. But to the developer it is also
all the packages that
On Wed, Apr 22, 2009 at 10:39 PM, David Lyon wrote:
> Hi David,
>
>
>
> Yes, I agree...
>
> But as an end-application-developer, I would put it to you that it is a lot
> of effort for developers to humanly contact the package developers every
> time we end-developers find a bug.
> The task (for us
On Wed, 22 Apr 2009 19:06:18 -0400, David Lyon wrote:
> = Introduction =
>
> One of the big challenges for Python going forward is providing a
> testing infrastructure for Python Packages.
Why is it the responsibility of the Python language to provide such a
testing infrastructure?
> There a
Hi David,
Yes, I agree...
But as an end-application-developer, I would put it to you that it is a lot
of effort for developers to humanly contact the package developers every
time we end-developers find a bug.
The task (for us developers) involves:
* finding the project p
On Wed, Apr 22, 2009 at 7:06 PM, David Lyon wrote:
>
> One of the big challenges for Python going forward is providing a testing
> infrastructure for Python Packages.
>
> There are now over 6,000 packages listed on PyPi - and this number can only
> get bigger.
>
Interesting ideas, but I'm not sur
>> Have a look at http://www.snakebite.org/
>
> I'm not clear...
>
> - are you saying they already test all the packages on pypi?
They definitely don't do that currently and I don't know what their plans are.
> - are they doing it in a one off manner?
I don't know what their plans are :)
> Pa
Hi Daniel,
On Wed, 22 Apr 2009 16:39:05 -0700, Daniel Fetchinson
wrote:
> Have a look at http://www.snakebite.org/
I'm not clear...
- are you saying they already test all the packages on pypi?
- are they doing it in a one off manner?
Pardon me asking but it raised more questions than it
On Wed, 22 Apr 2009 16:39:05 -0700, Daniel Fetchinson
wrote:
> Have a look at http://www.snakebite.org/
Interesring...
--
http://mail.python.org/mailman/listinfo/python-list
> I'm working on a python package manager gui. Mainly because I struggle on
> windows
> getting python packages installed. In my mind, there seemed to be some
> minor
> problems, but then I did the numbers. Do the numbers I writa about here
> reflect
> reality?
>
> Should we discuss stuff like this
Hi all,
I'm working on a python package manager gui. Mainly because I struggle on
windows
getting python packages installed. In my mind, there seemed to be some
minor
problems, but then I did the numbers. Do the numbers I writa about here
reflect
reality?
Should we discuss stuff like this? Debat
27 matches
Mail list logo
