[Tracker-discuss] [issue508] 'NoneType' object has no attribute 'user_has_selected_nickname'

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: unread -> resol

[Tracker-discuss] [issue490] Review links crash after changing username

Berker Peksag added the comment: Thanks for the report and for the patch. The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: unread -> resol

[Tracker-discuss] [issue365] No issue exists with that id

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue434] ProgrammingError while deleting patch set

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue432] Rietveld traceback

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue435] Rietveld Code Review Tool bugs

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue424] Rietveld: AssertionError when trying to reply to comments

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue382] Bad CC on review

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue517] Issue Tracker crashes when replying to patch review

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue394] Better integration with Rietveld code review tool

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue554] Add special mark to Rietvelds emails

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue485] Autoclosing Rietveld issue

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: unread -> resol

[Tracker-discuss] [issue404] Personal comment rating

Berker Peksag added the comment: I agree with Serhiy. Closing this issue. -- nosy: +berker.peksag status: chatting -> resolved ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/is

[Tracker-discuss] [issue518] Plaintext connections when logging in

Berker Peksag added the comment: All HTTP requests now redirected to HTTPS: $ curl -I http://bugs.python.org HTTP/1.1 301 Moved Permanently Date: Tue, 12 Jun 2018 18:47:14 GMT Server: Apache/2.2.16 (Debian) Location: https://bugs.python.org/ Content-Type: text/html; charset=iso-8859-1

[Tracker-discuss] [issue156] Have a Core Bug Chaser Create a Bug Reporting Screencast

Berker Peksag added the comment: After 11 years, I think the better place to discuss this is the core-workflow list. Closing this issue. -- nosy: +berker.peksag status: chatting -> resolved ___ PSF Meta Tracker &l

[Tracker-discuss] [issue410] More useful filenames for patches generated from hg

Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue387] Need OpenID login for this tracker

Berker Peksag added the comment: I don't think it's worth to add OpenID login since the level of traffic and active users are pretty low here. -- nosy: +berker.peksag status: unread -> resolved ___ PSF Meta T

[Tracker-discuss] [issue644] 'Random Issue' Button isn't working

Berker Peksag added the comment: Thanks for the update, John. For future readers, here's a link to the discussion on the roundup-devel list: https://sourceforge.net/p/roundup/mailman/roundup-devel/thread/20180708014103.75EE34C0A5C%40itserver6.locald

[Tracker-discuss] [issue657] PyGILState_Release FatalError[auto-releasing thread-state, but no thread-state for this thread]

Berker Peksag added the comment: Thanks for the report, but this is not the correct place to report such issues. Please use https://bugs.python.org/ instead. Also, I'd first try getting help on python-list (https://mail.python.org/mailman/listinfo/python-list) or stackoverflow.com as

[Tracker-discuss] [issue660] Find a new bug in Python 3

Berker Peksag added the comment: > In windows, we always give a path using '\' and python 3 can correctly dispose > it just as we using '/' in Linux. But if you offer > a path in windows with a '\' followed as 'r'. Everyting will goes wrong. Y

[Tracker-discuss] [issue663] Add user to nosy list when PR is attached to issue

New submission from Berker Peksag : Currently, I'm getting this email when I've submitted a PR: -- keywords: +patch pull_requests: +8502 stage: -> patch review I think it would be nice if we could try to add the user to nosy list when attaching a P

<    1   2