From metatracker at psf.upfronthosting.co.za  Sun Feb  3 18:37:06 2013
From: metatracker at psf.upfronthosting.co.za (Terry Reedy)
Date: Sun, 03 Feb 2013 17:37:06 +0000
Subject: [Tracker-discuss] [issue506] Remove Extension Modules from
	Components:
Message-ID: <1359913026.32.0.444351441791.issue506@psf.upfronthosting.co.za>


New submission from Terry Reedy:

I presume component'Extension Modules' refers to stdlib modules coded in C *instead of* Python, that latter living in /Lib. We recently removed the Extension Modules header from What's New as it was little used, even for extension modules, and b) it presumes an increasingly obsolete exclusive-or situation, whereas modules are increasingly coded in both C and Python. I propose that it also be removed from the tracker when not set already, and that the '(Lib)' suffix for the 'Library' component be removed. An additional problem for the tracker is that one must know the current situation to set the headers properly.

----------
messages: 2701
nosy: terry.reedy
priority: feature
status: unread
title: Remove Extension Modules from Components:

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

From techtonik at gmail.com  Wed Feb  6 12:05:07 2013
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 6 Feb 2013 14:05:07 +0300
Subject: [Tracker-discuss] Mirror and small fix for running tests
Message-ID: <CAPkN8xJkLRhXsDvAAZwu-xmSSsdM6dJ=o92umpauSaoxFqX5XA@mail.gmail.com>

Hi,

I setup Bitbucket mirror for b.p.o to share changes more easily.

Here is the first fix:
https://bitbucket.org/rirror/bugs.python.org/pull-request/1/fix-roundup-path-in-message-wikification/commits

`hg inc` doesn't work on the URL above, so you need to check against:
https://bitbucket.org/techtonik/bugs.python.org

P.S. I've made a wikification engine that avoids conflicts between
replacement rules, so while I'm testing it there might be other minor
changes to b.p.o instance that appear on the URL above.
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20130206/7efbc7d7/attachment.html>

From roundup-admin at psf.upfronthosting.co.za  Mon Feb 11 01:28:23 2013
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Mon, 11 Feb 2013 00:28:23 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20130211002823.EE7D3568F9@psf.upfronthosting.co.za>



The node specified by the designator in the subject of your message
("17502") does not exist.

Subject was: "[issue17502]"



Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
 . In a multipart/mixed message or part, each subpart is extracted and
   examined. The text/plain subparts are assembled to form the textual
   body of the message, to be stored in the file associated with a "msg"
   class node. Any parts of other types are each stored in separate files
   and given "file" class nodes that are linked to the "msg" node.
 . In a multipart/alternative message or part, we look for a text/plain
   subpart and ignore the other parts.
 . A message/rfc822 is treated similar tomultipart/mixed (except for
   special handling of the first text part) if unpack_rfc822 is set in
   the mailgw config section.

Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.

Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.

Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).

If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.

If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.

Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
-------------- next part --------------
Return-Path: <tracker-discuss at python.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org [82.94.164.166])
	by psf.upfronthosting.co.za (Postfix) with ESMTPS id ADF5B568F6
	for <report at bugs.python.org>; Mon, 11 Feb 2013 01:28:23 +0100 (CET)
Received: from albatross.python.org (localhost [127.0.0.1])
	by mail.python.org (Postfix) with ESMTP id 3Z47Bv2yftzSjK
	for <report at bugs.python.org>; Mon, 11 Feb 2013 01:28:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901;
	t=1360542503; bh=Gv+T5xgzWqpAaYZ3GEVW7vSS2mlQ1++avz7rQzkW97I=;
	h=MIME-Version:Content-Type:Content-Transfer-Encoding:From:To:
	 Subject:Message-Id:Date;
	b=S4abv2Q3Lz5qleA73aIx7GyLHODXbhu7s9a4cG8W2JLLDjbO+zvJ6p8aQFDfCoRGh
	 rRMt8cwGWca2/d67UEnM1WBQLlAEpN6AiiAc3/xc9nfYbeaWZO/xmuM/EiRNuXciBG
	 l3J8tbHXMcK8U7Pyr7Px2Oa9Pjm4f8y8kmjacHLA=
