-----Ursprungligt meddelande----- Från: scipy-dev-bounces@scipy.org [mailto:scipy-dev-bounces@scipy.org] För scipy-dev-request@scipy.org Skickat: den 27 februari 2009 10:19 Till: scipy-dev@scipy.org Ämne: Scipy-dev Digest, Vol 64, Issue 66 Send Scipy-dev mailing list submissions to scipy-dev@scipy.org To subscribe or unsubscribe via the World Wide Web, visit http://projects.scipy.org/mailman/listinfo/scipy-dev or, via email, send a message with subject or body 'help' to scipy-dev-request@scipy.org You can reach the person managing the list at scipy-dev-owner@scipy.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Scipy-dev digest..." Today's Topics: 1. Re: Scipy workflow (and not tools). (David Cournapeau) 2. Re: Scipy workflow (and not tools). (Ondrej Certik) 3. Re: The future of SciPy and its development infrastructure (St?fan van der Walt) 4. Re: RFR 503, 849: more robust implementation of real Bessel I_v (St?fan van der Walt) 5. Re: The future of SciPy and its development infrastructure (Prabhu Ramachandran) 6. Re: The future of SciPy and its development infrastructure (Travis E. Oliphant) 7. Re: The future of SciPy and its development infrastructure (David Cournapeau) 8. Improving the bug tracking workflow: starting document (David Cournapeau) 9. Re: The future of SciPy and its development infrastructure (Pauli Virtanen) ---------------------------------------------------------------------- Message: 1 Date: Fri, 27 Feb 2009 13:23:30 +0900 From: David Cournapeau <cournape@gmail.com> Subject: Re: [SciPy-dev] Scipy workflow (and not tools). To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <5b8d13220902262023i675a4bc4ra8bf981267fb2156@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Fri, Feb 27, 2009 at 9:08 AM, Pauli Virtanen <pav@iki.fi> wrote:
Fri, 27 Feb 2009 00:48:00 +0200, St?fan van der Walt wrote:
2009/2/27 Pauli Virtanen <pav@iki.fi>:
If you want to discuss Git, you can probably steal from here:
Ah, yes, good reminder!
Could you give me a quick rundown of why you used --mirror earlier on when adding the remote?
The --mirror option adds
? ? ? ?fetch = +refs/*:refs/* ? ? ? ?mirror = yes
to [remote "origin"]. So one wouldn't need to edit .git/config manually.
However, the --mirror has another effect which I missed earlier: it makes the remote consider all heads its own, so that "git remote prune origin" would drop all branches, including local ones. Similar issue with "git fetch". So I think it's not the correct solution.
? ?***
But all of that is moot now. I finally figured out that I must push to the mirror with
? ? ? ?git push git@github.com:pv/numpy-svn.git \ ? ? ? ? ? ? ? ?+refs/remotes/*:refs/heads/* +master
Then it can be cloned simply with
? ? ? ?git clone --origin svn git://github.com/pv/scipy-svn.git
And "--origin svn" only because we want svn/trunk instead of origin/trunk. Also git-svn can be activated:
? ? ? ?git svn init -s --prefix=svn/ http://svn.scipy.org/svn/scipy ? ? ? ?git svn rebase -l
And as a bonus, the SVN branches are visible on Github!
Ah, nice, I did not find a way to do this - I used a dirty script to get local branches and update them instead. One thing which is still annoying is that tags are considered as branches - but I guess there is no way around it, since svn does not have any tag concept. David ------------------------------ Message: 2 Date: Thu, 26 Feb 2009 20:54:21 -0800 From: Ondrej Certik <ondrej@certik.cz> Subject: Re: [SciPy-dev] Scipy workflow (and not tools). To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <85b5c3130902262054i27fca37fq7e2d58c6cf06626a@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Thu, Feb 26, 2009 at 8:23 PM, David Cournapeau <cournape@gmail.com> wrote:
On Fri, Feb 27, 2009 at 9:08 AM, Pauli Virtanen <pav@iki.fi> wrote:
Fri, 27 Feb 2009 00:48:00 +0200, St?fan van der Walt wrote:
2009/2/27 Pauli Virtanen <pav@iki.fi>:
If you want to discuss Git, you can probably steal from here:
Ah, yes, good reminder!
Could you give me a quick rundown of why you used --mirror earlier on when adding the remote?
The --mirror option adds
? ? ? ?fetch = +refs/*:refs/* ? ? ? ?mirror = yes
to [remote "origin"]. So one wouldn't need to edit .git/config manually.
However, the --mirror has another effect which I missed earlier: it makes the remote consider all heads its own, so that "git remote prune origin" would drop all branches, including local ones. Similar issue with "git fetch". So I think it's not the correct solution.
? ?***
But all of that is moot now. I finally figured out that I must push to the mirror with
? ? ? ?git push git@github.com:pv/numpy-svn.git \ ? ? ? ? ? ? ? ?+refs/remotes/*:refs/heads/* +master
Then it can be cloned simply with
? ? ? ?git clone --origin svn git://github.com/pv/scipy-svn.git
And "--origin svn" only because we want svn/trunk instead of origin/trunk. Also git-svn can be activated:
? ? ? ?git svn init -s --prefix=svn/ http://svn.scipy.org/svn/scipy ? ? ? ?git svn rebase -l
And as a bonus, the SVN branches are visible on Github!
Ah, nice, I did not find a way to do this - I used a dirty script to get local branches and update them instead. One thing which is still annoying is that tags are considered as branches - but I guess there is no way around it, since svn does not have any tag concept.
Btw, I guess you already know it, but if you need to clone the git repository (for example David's) and then you would like to update it using git-svn with the latest svn from scipy, here is the howto: http://subtlegradient.com/articles/2008/04/22/cloning-a-git-svn-clone E.g. basically: git svn init http://macromates.com/svn/Bundles/trunk/Bundles/Ruby.tmbundle -R svn cp .git/refs/remotes/origin/master .git/refs/remotes/git-svn git svn fetch Ondrej ------------------------------ Message: 3 Date: Fri, 27 Feb 2009 07:37:46 +0200 From: St?fan van der Walt <stefan@sun.ac.za> Subject: Re: [SciPy-dev] The future of SciPy and its development infrastructure To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <9457e7c80902262137j69478ba9h910dcfac3949af26@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi Travis 2009/2/27 Travis E. Oliphant <oliphant@enthought.com>:
My biggest concern is having a bunch of code sitting in a queue and not reviewed, nor committed --- or the review processes become too onerous and code not making it through because of what I would consider to be "ticky-tacky technicalities."
That's a very valid concern. David and I are experimenting with different issue trackers and plugins for trac, to see how best to generate a "review pool". I.e., what I'd like to see is that, if you only have 5 minutes to work on SciPy in the evening, you can a) Go to trac and click on "tickets for review" b) Review a couple of tickets or a) Go to trac and click on "reviewed tickets" b) Apply those patches or a) Go to trac and click on "unresolved issues" b) Fix the bug c) Upload the patch for review Technically, (c) is a bit challenging. I note your concern that it would become difficult to check in, so what I would like is to have a script such as scipy-submit -t 212 -m "Do not deallocate memory after object disposal." which then uploads the patch to the codereview site, and adds a link to ticket 212 with the commit message and review URL. All of this can be done via the web, but I'd prefer to have a CLI available. Do you have any suggestions or further concerns? Thanks St?fan ------------------------------ Message: 4 Date: Fri, 27 Feb 2009 07:42:52 +0200 From: St?fan van der Walt <stefan@sun.ac.za> Subject: Re: [SciPy-dev] RFR 503, 849: more robust implementation of real Bessel I_v To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <9457e7c80902262142w333024a4nd1a2e0afb8082231@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 2009/2/27 Pauli Virtanen <pav@iki.fi>:
Urgh, the codereview app does not add any distinguishing headers to the mails it sends for each comment.
I'll ask on the rietveld list. Cheers St?fan ------------------------------ Message: 5 Date: Fri, 27 Feb 2009 11:22:55 +0530 From: Prabhu Ramachandran <prabhu@aero.iitb.ac.in> Subject: Re: [SciPy-dev] The future of SciPy and its development infrastructure To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <49A77FB7.7010406@aero.iitb.ac.in> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 02/27/09 11:07, St?fan van der Walt wrote:
scipy-submit -t 212 -m "Do not deallocate memory after object disposal."
which then uploads the patch to the codereview site, and adds a link to ticket 212 with the commit message and review URL. All of this can be done via the web, but I'd prefer to have a CLI available.
Do you have any suggestions or further concerns?
I've not contributed anything in years to scipy but I have a practical problem that might be worth addressing eventually (others might be in a similar position) -- my entire network is firewalled and I can only access the web behind an authenticated http proxy. The firewall does allow ssh connections out though but that seems useless to access a git repository hosted on github say. The git user guide does not mention the word proxy (google wasn't too much help either) and it would be nice if all the tools allowed people to use the workflow from behind a firewall without too much pain. This may or may not be possible right away and may be low priority but is worth keeping in mind. Thanks. prabhu ------------------------------ Message: 6 Date: Fri, 27 Feb 2009 00:00:49 -0600 From: "Travis E. Oliphant" <oliphant@enthought.com> Subject: Re: [SciPy-dev] The future of SciPy and its development infrastructure To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <49A78191.20902@enthought.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed St?fan van der Walt wrote:
Hi Travis
2009/2/27 Travis E. Oliphant <oliphant@enthought.com>:
My biggest concern is having a bunch of code sitting in a queue and not reviewed, nor committed --- or the review processes become too onerous and code not making it through because of what I would consider to be "ticky-tacky technicalities."
That's a very valid concern. David and I are experimenting with different issue trackers and plugins for trac, to see how best to generate a "review pool". I.e., what I'd like to see is that, if you only have 5 minutes to work on SciPy in the evening, you can
a) Go to trac and click on "tickets for review" b) Review a couple of tickets
or
a) Go to trac and click on "reviewed tickets" b) Apply those patches
or
a) Go to trac and click on "unresolved issues" b) Fix the bug c) Upload the patch for review
Technically, (c) is a bit challenging. I note your concern that it would become difficult to check in, so what I would like is to have a script such as
scipy-submit -t 212 -m "Do not deallocate memory after object disposal."
Something like that would be nice! Thanks for the continued effort at improving workflow. -Travis ------------------------------ Message: 7 Date: Fri, 27 Feb 2009 14:48:01 +0900 From: David Cournapeau <david@ar.media.kyoto-u.ac.jp> Subject: Re: [SciPy-dev] The future of SciPy and its development infrastructure To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <49A77E91.4010101@ar.media.kyoto-u.ac.jp> Content-Type: text/plain; charset=ISO-8859-1 Prabhu Ramachandran wrote:
On 02/27/09 11:07, St?fan van der Walt wrote:
scipy-submit -t 212 -m "Do not deallocate memory after object disposal."
which then uploads the patch to the codereview site, and adds a link to ticket 212 with the commit message and review URL. All of this can be done via the web, but I'd prefer to have a CLI available.
Do you have any suggestions or further concerns?
I've not contributed anything in years to scipy but I have a practical problem that might be worth addressing eventually (others might be in a similar position) -- my entire network is firewalled and I can only access the web behind an authenticated http proxy.
I have similar issues, and I agree those are valid concerns. Those can be very painful to handle. In my case, there is no DNS server, the names are resolved by the proxy; my workstation can only resolve the proxy name. This breaks most applications out there. ssh is not easy, because ssh cannot resolve names - for git, I managed to get things worked out for github using corkscrew. This is the kind of things which I managed to do once and hope never have to do again, so I can't tell you exactly how to do it: http://en.wikipedia.org/wiki/Corkscrew_(program) My .ssh/config looks like this for github Host gitproxy User git HostName ssh.github.com Port 443 ProxyCommand /usr/bin/corkscrew www 3128 %h %p IdentityFile /home/david/.ssh/id_rsa.pub Where www is the name of my proxy and 3128 the port. FWIW, svn has similar problems. I could never commit anything from a former internship location because of some proxy limitations - it is one of the reasons which pushed me into git for scipy development, actually. If you can't access either ssh or proxy, my experience is that you are more or less screwed with any tool out there - but with DVCS, you can at least put your changes aside and commit them later from an easier connection. cheers, David ------------------------------ Message: 8 Date: Fri, 27 Feb 2009 17:28:53 +0900 From: David Cournapeau <david@ar.media.kyoto-u.ac.jp> Subject: [SciPy-dev] Improving the bug tracking workflow: starting document To: SciPy Developers List <scipy-dev@scipy.org> Message-ID: <49A7A445.4010800@ar.media.kyoto-u.ac.jp> Content-Type: text/plain; charset=ISO-8859-1 Hi, Following the discussions, I have started to write a small document highlighting my current gripes with trac. I focus on some common scenario, and pin-point trac limitations. I mention possible new tools at the end, but that's not the main point: everybody who is also disatisfied with trac, and maybe even more importantly people who are currently satisfied and think their scenario is not covered should feel free to comment/modify it: http://scipy.org/scipy/numpy/wiki/ImprovingIssueWorkflow I put the initial version in svn as well: http://projects.scipy.org/scipy/numpy/browser/trunk/doc/neps/newbugtracker.r st. cheers, David ------------------------------ Message: 9 Date: Fri, 27 Feb 2009 09:18:22 +0000 (UTC) From: Pauli Virtanen <pav@iki.fi> Subject: Re: [SciPy-dev] The future of SciPy and its development infrastructure To: scipy-dev@scipy.org Message-ID: <go8b4u$jpb$1@ger.gmane.org> Content-Type: text/plain; charset=UTF-8 Fri, 27 Feb 2009 11:22:55 +0530, Prabhu Ramachandran wrote: [clip]
I've not contributed anything in years to scipy but I have a practical problem that might be worth addressing eventually (others might be in a similar position) -- my entire network is firewalled and I can only access the web behind an authenticated http proxy. The firewall does allow ssh connections out though but that seems useless to access a git repository hosted on github say.
Git can clone over HTTP, just change git:// to http:// and it seems to work. I can also clone through a proxy with export http_proxy=http://username:password@proxy:port/ git clone http://whatever Pushing over HTTP is another question... It's probably not possible to push to Github over HTTPS, but maybe there are places that you can push to with only HTTP authentication. -- Pauli Virtanen ------------------------------ _______________________________________________ Scipy-dev mailing list Scipy-dev@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-dev End of Scipy-dev Digest, Vol 64, Issue 66 *****************************************
participants (1)
-
Stefan Waller