From metatracker at psf.upfronthosting.co.za  Thu Nov  3 19:12:17 2011
From: metatracker at psf.upfronthosting.co.za (ericsnow)
Date: Thu, 03 Nov 2011 18:12:17 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1320343937.58.0.683538308395.issue402@psf.upfronthosting.co.za>


ericsnow <ericsnowcurrently at gmail.com> added the comment:

I wanted to confirm what Nadeem last responded.  This is pretty annoying.

----------
nosy: +ericsnow

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue402>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Nov 19 06:58:46 2011
From: metatracker at psf.upfronthosting.co.za (Loic Jaquemet)
Date: Sat, 19 Nov 2011 05:58:46 +0000
Subject: [Tracker-discuss] [issue426] ctypeslib codegenerator chokes on
	CvQualifiedType
Message-ID: <1321682326.92.0.521464077665.issue426@psf.upfronthosting.co.za>


New submission from Loic Jaquemet <loic.jaquemet+python at gmail.com>:

When using xml2py from the ctypeslib codegenerator 
http://svn.python.org/projects/ctypes/trunk/ctypeslib/ctypeslib/codegen/codegenerator.py

Attribute CVQualifiedType are not correctly parsed.
There are no size and align attributes.
We should use the super-type size and align attribute.
patch attached

Traceback (most recent call last):
  File "/usr/bin/xml2py", line 6, in <module>
    sys.exit(main())
  File "/usr/lib/pymodules/python2.7/ctypeslib/xml2py.py", line 199, in main
    types=options.kind)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 873, in generate_code
    loops = gen.generate_code(items)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 784, in generate_code
    loops = self.generate_items(items)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 773, in generate_items
    self.generate_all(sorted(items, self.cmpitems))
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 757, in generate_all
    self.generate(item)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 753, in generate
    mth(item)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 401, in Structure
    self.generate(struct.get_body())
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 753, in generate
    mth(item)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 560, in StructureBody
    pack = calc_packing(body.struct, fields)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 124, in calc_packing
    _calc_packing(struct, fields, pack, isStruct)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 97, in _calc_packing
    s, a = storage(f.typ)
  File "/usr/lib/pymodules/python2.7/ctypeslib/codegen/codegenerator.py", line 75, in storage
    return int(t.size), int(t.align)
AttributeError: 'CvQualifiedType' object has no attribute 'size'

----------
files: codegenerator.py.diff
messages: 2306
nosy: trolldbois
priority: bug
status: unread
title: ctypeslib codegenerator chokes on CvQualifiedType

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue426>
_______________________________________________________
-------------- next part --------------
--- codegenerator.py.orig	2011-02-18 08:16:47.000000000 -0500
+++ codegenerator.py	2011-11-19 00:47:13.197943171 -0500
@@ -72,6 +72,8 @@
         if t.max.lower() == GCCXML_NOSIZE:
             return 0, a
         return s * (int(t.max) - int(t.min) + 1), a
+    elif isinstance(t, typedesc.CvQualifiedType):
+        return int(t.typ.size), int(t.typ.align)
     return int(t.size), int(t.align)
 
 class PackingError(Exception):

From metatracker at psf.upfronthosting.co.za  Sun Nov 20 10:44:03 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 20 Nov 2011 09:44:03 +0000
Subject: [Tracker-discuss] [issue426] ctypeslib codegenerator chokes on
	CvQualifiedType
In-Reply-To: <1321682326.92.0.521464077665.issue426@psf.upfronthosting.co.za>
Message-ID: <1321782243.88.0.377322158796.issue426@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

This is the bug tracker for issues with the Python roundup installation, not for bugs in Python. For bugs in Python, use bugs.python.org.

----------
nosy: +loewis
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue426>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Nov 24 18:15:38 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 24 Nov 2011 17:15:38 +0000
Subject: [Tracker-discuss] [issue120] Allow users to report msg/file
	instances as misclassified
In-Reply-To: <87sl79vn7r.fsf@uterus.efod.se>
Message-ID: <1322154938.44.0.804430460979.issue120@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Allowing all developers to reclassify messages sounds good.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue120>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Nov 24 21:33:42 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 24 Nov 2011 20:33:42 +0000
Subject: [Tracker-discuss] [issue427] Time synchronization defect
Message-ID: <1322166822.28.0.27718847317.issue427@psf.upfronthosting.co.za>


New submission from Martin v. L?wis <martin at v.loewis.de>:

