Am 21.01.2010 04:33, schrieb Ben Finney:
> Georg Brandl writes:
>
>> But I've no intention to restrict feature releases to "every 18-24
>> months". What now?
>
> Now we take further discussion to the ‘python-ideas’ forum.
Whoever "we" is. You can be assured I've not planned any further
discuss
Georg Brandl writes:
> But I've no intention to restrict feature releases to "every 18-24
> months". What now?
Now we take further discussion to the ‘python-ideas’ forum.
--
\ “We must respect the other fellow's religion, but only in the |
`\ sense and to the extent that we resp
Am 20.01.2010 03:43, schrieb David Lyon:
>> Barry was talking about mirrors of the python code. It is true a
>> "package manager" could be developed based on a SCM, however you need
>> to implement this far away from the stdlib and get traction with it
>> within the community long before inclusion
David Lyon wrote:
> On 2; Who knows what their life cycle is. CVS is pretty much
> dead, and svn looks like it is on the way out.
> I can't think of how anything could be better than
> mercurial or bzr but I know I will be proved wrong.
I believe you misunderstood what Matthieu m
David Lyon pythontest.org> writes:
>
> I think I'll have better chances with PEPs.
>
> Being honest, if wonderful libraries like Sphinx and Mercurial
> and Git and BZR can't make it into the stdlib, then there is
> no hope for even newer code to get in there.
> [snip]
This is python-ideas mater
Barry Warsaw writes:
> (Besides, git in the stdlib doesn't make much sense :).
"Dulwich."
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-d
> That's only two points. :-)
In French, we say that several starts with 2 ;)
> On 1; If that's true, I won't mention git again.
I tis, you can check on the git repository (it's a mix of C, perl,
shell scripts, Python, ...)
> On 2; Who knows what their life cycle is.
You can check on their web
Matthieu,
>> I'd be happy to see bzr and mercurial and git all made it together
>> into the stdlib for python 3. That would give a superb updating
>> mechanism for python that would propel python well beyond
>> the dinosaur badlands of CPAN and other languages.
>
> I think there are several point
> I'd be happy to see bzr and mercurial and git all made it together
> into the stdlib for python 3. That would give a superb updating
> mechanism for python that would propel python well beyond
> the dinosaur badlands of CPAN and other languages.
I think there are several points that make them no
"David Lyon" writes:
> Well using that logic, distutils is an application..
Distutils is an application, the function of which is essential to
allowing sane development of Python packages. It's a special case. We
need to strictly limit the number of special cases, not gleefully add to
them.
--
Barry Warsaw writes:
> On Jan 20, 2010, at 03:29 PM, David Lyon wrote:
> >So here I am as a user doing things the 'right' way.
>
> Actually, you're not. It's not up to the Python community to initiate
> this. If you really want this, you should engage with the relevant
> DVCS communities and push
> "David Lyon" writes:
>
>> Being honest, if wonderful libraries like Sphinx and Mercurial and Git
>> and BZR can't make it into the stdlib, then there is no hope for even
>> newer code to get in there.
>
> Those are applications, not libraries. Applications don't belong in the
> standard library.
Okay, last follow up on this and then I'm going to bed. :)
On Jan 20, 2010, at 03:29 PM, David Lyon wrote:
>> On Jan 19, 2010, at 08:09 PM, Barry Warsaw wrote:
>>
>> I'd be surprised if any of the big 3 DVCS developers would actually /want/
>> their stuff in the stdlib.
>
>If they ask, they'll ge
> On Jan 19, 2010, at 08:09 PM, Barry Warsaw wrote:
>
> I'd be surprised if any of the big 3 DVCS developers would actually /want/
> their stuff in the stdlib.
If they ask, they'll get told they're motorbike-shedding. "It's better
if their users ask". So here I am as a user doing things the 'right
On Jan 20, 2010, at 02:43 PM, David Lyon wrote:
>> On Tue, Jan 19, 2010 at 7:51 PM, Jesse Noller wrote:
>> A SCM is not a "package management system".
>
>Exactly. It almost makes the need for a "package management system"
>pretty much obsolete if you can update your code directly from
>the develo
On Tue, Jan 19, 2010 at 21:43, David Lyon wrote:
>
> Being honest, if wonderful libraries like Sphinx and Mercurial
> and Git and BZR can't make it into the stdlib, then there is
> no hope for even newer code to get in there.
>
I'm not entirely sure I see why the inclusion of a SCM into the stdl
"David Lyon" writes:
> Being honest, if wonderful libraries like Sphinx and Mercurial and Git
> and BZR can't make it into the stdlib, then there is no hope for even
> newer code to get in there.
Those are applications, not libraries. Applications don't belong in the
standard library.
--
\
On Tue, Jan 19, 2010 at 10:43 PM, David Lyon wrote:
[snip]
> Being honest, if wonderful libraries like Sphinx and Mercurial
> and Git and BZR can't make it into the stdlib, then there is
> no hope for even newer code to get in there.
Did you ever stop to think that some package authors do not wan
> On Tue, Jan 19, 2010 at 7:51 PM, Jesse Noller wrote:
> Python 3 is still modularized, still has a standard library, etc. If
> you're really interested in helping with the standard library, get on
> stdlib-sig, and get ready to write code and PEPs.
Thank you for your direction to move these ite
On Jan 19, 2010, at 08:09 PM, Jesse Noller wrote:
>The decision to move python's source control from SVN to mercurial was
>controversial enough; including 3 or more scm libraries into core
>would be an intractable uphill mountain of bike sheds.
I'd be surprised if any of the big 3 DVCS developers
On Tue, Jan 19, 2010 at 7:51 PM, David Lyon wrote:
>> On Jan 20, 2010, at 10:16 AM, Barry wrote:
>
>>> So does that mean we could update the stdlib for a given
>>> python version using this ?
>>
>> In a sense, yes (if I understand your question correctly).
>
> Yeah, it just needs an implementation
> On Jan 20, 2010, at 10:16 AM, Barry wrote:
>> So does that mean we could update the stdlib for a given
>> python version using this ?
>
> In a sense, yes (if I understand your question correctly).
Yeah, it just needs an implementation.
> The one thing I am unsure about, mostly because I have n
On Jan 20, 2010, at 10:16 AM, David Lyon wrote:
>Hi Barry,
>
>That looks very interesting...
Hi David,
>So does that mean we could update the stdlib for a given
>python version using this ?
In a sense, yes (if I understand your question correctly).
You can use Bazaar to branch any of the 4 Pyt
Hi Barry,
That looks very interesting...
So does that mean we could update the stdlib for a given
python version using this ?
David
> I've just updated the Launchpad mirrors for the 4 active Python branches,
> trunk, py3k, 2.6, and 3.1. These used to mirror the defunct Bazaar
> branches
> on
24 matches
Mail list logo