Received: from localhost (HELO mail.python.org) (127.0.0.1)
  by albatross.python.org with SMTP; 11 Feb 2013 01:28:23 +0100
Received: from virt-7yvsjn.psf.osuosl.org (virt-7yvsjn.psf.osuosl.org [140.211.10.72])
	by mail.python.org (Postfix) with ESMTP
	for <report at bugs.python.org>; Mon, 11 Feb 2013 01:28:22 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue17502]
Message-Id: <3Z47Bv2yftzSjK at mail.python.org>
Date: Mon, 11 Feb 2013 01:28:23 +0100 (CET)

TmV3IGNoYW5nZXNldCAxY2NmMDc1NmExM2QgYnkgTWljaGFlbCBGb29yZCBpbiBicmFuY2ggJzIu
Nyc6Cklzc3VlIDE3NTAyOiB1bml0dGVzdCBkaXNjb3Zlcnkgc2hvdWxkIHVzZSBzZWxmLnRlc3RM
b2FkZXIKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvMWNjZjA3NTZhMTNkCgoKTmV3
IGNoYW5nZXNldCA2ODYwYWM3NmJkZWEgYnkgTWljaGFlbCBGb29yZCBpbiBicmFuY2ggJzMuMic6
Cklzc3VlIDE3NTAyOiB1bml0dGVzdCBkaXNjb3Zlcnkgc2hvdWxkIHVzZSBzZWxmLnRlc3RMb2Fk
ZXIKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvNjg2MGFjNzZiZGVhCg==

From fwierzbicki at gmail.com  Wed Feb 13 19:20:51 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Wed, 13 Feb 2013 10:20:51 -0800
Subject: [Tracker-discuss] Jython tracker
Message-ID: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>

Hi all,

Just in case this ends up being a repeat:

I sent a couple of emails here, but just realized I used an email
address that is not subscribed and so they probably never reached the
list. There where two, one was asking for help as I think adding
versions is currently broken for the Jython tracker (which is my fault
as I am supposed to be the maintainer these days) but then I had what
I hope is a better idea:

Proposal: Jython to use the same tracker as CPython
==========================================

I think the problems I've been having with Jython's tracker stem from
it drifting as roundup is upgraded for python-dev. Outside of the fact
that I'm a crappy maintainer of Jython's tracker here are some
justifications for us sharing the same tracker:

* In the 3.x timeframe, we plan to push all of our *.py code into the
CPython standard library. I have the support of many core devs on
this, it just hasn't been done in a systematic way yet. I've already
done this for a couple of files (for example see
http://bugs.python.org/issue16886) but I plan to see that all of our
.py files get pushed as Jython moves to 3.x. Since half of Jython's
code will live in the CPython repo anyway, why not use the same
tracker?

* It would be better for Jython in general if we followed CPython's
development style more closely, with code reviews etc. It would be
essential for us to do this with code that actually lives in CPython's
standard library anyway.

* The database of who has signed a contributor agreement is clear in
bugs.python.org, but is not in bugs.jython.org, and it would probably
be too much work to sync them.

* The implementation effort would be small (really just add "Jython
2.5" and "Jython 2.7" to the Versions field and later "Jython 3.4" or
whatever version we end up targeting). I also don't see a need to
migrate the data from bugs.jython.org - we could just slowly re-direct
people to http:/bugs.python.org on a bug-by-bug basis until traffic to
htttp://bugs.jython.org gets slow enough, then we could either shut it
down or leave it up read-only.

What do you folks think? I have not discussed this with current Jython
devs yet, as I'd prefer to be sure that it would be acceptable here first.

-Frank

From brett at python.org  Wed Feb 13 19:40:40 2013
From: brett at python.org (Brett Cannon)
Date: Wed, 13 Feb 2013 13:40:40 -0500
Subject: [Tracker-discuss] Jython tracker
In-Reply-To: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>
References: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>
Message-ID: <CAP1=2W43=QLaMHCgDR__+JdAy5Ovi+y_-4HEprCgHeec3c589Q@mail.gmail.com>

On Wed, Feb 13, 2013 at 1:20 PM, fwierzbicki at gmail.com <
fwierzbicki at gmail.com> wrote:

> Hi all,
>
> Just in case this ends up being a repeat:
>
> I sent a couple of emails here, but just realized I used an email
> address that is not subscribed and so they probably never reached the
> list. There where two, one was asking for help as I think adding
> versions is currently broken for the Jython tracker (which is my fault
> as I am supposed to be the maintainer these days) but then I had what
> I hope is a better idea:
>
> Proposal: Jython to use the same tracker as CPython
> ==========================================
>
> I think the problems I've been having with Jython's tracker stem from
> it drifting as roundup is upgraded for python-dev. Outside of the fact
> that I'm a crappy maintainer of Jython's tracker here are some
> justifications for us sharing the same tracker:
>
> * In the 3.x timeframe, we plan to push all of our *.py code into the
> CPython standard library. I have the support of many core devs on
> this, it just hasn't been done in a systematic way yet. I've already
> done this for a couple of files (for example see
> http://bugs.python.org/issue16886) but I plan to see that all of our
> .py files get pushed as Jython moves to 3.x. Since half of Jython's
> code will live in the CPython repo anyway, why not use the same
> tracker?
>
> * It would be better for Jython in general if we followed CPython's
> development style more closely, with code reviews etc. It would be
> essential for us to do this with code that actually lives in CPython's
> standard library anyway.
>
> * The database of who has signed a contributor agreement is clear in
> bugs.python.org, but is not in bugs.jython.org, and it would probably
> be too much work to sync them.
>
> * The implementation effort would be small (really just add "Jython
> 2.5" and "Jython 2.7" to the Versions field and later "Jython 3.4" or
> whatever version we end up targeting). I also don't see a need to
> migrate the data from bugs.jython.org - we could just slowly re-direct
> people to http:/bugs.python.org on a bug-by-bug basis until traffic to
> htttp://bugs.jython.org gets slow enough, then we could either shut it
> down or leave it up read-only.
>

I quickly looked at the Jython bug tracker and there are 355 open bugs and
they seem to average activity (not necessarily new bugs) on 4 issues/day.


>
> What do you folks think? I have not discussed this with current Jython
> devs yet, as I'd prefer to be sure that it would be acceptable here first.
>

I can't wait until the first person clicks Jython 2.7 when they meant
CPython 2.7. =)

I'm fine with it due to the low volume, but people who subscribe to the
various bug lists might not love the increased volume (although the volume
does seem very small).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20130213/ce5ac265/attachment.html>

From rdmurray at bitdance.com  Wed Feb 13 20:02:23 2013
From: rdmurray at bitdance.com (R. David Murray)
Date: Wed, 13 Feb 2013 14:02:23 -0500
Subject: [Tracker-discuss] Jython tracker
In-Reply-To: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>
References: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>
Message-ID: <20130213190223.71B552500B3@webabinitio.net>

On Wed, 13 Feb 2013 10:20:51 -0800, "fwierzbicki at gmail.com" <fwierzbicki at gmail.com> wrote:
> Proposal: Jython to use the same tracker as CPython

I think you should send this to the python-committers mailing list,
and probably then to python-dev assuming it passes muster on
committers :)

I have no objection myself.

--David

From fwierzbicki at gmail.com  Wed Feb 13 21:26:55 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Wed, 13 Feb 2013 12:26:55 -0800
Subject: [Tracker-discuss] Jython tracker
In-Reply-To: <20130213190223.71B552500B3@webabinitio.net>
References: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>
	<20130213190223.71B552500B3@webabinitio.net>
Message-ID: <CADrh4zL4B9VDwG9ofTh9=wvdPu3bfZF0qWAp5U3WD1JUeE1wSQ@mail.gmail.com>

On Wed, Feb 13, 2013 at 11:02 AM, R. David Murray <rdmurray at bitdance.com> wrote:
> On Wed, 13 Feb 2013 10:20:51 -0800, "fwierzbicki at gmail.com" <fwierzbicki at gmail.com> wrote:
>> Proposal: Jython to use the same tracker as CPython
>
> I think you should send this to the python-committers mailing list,
> and probably then to python-dev assuming it passes muster on
> committers :)
Sounds good to me - hopefully subscribers to both of these lists won't
mind the repeat :)

-Frank