http://psf.upfronthosting.co.za is currently off by ca 15s from UTC. This broke my new OpenID login procedure, which assume a maximum offset of 10s. I worked around by allowing up to 5 minutes.

Can time synchronization be improved?

----------
assignedto: izak
messages: 2309
nosy: izak, loewis
priority: urgent
status: unread
title: Time synchronization defect

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue427>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Nov 24 22:23:04 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 24 Nov 2011 21:23:04 +0000
Subject: [Tracker-discuss] [issue415] Mercurial integration: regression in
	diff generation
In-Reply-To: <1312642512.39.0.425778233696.issue415@psf.upfronthosting.co.za>
Message-ID: <1322169784.01.0.646169092163.issue415@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Using the mercurial diff format is intentional - the git format is utterly broken and must not be used.

As for changes that are reverted: what changes specifically? (or: what versions should it have compared instead of comparing 0c1c9bb590a9 and bc362109eed8?)

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue415>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Nov 24 22:29:11 2011
From: metatracker at psf.upfronthosting.co.za (Izak Burger)
Date: Thu, 24 Nov 2011 21:29:11 +0000
Subject: [Tracker-discuss] [issue427] Time synchronization defect
In-Reply-To: <1322166822.28.0.27718847317.issue427@psf.upfronthosting.co.za>
Message-ID: <CAGscxN0EiXNg9h4AqgNThHan5nR_ZkwO+GPX_Gju9MNMwHMvew@mail.gmail.com>


Izak Burger <izak at upfrontsystems.co.za> added the comment:

On Thu, Nov 24, 2011 at 10:33 PM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:
> http://psf.upfronthosting.co.za is currently off by ca 15s from UTC. This broke my new OpenID login procedure, which assume a maximum offset of 10s. I worked around by allowing up to 5 minutes.
>
> Can time synchronization be improved?

Ntp died. Usually ntp is as stable as, well, apache or postfix, it
just never falls over, but somehow it did. I ran ntpdate and restarted
ntpd. That should fix it.

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue427>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Nov 24 23:40:51 2011
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Thu, 24 Nov 2011 22:40:51 +0000
Subject: [Tracker-discuss] [issue428] Patch generator and dependent feature
	branches
Message-ID: <1322174451.03.0.274638212194.issue428@psf.upfronthosting.co.za>


New submission from Nick Coghlan <ncoghlan at gmail.com>:

The diff generator seems to get confused when the most recent merge with default was via a different branch: http://bugs.python.org/issue11682

The pep380 branch in my BitBucket sandbox depends on the new feature in the get_opinfo branch, so the merge flow is currently: default->get_opinfo->pep380

(I haven't closely examined the patch I just generated, but it still didn't look right on an initial glance)

----------
messages: 2312
nosy: loewis, ncoghlan
priority: bug
status: unread
title: Patch generator and dependent feature branches

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue428>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Nov 26 09:31:22 2011
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Sat, 26 Nov 2011 08:31:22 +0000
Subject: [Tracker-discuss] [issue429] Can't generate patch for issue 11816
Message-ID: <1322296282.92.0.118756601209.issue429@psf.upfronthosting.co.za>


New submission from Nick Coghlan <ncoghlan at gmail.com>:

Every time I hit "Create Patch" on issue 11816 for my get_opinfo branch, I get the error message: "9512712044a6.diff is already available"

It first started happening when I hit 'Create Patch' after unlinking the previous diff (which used the filename that Roundup is apparently trying to reuse). However, relinking that file didn't make the problem go away.

----------
messages: 2313
nosy: loewis, ncoghlan
priority: bug
status: unread
title: Can't generate patch for issue 11816
topic: patch_generator

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue429>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Nov 28 12:36:15 2011
From: metatracker at psf.upfronthosting.co.za (Weeble)
Date: Mon, 28 Nov 2011 11:36:15 +0000
Subject: [Tracker-discuss] [issue430] Email address revealed to
	unauthenticated user
Message-ID: <1322480175.95.0.81590440887.issue430@psf.upfronthosting.co.za>


New submission from Weeble <clockworksaint at gmail.com>:

Click on "lost your login". Enter any username and submit. The following page reports the email address that is associated with that account.

I would not expect the email address to be revealed by this action.

----------
messages: 2314
nosy: weeble
priority: bug
status: unread
title: Email address revealed to unauthenticated user

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue430>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Nov 29 04:58:32 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 29 Nov 2011 03:58:32 +0000
Subject: [Tracker-discuss] [issue430] Email address revealed to
	unauthenticated user
