Stefan Seefeld writes:
> This set of use cases ('C') is what I have most difficulties with. It
> clearly is about 'VCS <-> Roundup integration', but it's in the other
> direction. And thus, this doesn't seem to concern Roundup itself, or
> does it ? Presumably, everything needed already exists
Stefan Seefeld writes:
> While in theory [implementing a hook for closing bugs via VCS commit
> messages] is all up for customization, I think it would be nice to set
> up some conventions to guide users in how to do this (the 'token
> grammar', mostly), just for convenience.
A reference impleme
http://bugs.python.org/issue6195 (with patch)
On Wed, Jun 3, 2009 at 8:26 AM, Amaury Forgeot d'Arc wrote:
> Hello,
>
> 2009/6/3 Stefan Behnel :
>> Hi,
>>
>> I can't currently file a bug report on this, but I was told by Lisandro
>> Dalcín that there is a serious problem with the doctest module in
Aahz writes:
> It sounds like Wave requires a high-powered browser, similar to Google
> Maps. That makes me -1 because I want to continue using Lynx.
I'm not sure - I think you can implement your own choices at different
points.
What's interesting to me so far is less the current UI/flashiness
Google Wave is also still in tightly restricted beta. Gmail went
through a long invite-only period. Until we have an idea of how long
it will be until basically all python developers who want a Wave
account can get one, it doesn't make sense to talk about using it for
python development, IMO.
-j
On Thu, Jun 04, 2009 at 01:15:16PM -0400, Terry Reedy wrote:
> marked as having new content. At your leisure, you open it (or perhaps
> you have marked it 'download updates in background'). That that takes
> longer with a slow connection is no different than with other text
> streams. If y
Hi Mario,
thanks for sending these use-cases out. Let me give some feedback:
Mario wrote:
Technical talk: USE CASE A: Integrate issue property editing with
Mercurial, including:
* USE CASE A1: Allow users to close issues via tokens embedded
into commit messages.
* USE CASE A2: Allow us
Mario wrote:
USE CASE F:
Van Lindberg is concerned about code submissions from non-core
developers: how can the PSF re-license this code in the future without
talking to each contributor, whether the PSF is safe from litigation
based on copyrights of these contributions and related questions are
In article <20090604173400.gb25...@idyll.org>,
"C. Titus Brown" wrote:
> Something like MarkMail (as Dirkjan mentioned) may have a better
> interface. I'll give it a try.
Or http://search.gmane.org/ with group gmane.comp.python.devel
--
Ned Deily,
n...@acm.org
On Thu, Jun 04, 2009 at 05:54:23PM +0200, "Martin v. L?wis" wrote:
-> > Is there a good python-dev archive search mechanism (other than to
-> > google "python-dev " ;) out there? Wouldn't that help?
->
-> I would add site:mail.python.org into the google query, but apart from
-> that: what's wrong
Martin v. Löwis wrote:
In addition, you can fairly easily create a saved query to show you all
the open tickets that you are on the nosy list for. (Although I created
and saved my query for that so long ago that I don't recall the exact
details on how to go about doing that).
It's fairly easy.
Hello,
in the last few weeks I have been working on defining use-cases which
will lead the improvement of the Roundup tracker. As this is very important,
I would like your valuable input in form of comments, criticism and advices.
Use-cases in-lined:
==
Daniel is a great hacker, but t
Ben Finney wrote:
Terry Reedy writes:
Ben Finney wrote:
I watched [the Google Wave presentation] too. It appears to be
heavily reliant on *very* fast internet access for participants in a
wave. That's far from universal in the Python community, let alone
the internet at large.
Even a slow co
> In addition, you can fairly easily create a saved query to show you all
> the open tickets that you are on the nosy list for. (Although I created
> and saved my query for that so long ago that I don't recall the exact
> details on how to go about doing that).
It's fairly easy. Start a search, pu
Alexander Belopolsky wrote:
> Alternatively, one could create a python-dev profile on roundup and
> encourage people to add python-dev to the nosy list when discussion
> needs to be broaden. This way replies to all will be posted in both
> places. Once discussion gets too specialized, someone can
> Is there a good python-dev archive search mechanism (other than to
> google "python-dev " ;) out there? Wouldn't that help?
I would add site:mail.python.org into the google query, but apart from
that: what's wrong with google search?
Regards,
Martin
On Thu, Jun 4, 2009 at 5:08 PM, C. Titus Brown wrote:
> In my experience this kind automated stuff is too fragile to work
> reliably & specifically over time, which is what we would want -- "fire
> and forget".
You could a python-dev account in the tracker and allow people to nosy it.
> Is there
> Is there a document which lists these things, and explains how it is
> desirable to communicate them? I recently updated Twisted's equivalent
> document, adding minutae like which buttons to click on in our issue
> tracker, since that seems obvious to me but apparently wasn't obvious to
> a lot
On Thu, Jun 04, 2009 at 11:03:22AM -0400, Alexander Belopolsky wrote:
-> On Thu, Jun 4, 2009 at 6:20 AM, Paul Moore wrote:
-> ...
-> > I could still argue that there are downsides (need to take action to
-> > set myself as nosy on an issue, possibly setting up a new mail filter,
-> > housekeeping
Alternatively, one could create a python-dev profile on roundup and
encourage people to add python-dev to the nosy list when discussion
needs to be broaden. This way replies to all will be posted in both
places. Once discussion gets too specialized, someone can remove
python-dev from the "nosies."
On Thu, Jun 4, 2009 at 4:20 PM, Paul Moore wrote:
> Silly question, but given that Mercurial itself does *no* conversion,
> and CRLF is the only valid form for that file, why shouldn't the file
> be checked into the repository with CRLF endings, and that's the end
> of it (apart from misconfigured
On Thu, Jun 4, 2009 at 6:20 AM, Paul Moore wrote:
...
> I could still argue that there are downsides (need to take action to
> set myself as nosy on an issue, possibly setting up a new mail filter,
> housekeeping cruft, the fact that people don't quote in the same way
> on tracker items) that make
On Thu, Jun 04, 2009 at 03:20:56PM +0100, Paul Moore wrote:
> Essentially, pcbuild.sln is a binary file, and should be treated as
> such. Maybe it's an error in the Subversion setup that it's treated as
> text at all...
Subversion has a built-in notion of eol-conversion (don't know if it was
us
2009/6/4 Dirkjan Ochtman :
> On Thu, Jun 4, 2009 at 3:02 PM, Jason R. Coombs wrote:
>> I wanted to share this with the community in case anyone else runs into this
>> issue. Also, if there's a recommended procedure for addressing this issue
>> (and others that might arise due to non-native line
On Thu, Jun 4, 2009 at 3:49 PM, R. David Murray wrote:
> The above statement seems like a really odd design choice, with the
> potential for causing considerable developer coordination headaches.
>
> Any Mercurial boffins want to talk about how this works in practice?
I'm guessing that's just bec
On Thu, 4 Jun 2009 at 17:30, Oleg Broytmann wrote:
On Thu, Jun 04, 2009 at 09:02:53AM -0400, Jason R. Coombs wrote:
It seems that within the hg repository, everything has been converted to LF for
line endings. I suspect this is because HG provides no integrated support for
line-ending convers
On Thu, Jun 4, 2009 at 3:02 PM, Jason R. Coombs wrote:
> I wanted to share this with the community in case anyone else runs into this
> issue. Also, if there's a recommended procedure for addressing this issue
> (and others that might arise due to non-native line endings), I'd be
> interested
On Thu, Jun 04, 2009 at 09:02:53AM -0400, Jason R. Coombs wrote:
> It seems that within the hg repository, everything has been converted to LF
> for line endings. I suspect this is because HG provides no integrated
> support for line-ending conversions and because the hg to svn bridge is
> prob
I just wanted to share my experience with the mercurial checkout. I cloned
http://code.python.org/hg/branches/py3k to continue work on
http://bugs.python.org/issue1578269 but I found that when I click on
PC/VS8.0/pcbuild.sln, nothing happens.
This appears to be due to a bug/limitation in vslau
On Thu, Jun 04, 2009, Terry Reedy wrote:
>
> Example: if PEPs were waves, then responses could either be entered as
> live edits (with permission) or comments immediately following the
> relevant text (as with email/newsgroups) visible to all. Much easier
> than current situation. Edits are
2009/6/4 Nick Coghlan :
> Paul Moore wrote:
>> Mostly, I agree, but I definitely disagree, I'm afraid, on the use of
>> the tracker for discussions. To keep track of discussions on a ticket,
>> I have to personally keep a list of the tickets I'm interested in,
>> check back regularly to see if ther
Paul Moore wrote:
> Mostly, I agree, but I definitely disagree, I'm afraid, on the use of
> the tracker for discussions. To keep track of discussions on a ticket,
> I have to personally keep a list of the tickets I'm interested in,
> check back regularly to see if there's anything new, and keep a m
Ben Finney writes:
> Terry Reedy writes:
> > Even a slow connection would make participation in PEPs better than
> > today.
>
> How can you know that? A slow link doesn't punish email or NNTP
> communication the way an interactive web application does.
Strike that; reverse it. Should be “A slo
Terry Reedy writes:
> Ben Finney wrote:
> > I watched [the Google Wave presentation] too. It appears to be
> > heavily reliant on *very* fast internet access for participants in a
> > wave. That's far from universal in the Python community, let alone
> > the internet at large.
>
> Even a slow co
Stephen J. Turnbull wrote:
Antoine Pitrou writes:
> Terry Reedy udel.edu> writes:
> >
> > I watched and was greatly impressed by the video demo of Google's new
> > Wave collaborative communication system. I believe it would/will help
> > with some of the chronic problems we (and others)
35 matches
Mail list logo