From fwierzbicki at gmail.com  Wed Feb 13 21:29:45 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Wed, 13 Feb 2013 12:29:45 -0800
Subject: [Tracker-discuss] Jython tracker
In-Reply-To: <CADrh4zL4B9VDwG9ofTh9=wvdPu3bfZF0qWAp5U3WD1JUeE1wSQ@mail.gmail.com>
References: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>
	<20130213190223.71B552500B3@webabinitio.net>
	<CADrh4zL4B9VDwG9ofTh9=wvdPu3bfZF0qWAp5U3WD1JUeE1wSQ@mail.gmail.com>
Message-ID: <CADrh4zL3-D2gX3P1+hMq-UjkaeO1JtGrwA3MdEpuhT-B3a8W1g@mail.gmail.com>

On Wed, Feb 13, 2013 at 12:26 PM, fwierzbicki at gmail.com
<fwierzbicki at gmail.com> wrote:
> On Wed, Feb 13, 2013 at 11:02 AM, R. David Murray <rdmurray at bitdance.com> wrote:
>> On Wed, 13 Feb 2013 10:20:51 -0800, "fwierzbicki at gmail.com" <fwierzbicki at gmail.com> wrote:
>>> Proposal: Jython to use the same tracker as CPython
>>
>> I think you should send this to the python-committers mailing list,
>> and probably then to python-dev assuming it passes muster on
>> committers :)
> Sounds good to me - hopefully subscribers to both of these lists won't
> mind the repeat :)
Actually I'll take it back to jython-dev first just to make sure that
the Jython folks are OK with this.

-Frank

From metatracker at psf.upfronthosting.co.za  Thu Feb 14 14:58:00 2013
From: metatracker at psf.upfronthosting.co.za (Ramchandra Apte)
Date: Thu, 14 Feb 2013 13:58:00 +0000
Subject: [Tracker-discuss] [issue507] Tracker allows a user to change
	username to existing	username.
Message-ID: <1360850280.22.0.32930641744.issue507@psf.upfronthosting.co.za>


New submission from Ramchandra Apte:

Subject says it all.

----------
messages: 2702
nosy: ramchandra.apte
priority: bug
status: chatting
title: Tracker allows a user to change username to existing username.

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

From fwierzbicki at gmail.com  Thu Feb 14 20:09:41 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Thu, 14 Feb 2013 11:09:41 -0800
Subject: [Tracker-discuss] Jython tracker and spambayes
Message-ID: <CADrh4z+qgC2EpjayE2tWxoDu157c_D5F5e4Xs38FWY=vnxcxwg@mail.gmail.com>

In attempting to follow

http://wiki.python.org/moin/TrackerDevelopment

to get a local Jython tracker setup, I got an error where the tracker
is looking for spambayes.py linked like so:

spambayes.py -> ../../spambayes_integration/extensions/spambayes.py

There isn't anything in these directions about spambayes - I assume
that this is a case of bit rot. Does anyone how I can work around
this?

Or would it be better for me to start with the python-dev tracker and
attempt to work backwards and get a Jython instance going from there?

-Frank

From fwierzbicki at gmail.com  Thu Feb 14 20:05:07 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Thu, 14 Feb 2013 11:05:07 -0800
Subject: [Tracker-discuss] Jython tracker
In-Reply-To: <CADrh4zL3-D2gX3P1+hMq-UjkaeO1JtGrwA3MdEpuhT-B3a8W1g@mail.gmail.com>
References: <CADrh4z+mVmRhtNUUm4BHYnsDpQ+y-uv2qmijEa_aKPXTkkTSrg@mail.gmail.com>
	<20130213190223.71B552500B3@webabinitio.net>
	<CADrh4zL4B9VDwG9ofTh9=wvdPu3bfZF0qWAp5U3WD1JUeE1wSQ@mail.gmail.com>
	<CADrh4zL3-D2gX3P1+hMq-UjkaeO1JtGrwA3MdEpuhT-B3a8W1g@mail.gmail.com>
Message-ID: <CADrh4z+ZALriORWX9_kYnYyN3_xDgKdjABwvMtD_E7KR=iqfrA@mail.gmail.com>

Circling back to jython-dev, I'm convinced that I should go ahead and
do my best to update the current Jython tracker before I consider a
move. I'll be asking lots of questions here soon I think.