In-Reply-To: <1322480175.95.0.81590440887.issue430@psf.upfronthosting.co.za>
Message-ID: <1322539112.8.0.27299926831.issue430@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

FWIW this has been already reported upstream: http://issues.roundup-tracker.org/issue2550716

----------
nosy: +ezio.melotti
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue430>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Nov 29 22:09:01 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 29 Nov 2011 21:09:01 +0000
Subject: [Tracker-discuss] [issue430] Email address revealed to
	unauthenticated user
In-Reply-To: <1322480175.95.0.81590440887.issue430@psf.upfronthosting.co.za>
Message-ID: <1322600941.89.0.131875035164.issue430@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

I think some indication must be given to a legitimate user, as the user otherwise may not recall what email account to check. In the specific case of bugs.python.org, it may, in particular, be a sourceforge address.

If people are worried that users massively read out email addresses from the bug tracker, I'd rather rate-limit password reset operations by IP address, to one reset per hour. 

If users use this to research a specific email address of a specific user account, I'd rather not stop them from doing so. People who are too worried about revealing their email address should arrange to use a separate address for places such as the bug tracker.

----------
nosy: +loewis

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue430>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 09:15:18 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 30 Nov 2011 08:15:18 +0000
Subject: [Tracker-discuss] [issue428] Patch generator and dependent feature
	branches
In-Reply-To: <1322174451.03.0.274638212194.issue428@psf.upfronthosting.co.za>
Message-ID: <1322640918.71.0.59187166588.issue428@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

The diff generator will always generate a patch against some revision of cpython. IIUC, you would want it to diff against a base revision that is *not* in cpython.

I'm doubtful that this is a desirable feature:
a) your patch cannot be applied as-is to cpython, as you would need to commit the feature it depends on first.
b) the Rietveld integration would not be able to locate the base revision of the patch, since it's not in cpython.

AFAICT, the generated patch is then correct, in the sense of above: it *is* the patch that needs to be applied to cpython to integrate the pep380 branch into Python.

If/when get_opinfo gets merged into cpython first, you may be confronted with a tricky merge operation, since the change set from default will duplicate what you have merged/branched-off already (most likely, hg will figure out that this is the very same changes twice). Creating a patch then will show just the changes of your branch.

I was considering adding UI for a "base" branch, but it wouldn't have occurred to me that the base branch may not exist in cpython. We would then also need the notion of a "base repository".

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue428>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 11:47:34 2011
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Wed, 30 Nov 2011 10:47:34 +0000
Subject: [Tracker-discuss] [issue428] Patch generator and dependent feature
	branches
In-Reply-To: <1322174451.03.0.274638212194.issue428@psf.upfronthosting.co.za>
Message-ID: <1322650054.69.0.757797885803.issue428@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Yeah, I'm thinking I may be able to fix the generated patches by changing my merge workflow to be:

default -> get_opinfo
default -> pep380
get_opinfo -> pep380

That way, the Create Patch button on both issues would generate a patch that can be applied directly to CPython tip.

A patch to be *reviewed* on the latter issue would still need to be generated manually, though. (Since the generated patch will include the disassembler changes as well as the PEP 380 ones)

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue428>
_______________________________________________________

From techtonik at gmail.com  Wed Nov 30 13:05:56 2011
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 30 Nov 2011 15:05:56 +0300
Subject: [Tracker-discuss] [issue394] Better integration with Rietveld
 code review tool
In-Reply-To: <1317916402.98.0.821961763617.issue394@psf.upfronthosting.co.za>
References: <1303156350.85.0.792534425783.issue394@psf.upfronthosting.co.za>
	<1317916402.98.0.821961763617.issue394@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xKZ81FoYrf0yRp-aPyUZxOm7vP3JbbhV1juO_PBk5Tomg@mail.gmail.com>

Rietveld now has an API that allows to query all messages for an issue -
http://code.google.com/p/rietveld/wiki/APIs However, to make a progress on
this bug, we need now two things from Martin.

> Martin, is the process to install Rietveld for documented somewhere?

It seems that it isn't, but it is at least evident that it runs through
gae2django -
http://svn.python.org/view/tracker/instances/python-dev/rietveld/ Basically,
there should not be differences in interacting with Rietveld running on
AppEngine or with gae2django version. But I remember that Roundup
integration was using some hacks to inject patches into Rietveld DB.

I propose to move all python.org specific patches for Rietveld to a
separate branch in official repository (like it currently works for
Chromium). It will be easier to sync and maintain.

