On Wed, 2011-10-19 at 22:17 +0300, anatoly techtonik wrote:
> Does everybody feel comfortable with 'stage' and 'resultion' fields in
> tracker?
>
> I understand that 'stage' defines workflow and 'resolution' is status
> indicator, but the question is - do we really need to separate them?
> For ex
On Thu, Oct 20, 2011 at 2:53 AM, senthil.kumaran
wrote:
> http://hg.python.org/cpython/rev/489237756488
> changeset: 72988:489237756488
> branch: 2.7
> parent: 72984:86e3943d0d5b
> user: Senthil Kumaran
> date: Thu Oct 20 00:52:24 2011 +0800
> summary:
> Fix closes Issu
On Wed, Oct 19, 2011 at 14:17, anatoly techtonik wrote:
> The resolution will likely be 'fixed' which doesn't give any info
> about if the patch was actually committed or not.
If there's no commit update in the messages on the issue, you should
assume it was not committed. At that point, either i
Does everybody feel comfortable with 'stage' and 'resultion' fields in tracker?
I understand that 'stage' defines workflow and 'resolution' is status
indicator, but the question is - do we really need to separate them?
For example, right now when a ticket's 'status' is closed (all right -
there is
Éric Araujo wrote:
> Do we have buildbots with the rpm programs installed? There is a patch
> I want to commit to fix a bug in distutils’ bdist_rpm; it was tested by
> the patch author, but I cannot verify it on my machine, so I would feel
> safer if our buildbot fleet would cover that.
Yes, the
Hi,
Do we have buildbots with the rpm programs installed? There is a patch
I want to commit to fix a bug in distutils’ bdist_rpm; it was tested by
the patch author, but I cannot verify it on my machine, so I would feel
safer if our buildbot fleet would cover that.
Thanks
Sam Partington gmail.com> writes:
> Ok ok, I give up. Apparently I am the only one who wants to be able
> to run different versions of python based on the shebang line AND add
> occasional arguments to the python command line.
It sounds as if adding arguments to the shebang line will work for a
On 19 October 2011 00:18, Mark Hammond wrote:
> On 18/10/2011 8:59 PM, Sam Partington wrote:
...
>> I added shebangs to
>> all files as appropriate for devel/stable branch, and initially I
>> changed the python build targets from "python -utt build.py" to
>> "./build.py" and I lost the -utt functi
On 19 October 2011 00:18, Mark Hammond wrote:
> On 18/10/2011 8:59 PM, Sam Partington wrote:
>> ... and I can imagine lots of users swapping "python" with
>> "py".
>
> Why would users choose to do that? Using "python" presumably already works
> for them, so what benefit do they get? If the main