-Frank

From techtonik at gmail.com  Fri Feb 15 10:28:04 2013
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 15 Feb 2013 12:28:04 +0300
Subject: [Tracker-discuss] Improve password generator complexity
Message-ID: <CAPkN8xK2hf3Qk4yc1R7bXTS3gjvZ94OEqPwfP58Z3OTU-YPpug@mail.gmail.com>

Hi,

I can not use Roundup generated password for PyPI, because it doesn't
contain any numbers. It also only 8 symbols long. How about increasing
complexity to 10 symbols with obligatory digits?


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

From fwierzbicki at gmail.com  Sun Feb 17 20:41:50 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Sun, 17 Feb 2013 11:41:50 -0800
Subject: [Tracker-discuss] tracker access
Message-ID: <CADrh4zL2tQ2Wxi5Rf=AKzY1DFJeUNaQ7Z5W3QnnmJiu=4qw7Dw@mail.gmail.com>

Hi all,

Having played around with a local tracker, I think I should be able to
fix Jython's version problems with the roundup admin tool. How do I
access the Jython tracker instance? Has it been moved to the VM
infrastructure?

-Frank

From martin at v.loewis.de  Mon Feb 18 14:48:15 2013
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 18 Feb 2013 14:48:15 +0100
Subject: [Tracker-discuss] tracker access
In-Reply-To: <CADrh4zL2tQ2Wxi5Rf=AKzY1DFJeUNaQ7Z5W3QnnmJiu=4qw7Dw@mail.gmail.com>
References: <CADrh4zL2tQ2Wxi5Rf=AKzY1DFJeUNaQ7Z5W3QnnmJiu=4qw7Dw@mail.gmail.com>
Message-ID: <5122311F.3070206@v.loewis.de>

Am 17.02.13 20:41, schrieb fwierzbicki at gmail.com:
> Hi all,
>
> Having played around with a local tracker, I think I should be able to
> fix Jython's version problems with the roundup admin tool. How do I
> access the Jython tracker instance? Has it been moved to the VM
> infrastructure?

No. Your account "frank" should continue to work.

Regards,
Martin



From fwierzbicki at gmail.com  Tue Feb 19 18:13:55 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Tue, 19 Feb 2013 09:13:55 -0800
Subject: [Tracker-discuss] Planning to retire some Jython versions
Message-ID: <CADrh4zKmHumpm=uF2LLmQ85xyS6-Bbr8V4SGr=2jObB0nOGdYg@mail.gmail.com>

Hi all,

The Jython version dropdown is a mess, and I'd like to retire a bunch
of the versions and make our versions look more like CPython's with a
small number of simple versions like "Jython 2.7" instead of a bunch
of ugly alpha, beta, and rc leftovers from the past. Testing on my
local instance, it looks like I can safely retire versions and the old
versions that are still attached to existing bugs will be left until
they are changed. So I plan to run the roundup admin like this:

/home/roundup/roundup/bin/roundup-admin -i /home/roundup/trackers/jython/

List the versions like this:
roundup> list version
  19: 2.5.1
  20: 2.5b1
  18: 2.5b0
  21: 25rc4
  23: 2.5.0
  24: 2.5.2b1
  25: 2.5.2rc
  33: Jython 2.2
  28: 2.5.3b1
  29: 2.5.3b2
  27: 2.7a1
  30: 2.7a2
  26: 2.5.2
  13: 2.2.2
   5: Jython 2.1
   1: Deferred
  31: Jython 2.5
  32: Jython 2.7

And then retire versions with commands like this:

> retire version19

Then later as I triage our outstanding bugs, I will manually move them
from (for example) "2.7b1" -> "Jython 2.7"

Am I on the right track?

-Frank