> What version of Rietveld is currently deployed on python.org?

-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20111130/77850070/attachment.html>

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 13:06:18 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 12:06:18 +0000
Subject: [Tracker-discuss] [issue394] Better integration with Rietveld code
	review tool
In-Reply-To: <1317916402.98.0.821961763617.issue394@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xKZ81FoYrf0yRp-aPyUZxOm7vP3JbbhV1juO_PBk5Tomg@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

Rietveld now has an API that allows to query all messages for an issue -
http://code.google.com/p/rietveld/wiki/APIs However, to make a progress on
this bug, we need now two things from Martin.

> Martin, is the process to install Rietveld for documented somewhere?

It seems that it isn't, but it is at least evident that it runs through
gae2django -
http://svn.python.org/view/tracker/instances/python-dev/rietveld/ Basically,
there should not be differences in interacting with Rietveld running on
AppEngine or with gae2django version. But I remember that Roundup
integration was using some hacks to inject patches into Rietveld DB.

I propose to move all python.org specific patches for Rietveld to a
separate branch in official repository (like it currently works for
Chromium). It will be easier to sync and maintain.

> What version of Rietveld is currently deployed on python.org?

----------
title: Better integration with Rietveld code	review tool -> Better integration with Rietveld code review tool

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue394>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20111130/77850070/attachment-0001.html>

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 13:43:51 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 12:43:51 +0000
Subject: [Tracker-discuss] [issue431] Link meta to tracker source code
Message-ID: <1322657031.2.0.11743534232.issue431@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

Can anybody add support to link revision references to source code browser for this tracker? It will save me (and people) a lot of time when tracking how changes for tickets are made to tracker.

The specific commit I am interested ATM is in msg2204 but I don't remember the repository path to look it up. As a side note, it would also be convenient to have the link to source code layout/explanation/browser in help menu on the left.

----------
messages: 2320
nosy: techtonik
priority: urgent
status: unread
title: Link meta to tracker source code

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue431>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 13:44:55 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 12:44:55 +0000
Subject: [Tracker-discuss] [issue431] Link meta to tracker source code
In-Reply-To: <1322657031.2.0.11743534232.issue431@psf.upfronthosting.co.za>
Message-ID: <1322657095.49.0.989194263192.issue431@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Upstream issue http://issues.roundup-tracker.org/issue2550737

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue431>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 14:04:26 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 30 Nov 2011 13:04:26 +0000
Subject: [Tracker-discuss] [issue428] Patch generator and dependent feature
	branches
In-Reply-To: <1322174451.03.0.274638212194.issue428@psf.upfronthosting.co.za>
Message-ID: <1322658266.15.0.799694806521.issue428@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

So what do you propose should roundup do here? I propose that the current behavior is actually "correct", and that mismatches with user expectations should be dealt with by education.

For the patch generation to work in the expected manner, you could create one additional branch:

- default -> pep380pure -> pep380full
- default -> get_opinfo -> pep380full

You then submit the pep380pure branch for review, and pep380full for testing.

Alternatively, you could just do your pep380 changes on the default branch of a dedicated pep-380 clone; the patch generation can very well compare a clone's default branch with cpython's default branch.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue428>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 16:08:53 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 30 Nov 2011 15:08:53 +0000
Subject: [Tracker-discuss] [issue431] Link meta to tracker source code
In-Reply-To: <1322657031.2.0.11743534232.issue431@psf.upfronthosting.co.za>
Message-ID: <1322665733.65.0.849378232227.issue431@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

You can find it here: http://svn.python.org/view?view=rev&revision=88874
You can also enter any revision number on that page to find the corresponding commit.  http://wiki.python.org/moin/TrackerDevelopment has more informations.

----------
nosy: +ezio.melotti

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue431>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 16:34:54 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 30 Nov 2011 15:34:54 +0000
Subject: [Tracker-discuss] [issue422] Keyboard shortcuts
In-Reply-To: <1317625041.71.0.42670053076.issue422@psf.upfronthosting.co.za>
Message-ID: <1322667294.35.0.127978250811.issue422@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> These shortcuts use a single key, so they don't need to be combined with ctrl/alt in order to work.
> That means no conflicts with key combinations that the browsers might use.
Good.

> OTOH, it conflicts with the find-as-you-type, but I don't know how used that is.
It does.  I guess only advanced users use find as you type, and they know they can use Ctrl-F to start an explicit search.

