Hello Dirkjan, We are going to start working on a few things in Distutils at Pycon outside the trunk. I was about to start this work in the svn sandbox, but if possible I'd rather have a repo at hg.python.org as well Regards Tarek -- Tarek Ziadé | http://ziade.org
On Sun, Feb 21, 2010 at 21:44, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
We are going to start working on a few things in Distutils at Pycon outside the trunk.
This would be full branch of Python? In that case, we probably don't want to go there yet, because the hashes of the python repository currently on hg.p.o will definitely change more and that will cause problems. Cheers, Dirkjan
On Sun, Feb 21, 2010 at 9:47 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
No that would be just a new fresh empty repository for "distutils 2" that will be developed outside the Python stdlib for a while, and will enventually get back into it when it's ready I guess. I figured it would be easier for people to fork/clone it to work on it if ts a DVCS, even if it's just me that can push in it for the moment. But if this is too much trouble right now don't worry about it. Tarek -- Tarek Ziadé | http://ziade.org
On Sun, Feb 21, 2010 at 21:56, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
Sounds good, per the policy for Mercurial hosting, see the other thread (but weren't you going to improve distutils, instead of rewriting it?). Only problem is, right now you could only push through me. So, start off in hg, put it on bitbucket for now and we'll set it up on hg.p.o when Martin gets back to me (also see the other thread). Cheers, Dirkjan
On Sun, Feb 21, 2010 at 10:54 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
I am improving it, continuing the work that has been started. Here's the bottom line: We decided during the language summit that I would perform this work outside the stdlib (e.g. fork distutils), and leave the current distutils in its current state to avoid any backward compat work nightmares, and possible issues with some third party projects that might be sensitive to some changes even if performed in the internals. (it happened) The new PEPs will be implemented in distutils2 (non-definitive name) and I'll be able to remove stuff we don't want to keep in there without worrying. I was reluctant with this idea at first because I've started to work on this in distutils itself and I wanted the work to be included in 2.7 so we wouldn't wait 18 more months. But now I am fully convinced this is the best plan : around the time 2.7 is out, we will be able to release distutils2 and provide a version for 2.4/2.5/2.6/3.1 as well, and get feedback from the community to prepare a rock-solid version for 3.3. And if we make some mistakes in it, we will be able to correct them faster. We do want this package in the stdlib, because its part of what people are expecting in the batteries included, but as Guido explained during the summit, a package in the stdlib has one foot in the grave.
Sounds good, thanks Tarek -- Tarek Ziadé | http://ziade.org
On Feb 22, 2010, at 12:04 PM, Dirkjan Ochtman wrote:
The checkout URL for non-ssh read-only access is: http://hg.python.org/distutils2/ in case anyone else is searching for it. S
2010/2/22 ssteinerX@gmail.com <ssteinerx@gmail.com>:
Right. As Maciej asked about this, let's discuss it here: there are currently no emails for these repositories. I'd like to get that going; should I just have it send emails for each push to the normal commits mailing list for now? Cheers, Dirkjan
On Tue, Feb 23, 2010 at 00:57, "Martin v. Löwis" <martin@v.loewis.de> wrote:
Can I use that to filter out distutils2 commits?
Well, I don't think we'll do commit emails for distutils2 or unittest2, only for benchmarks (to python-checkins, anyway). I'll make sure that you can filter something out by repository. Cheers, Dirkjan
On Tue, Feb 23, 2010 at 1:04 AM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
Why is that ? I do want them as much as someone else would want the benchmarks ones I suppose. The whole subversion repository (including the sandbox) is sending mails to python-checkins, so I think we need to have the same policy here if possible, and use for example a subject prefix to make the filtering easier (which should be simpler with multiple mercurial repositories as a matter of fact) Tarek -- Tarek Ziadé | http://ziade.org
2010/2/23 Tarek Ziadé <ziade.tarek@gmail.com>:
Note sure what do you mean by doubts. I have no doubts I want to receive those emails to work on this code ;)
Some of the other committers didn't think they wanted email on python-checkins from all the projects that will ever be hosted on hg.python.org, so there should be some selection. I'll let you fight with them over where the email from distutils2 goes; I'm just maintaining this. Cheers, Dirkjan
2010/2/23 Dirkjan Ochtman <dirkjan@ochtman.nl>:
Sorry I didn't mean to stress you on this, I just want to make sure I'll be able to get those mails at some point. The solution, I think, is to create one checking mailing list per hosted project at hg.python.org. And possibly reunite several projects under a single mailing list. Let me know if it fits your maintenance process. if so I'll ask for a mailing list for this particular repo. Thanks for your work, Tarek -- Tarek Ziadé | http://ziade.org
On Feb 23, 2010, at 01:04 AM, Dirkjan Ochtman wrote:
I think we should have commit emails for all projects hosted on hg.python.org. Those emails should perhaps go to different mailing lists, but post-commit emails are a great way for community members to follow the developments of our various projects. -Barry
On Tue, Feb 23, 2010 at 08:32, Barry Warsaw <barry@python.org> wrote:
I definitely agree that there should be post-push mails for every repo, it's just a matter of what list to send them too, since python-checkins may not be the right one for each repo hosted there. Cheers, Dirkjan
On Sun, Feb 21, 2010 at 21:44, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
We are going to start working on a few things in Distutils at Pycon outside the trunk.
This would be full branch of Python? In that case, we probably don't want to go there yet, because the hashes of the python repository currently on hg.p.o will definitely change more and that will cause problems. Cheers, Dirkjan
On Sun, Feb 21, 2010 at 9:47 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
No that would be just a new fresh empty repository for "distutils 2" that will be developed outside the Python stdlib for a while, and will enventually get back into it when it's ready I guess. I figured it would be easier for people to fork/clone it to work on it if ts a DVCS, even if it's just me that can push in it for the moment. But if this is too much trouble right now don't worry about it. Tarek -- Tarek Ziadé | http://ziade.org
On Sun, Feb 21, 2010 at 21:56, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
Sounds good, per the policy for Mercurial hosting, see the other thread (but weren't you going to improve distutils, instead of rewriting it?). Only problem is, right now you could only push through me. So, start off in hg, put it on bitbucket for now and we'll set it up on hg.p.o when Martin gets back to me (also see the other thread). Cheers, Dirkjan
On Sun, Feb 21, 2010 at 10:54 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
I am improving it, continuing the work that has been started. Here's the bottom line: We decided during the language summit that I would perform this work outside the stdlib (e.g. fork distutils), and leave the current distutils in its current state to avoid any backward compat work nightmares, and possible issues with some third party projects that might be sensitive to some changes even if performed in the internals. (it happened) The new PEPs will be implemented in distutils2 (non-definitive name) and I'll be able to remove stuff we don't want to keep in there without worrying. I was reluctant with this idea at first because I've started to work on this in distutils itself and I wanted the work to be included in 2.7 so we wouldn't wait 18 more months. But now I am fully convinced this is the best plan : around the time 2.7 is out, we will be able to release distutils2 and provide a version for 2.4/2.5/2.6/3.1 as well, and get feedback from the community to prepare a rock-solid version for 3.3. And if we make some mistakes in it, we will be able to correct them faster. We do want this package in the stdlib, because its part of what people are expecting in the batteries included, but as Guido explained during the summit, a package in the stdlib has one foot in the grave.
Sounds good, thanks Tarek -- Tarek Ziadé | http://ziade.org
On Feb 22, 2010, at 12:04 PM, Dirkjan Ochtman wrote:
The checkout URL for non-ssh read-only access is: http://hg.python.org/distutils2/ in case anyone else is searching for it. S
2010/2/22 ssteinerX@gmail.com <ssteinerx@gmail.com>:
Right. As Maciej asked about this, let's discuss it here: there are currently no emails for these repositories. I'd like to get that going; should I just have it send emails for each push to the normal commits mailing list for now? Cheers, Dirkjan
On Tue, Feb 23, 2010 at 00:57, "Martin v. Löwis" <martin@v.loewis.de> wrote:
Can I use that to filter out distutils2 commits?
Well, I don't think we'll do commit emails for distutils2 or unittest2, only for benchmarks (to python-checkins, anyway). I'll make sure that you can filter something out by repository. Cheers, Dirkjan
On Tue, Feb 23, 2010 at 1:04 AM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
Why is that ? I do want them as much as someone else would want the benchmarks ones I suppose. The whole subversion repository (including the sandbox) is sending mails to python-checkins, so I think we need to have the same policy here if possible, and use for example a subject prefix to make the filtering easier (which should be simpler with multiple mercurial repositories as a matter of fact) Tarek -- Tarek Ziadé | http://ziade.org
2010/2/23 Tarek Ziadé <ziade.tarek@gmail.com>:
Note sure what do you mean by doubts. I have no doubts I want to receive those emails to work on this code ;)
Some of the other committers didn't think they wanted email on python-checkins from all the projects that will ever be hosted on hg.python.org, so there should be some selection. I'll let you fight with them over where the email from distutils2 goes; I'm just maintaining this. Cheers, Dirkjan
2010/2/23 Dirkjan Ochtman <dirkjan@ochtman.nl>:
Sorry I didn't mean to stress you on this, I just want to make sure I'll be able to get those mails at some point. The solution, I think, is to create one checking mailing list per hosted project at hg.python.org. And possibly reunite several projects under a single mailing list. Let me know if it fits your maintenance process. if so I'll ask for a mailing list for this particular repo. Thanks for your work, Tarek -- Tarek Ziadé | http://ziade.org
On Feb 23, 2010, at 01:04 AM, Dirkjan Ochtman wrote:
I think we should have commit emails for all projects hosted on hg.python.org. Those emails should perhaps go to different mailing lists, but post-commit emails are a great way for community members to follow the developments of our various projects. -Barry
On Tue, Feb 23, 2010 at 08:32, Barry Warsaw <barry@python.org> wrote:
I definitely agree that there should be post-push mails for every repo, it's just a matter of what list to send them too, since python-checkins may not be the right one for each repo hosted there. Cheers, Dirkjan
participants (5)
-
"Martin v. Löwis" -
Barry Warsaw -
Dirkjan Ochtman -
ssteinerX＠gmail.com -
Tarek Ziadé