From martin at v.loewis.de  Tue Feb 19 18:17:07 2013
From: martin at v.loewis.de (=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 19 Feb 2013 18:17:07 +0100
Subject: [Tracker-discuss] Password reset
Message-ID: <5123B393.6040800@v.loewis.de>

As you know, wiki.python.org was broken into, which means that
there is a risk that the passwords were stolen (although it's
uncertain whether that actually happened).

There is a chance that some users were using the same passwords
on different services, which caused PyPI maintainers to force
a password change for everybody.

Should that also be done for bugs.python.org? What do you think?
(IIUC, we can figure out what users have changed there passwords
from the roundup journals, so we would only reset them for those
who didn't yet change them)

Regards,
Martin

From rdmurray at bitdance.com  Tue Feb 19 18:44:24 2013
From: rdmurray at bitdance.com (R. David Murray)
Date: Tue, 19 Feb 2013 12:44:24 -0500
Subject: [Tracker-discuss] Password reset
In-Reply-To: <5123B393.6040800@v.loewis.de>
References: <5123B393.6040800@v.loewis.de>
Message-ID: <20130219174424.5AD2A250BC9@webabinitio.net>

On Tue, 19 Feb 2013 18:17:07 +0100, =?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?= <martin at v.loewis.de> wrote:
> Should that also be done for bugs.python.org? What do you think?
> (IIUC, we can figure out what users have changed there passwords
> from the roundup journals, so we would only reset them for those
> who didn't yet change them)

As someone who does use unique passwords, I would find the reset annoying.
I also wonder how much good it would really do, given that the possible
password snatching was done a while ago now.

But, having said those things, I have no strong objection to doing it.

--David

From fwierzbicki at gmail.com  Tue Feb 19 22:21:10 2013
From: fwierzbicki at gmail.com (fwierzbicki at gmail.com)
Date: Tue, 19 Feb 2013 13:21:10 -0800
Subject: [Tracker-discuss] Planning to retire some Jython versions
In-Reply-To: <CADrh4zKmHumpm=uF2LLmQ85xyS6-Bbr8V4SGr=2jObB0nOGdYg@mail.gmail.com>
References: <CADrh4zKmHumpm=uF2LLmQ85xyS6-Bbr8V4SGr=2jObB0nOGdYg@mail.gmail.com>
Message-ID: <CADrh4zKM2Zq3AWMfr0_-sjC_FYW0grg_r7ytcSiGDJNN6k41Dg@mail.gmail.com>

By experimenting with some rarely used versions I was able to convince
myself that this was a safe path.

-Frank

From metatracker at psf.upfronthosting.co.za  Sat Feb 23 20:58:43 2013
From: metatracker at psf.upfronthosting.co.za (Petri Lehtinen)
Date: Sat, 23 Feb 2013 19:58:43 +0000
Subject: [Tracker-discuss] [issue508] 'NoneType' object has no
	attribute	'user_has_selected_nickname'
Message-ID: <1361649523.28.0.651717211054.issue508@psf.upfronthosting.co.za>


New submission from Petri Lehtinen:

After reviewing and commenting, I clicked the "publish + mail comments", and got a Django error page:

AttributeError at /review/17267/publish
'NoneType' object has no attribute 'user_has_selected_nickname'

...

Traceback:
File "/usr/lib/pymodules/python2.6/django/core/handlers/base.py" in get_response
  95.                     response = middleware_method(request, callback, callback_args, callback_kwargs)
File "/home/roundup/trackers/tracker/rietveld/rietveld_helper/middleware.py" in process_view
  37.         response = view_func(request, *view_args, **view_kwargs)
File "/home/roundup/trackers/tracker/rietveld/codereview/views.py" in login_wrapper
  657.     return func(request, *args, **kwds)
File "/home/roundup/trackers/tracker/rietveld/codereview/views.py" in issue_wrapper
  741.     return func(request, *args, **kwds)
File "/home/roundup/trackers/tracker/rietveld/codereview/views.py" in xsrf_wrapper
  694.     return func(request, *args, **kwds)
File "/home/roundup/trackers/tracker/rietveld/codereview/views.py" in publish
  3013.                                              'draft_message': draft_message,
File "/home/roundup/trackers/tracker/rietveld/codereview/views.py" in respond
  502.     must_choose_nickname = not account.user_has_selected_nickname()

Exception Type: AttributeError at /review/17267/publish
Exception Value: 'NoneType' object has no attribute 'user_has_selected_nickname'


When going back and clicking it again, it worked ok.

----------
messages: 2703
nosy: petri.lehtinen
priority: bug
status: unread
title: 'NoneType' object has no attribute 'user_has_selected_nickname'

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