> The form elements are special-cased, so while you are writing a message in the comment field, the shortcuts
> are disabled.
Good too.

> Is there something else that I'm missing?  If you have interesting links, please share.
I?ll need to dig them up, but the gist of it was that commonly-used browsers took up (nearly) all key combinations, so using only numbers for accesskeys is recommended.

> I'm also considering making this optional, with a checkbox somewhere to enable/disable it.
Maybe.  (The location would be the user profile I think.)

>> I?ve noticed the new help sub-sidebar; please don?t abuse HTML a elements.
> As I wrote in the source, that's just a temporary workaround.  If the shortcuts work well I'll move their
> documentation in the devguide and remove that sub-menu in a couple of weeks or so.
Did you get the feedback you wanted?  Here it works well (X11, Iceweasel).

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue422>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 16:54:38 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 30 Nov 2011 15:54:38 +0000
Subject: [Tracker-discuss] [issue422] Keyboard shortcuts
In-Reply-To: <1317625041.71.0.42670053076.issue422@psf.upfronthosting.co.za>
Message-ID: <1322668478.25.0.554303940773.issue422@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Thanks for the feedback.  I think this can be closed now.
I'll move the instructions to the devguide when I'll fix http://bugs.python.org/issue13455

----------
status: testing -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue422>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 17:16:47 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 16:16:47 +0000
Subject: [Tracker-discuss] [issue422] Keyboard shortcuts
In-Reply-To: <1317625041.71.0.42670053076.issue422@psf.upfronthosting.co.za>
Message-ID: <1322669807.81.0.00339518440832.issue422@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

I don't think it is resolved. =) Go to http://codereview.appspot.com/ and press Shift-?  This is a standard way to document keyboard shortcuts.

----------
nosy: +techtonik
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue422>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 17:18:27 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 16:18:27 +0000
Subject: [Tracker-discuss] [issue431] Link meta to tracker source code
In-Reply-To: <1322657031.2.0.11743534232.issue431@psf.upfronthosting.co.za>
Message-ID: <1322669907.74.0.365894158069.issue431@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

What is required to make this autolinking available in this instance of Roundup?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue431>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 17:19:08 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 16:19:08 +0000
Subject: [Tracker-discuss] [issue431] Link meta to tracker source code
In-Reply-To: <1322657031.2.0.11743534232.issue431@psf.upfronthosting.co.za>
Message-ID: <1322669948.56.0.630339220978.issue431@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

http://wiki.python.org/moin/TrackerDevelopment contains way too much information for me to crunch on this time, sorry. =(

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue431>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 17:26:11 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 30 Nov 2011 16:26:11 +0000
Subject: [Tracker-discuss] [issue422] Keyboard shortcuts
In-Reply-To: <1317625041.71.0.42670053076.issue422@psf.upfronthosting.co.za>
Message-ID: <1322670371.19.0.853857331588.issue422@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

How standard is 'Shift+?'?
If it doesn't conflict with browser shortcuts and if it's a common/known shortcut I could try to come up with something similar.

----------
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue422>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 17:30:01 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 30 Nov 2011 16:30:01 +0000
Subject: [Tracker-discuss] [issue431] Link meta to tracker source code
In-Reply-To: <1322657031.2.0.11743534232.issue431@psf.upfronthosting.co.za>
Message-ID: <1322670601.63.0.781421587076.issue431@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

A new extension like http://svn.python.org/view/tracker/instances/python-dev/extensions/local_replace.py?view=markup in  http://svn.python.org/view/tracker/instances/meta/extensions/

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue431>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 19:08:15 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 18:08:15 +0000
Subject: [Tracker-discuss] [issue422] Keyboard shortcuts
In-Reply-To: <1317625041.71.0.42670053076.issue422@psf.upfronthosting.co.za>
Message-ID: <1322676495.8.0.0449369776064.issue422@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

It is standard for all Google products, I believe.

----------
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue422>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Nov 30 19:11:33 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Wed, 30 Nov 2011 18:11:33 +0000
Subject: [Tracker-discuss] [issue422] Keyboard shortcuts
In-Reply-To: <1317625041.71.0.42670053076.issue422@psf.upfronthosting.co.za>
Message-ID: <1322676693.48.0.652290304055.issue422@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Note that Rietveld version is independent of keyboard layout. See this code http://codereview.appspot.com/2055042/diff/20002/static/script.js for example. Feel free to reuse everything that's in green.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue422>
_______________________________________________________