-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2009, at 2:03 PM, Mark Dickinson wrote:
On Wed, Feb 25, 2009 at 2:23 PM, Barry Warsaw ba...@python.org
wrote:
This is now done. Please let me know if you have any problems with
the
mirrors.
Is the cron job that's supposed to
On Fri, Feb 27, 2009 at 7:26 PM, Barry Warsaw ba...@python.org wrote:
On Feb 25, 2009, at 2:03 PM, Mark Dickinson wrote:
Is the cron job that's supposed to update the bzr repository still
running?
I think I have this fixed now. The branch updater is running on dinsdale
now, but I'm currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 20, 2009, at 10:09 AM, Barry Warsaw wrote:
I've just upgraded the Bazaar mirrors on code.python.org to use bzr
1.12. We now have the opportunity to upgrade the repository format
for better performance. Because of the bzr-svn
Barry Warsaw wrote:
I've just upgraded the Bazaar mirrors on code.python.org to use bzr
1.12. We now have the opportunity to upgrade the repository format
for better performance. Because of the bzr-svn requirement, we need a
rich root format. Upgrading to 1.9-rich-root could buy us some
On Wed, Feb 25, 2009 at 2:23 PM, Barry Warsaw ba...@python.org wrote:
This is now done. Please let me know if you have any problems with the
mirrors.
Is the cron job that's supposed to update the bzr repository still running?
I'm getting 'No revisions to pull' when I do 'bzr pull' for the py3k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2009, at 2:03 PM, Mark Dickinson wrote:
On Wed, Feb 25, 2009 at 2:23 PM, Barry Warsaw ba...@python.org
wrote:
This is now done. Please let me know if you have any problems with
the
mirrors.
Is the cron job that's supposed to
Steve Holden wrote:
Steven Bethard wrote:
On Sat, Feb 21, 2009 at 1:11 PM, Paul Moore p.f.mo...@gmail.com wrote:
PS Just for my own information, am I correct in thinking that it is
*only* Bazaar in the (D)VCS world that has this problem, to any real
extent? I know old Mercurial clients
Michael Foord wrote:
Steve Holden wrote:
Steven Bethard wrote:
On Sat, Feb 21, 2009 at 1:11 PM, Paul Moore p.f.mo...@gmail.com wrote:
PS Just for my own information, am I correct in thinking that it is
*only* Bazaar in the (D)VCS world that has this problem, to any real
extent? I
David Cournapeau writes:
Er, what are people without access to PPAs doing building Python from
a VCS checkout?
I don't see the link between access to PPA and building Python from
sources.
I didn't say from source, I said from a VCS checkout. If using a
*specific* recent official
I didn't say from source, I said from a VCS checkout. If using a
*specific* recent official release of a core tool is bureaucratically
infeasible, it would IMO be very unusual if you're allowed to checkout
and build arbitrary versions of Python, rather than using a version
provided by your
Martin v. Löwis writes:
sjt sez:
I didn't say from source, I said from a VCS checkout. If using a
*specific* recent official release of a core tool is bureaucratically
infeasible, it would IMO be very unusual if you're allowed to checkout
and build arbitrary versions of Python,
2009/2/21 Stephen J. Turnbull step...@xemacs.org:
Besides, if Barry makes this experiment *now* and enough people speak
up that it will make it difficult for them to contribute to Python,
the Bazaar proponents can revert to an older version of Bazaar before
a final decision is made.
In
You're ignoring the second paragraph quoted above. I'm *not* denying
that such environments are common. The question is Do developers
*restricted to such environments* really have an impact on Python
development to outweigh the real cost of standardizing on an older
implementation of Bazaar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
I didn't say from source, I said from a VCS checkout. If using a
*specific* recent official release of a core tool is bureaucratically
infeasible, it would IMO be very unusual if you're allowed to checkout
and build
Wouldn't such hypothetical core Python developers be able to build and
run their own local copy of bzr, using that self-compiled Python?
It has been hypothetical for a while, but it never was about core
developers.
Regards,
Martin
___
Python-Dev
I'm *not* ignoring them; I'm stating a strong belief that the great
majority of them will not be adversely affected by this change. Since
almost by definition they're not likely to speak up very much, I'm
happy to hear arguments from a qualified observer (such as yourself)
on their behalf.
Stephen J. Turnbull stephen at xemacs.org writes:
Whether it is depends on when a DVCS gets selected. If it gets selected
after lenny+1 has been released, I see no problem with requiring version
1.12 (or whatever lenny+1 will then ship with).
I really hope we won't have to wait
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 7:15 AM, Stephen J. Turnbull wrote:
Besides, if Barry makes this experiment *now* and enough people speak
up that it will make it difficult for them to contribute to Python,
the Bazaar proponents can revert to an older version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 4:57 AM, Martin v. Löwis wrote:
There is no problem with people building their own versions of Python,
though - they do so in their home directories, and OS security
mechanisms prevent them from doing harm to other users.
As
-On [20090221 21:30], Barry Warsaw (ba...@python.org) wrote:
I think no matter what DVCS gets chosen
Isn't that getting ahead of the game? I thought that the choice whether or
not a DVCS gets chosen is part of that PEP?
--
Jeroen Ruigrok van der Werven asmodai(-at-)in-nomine.org / asmodai
イェルーン
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 3:35 PM, Jeroen Ruigrok van der Werven wrote:
-On [20090221 21:30], Barry Warsaw (ba...@python.org) wrote:
I think no matter what DVCS gets chosen
Isn't that getting ahead of the game? I thought that the choice
whether or
2009/2/21 Martin v. Löwis mar...@v.loewis.de:
Wouldn't such hypothetical core Python developers be able to build and
run their own local copy of bzr, using that self-compiled Python?
It has been hypothetical for a while, but it never was about core
developers.
Given that it *is* all
On Sat, Feb 21, 2009 at 1:11 PM, Paul Moore p.f.mo...@gmail.com wrote:
PS Just for my own information, am I correct in thinking that it is
*only* Bazaar in the (D)VCS world that has this problem, to any real
extent? I know old Mercurial clients can interact with newer servers
(ie, the wire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 4:11 PM, Paul Moore wrote:
PS Just for my own information, am I correct in thinking that it is
*only* Bazaar in the (D)VCS world that has this problem, to any real
extent? I know old Mercurial clients can interact with newer
2009/2/21 Barry Warsaw ba...@python.org:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 4:11 PM, Paul Moore wrote:
PS Just for my own information, am I correct in thinking that it is
*only* Bazaar in the (D)VCS world that has this problem, to any real
extent? I know old
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Moore wrote:
2009/2/21 Barry Warsaw ba...@python.org:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 4:11 PM, Paul Moore wrote:
PS Just for my own information, am I correct in thinking that it is
*only* Bazaar in the
Steven Bethard wrote:
On Sat, Feb 21, 2009 at 1:11 PM, Paul Moore p.f.mo...@gmail.com wrote:
PS Just for my own information, am I correct in thinking that it is
*only* Bazaar in the (D)VCS world that has this problem, to any real
extent? I know old Mercurial clients can interact with newer
On Sat, Feb 21, 2009 at 9:15 PM, Stephen J. Turnbull step...@xemacs.org wrote:
Martin v. Löwis writes:
sjt sez:
I didn't say from source, I said from a VCS checkout. If using a
*specific* recent official release of a core tool is bureaucratically
infeasible, it would IMO be very
This has been true for a number of cases over the years: whether the
repostiory format, or the wire protocol, sometimes changes which
materially *improve* the user's experience may require upgrading the
client on the user's machine. In the case of SVN, upgrading to 1.5 gets
vastly better
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've just upgraded the Bazaar mirrors on code.python.org to use bzr
1.12. We now have the opportunity to upgrade the repository format
for better performance. Because of the bzr-svn requirement, we need a
rich root format. Upgrading to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 20, 2009, at 10:09 AM, Barry Warsaw wrote:
I've just upgraded the Bazaar mirrors on code.python.org to use bzr
1.12. We now have the opportunity to upgrade the repository format
for better performance. Because of the bzr-svn
On Sat, Feb 21, 2009 at 6:21 AM, Barry Warsaw ba...@python.org wrote:
Adam Olsen reminds me that bzr 1.9 won't be supported by default in Ubuntu
until Jaunty in April and Thomas reminds me that Debian still just has 1.5.
In both those cases, you can use the PPA:
David Cournapeau writes:
On Sat, Feb 21, 2009 at 6:21 AM, Barry Warsaw ba...@python.org wrote:
In both those cases, you can use the PPA:
Please note that for many people in a corporate/university
environment, this is not an option. Granted, you can install it by
yourself at this
On Sat, Feb 21, 2009 at 3:52 PM, Stephen J. Turnbull step...@xemacs.org wrote:
David Cournapeau writes:
On Sat, Feb 21, 2009 at 6:21 AM, Barry Warsaw ba...@python.org wrote:
In both those cases, you can use the PPA:
Please note that for many people in a corporate/university
34 matches
Mail list logo
