From metatracker at psf.upfronthosting.co.za Thu Jan 8 15:08:27 2015 From: metatracker at psf.upfronthosting.co.za (pnugues) Date: Thu, 08 Jan 2015 14:08:27 +0000 Subject: [Tracker-discuss] [issue561] Sorting with locale does not work properly with Python3 on Macos Message-ID: <1420726107.29.0.866027643228.issue561@psf.upfronthosting.co.za> New submission from pnugues: The sorted() function does not work properly with macosx. Here is a script to reproduce the issue: import locale locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8") a = ["A", "E", "Z", "a", "e", "?", "z"] sorted(a) sorted(a, key=locale.strxfrm) The execution on MacOsX produces: pierre:Flaubert pierre$ sw_vers -productVersion 10.10.1 pierre:Flaubert pierre$ python3 Python 3.4.2 (v3.4.2:ab2c023a9432, Oct 5 2014, 20:42:22) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import locale >>> locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8") 'fr_FR.UTF-8' >>> a = ["A", "E", "Z", "a", "e", "?", "z"] >>> sorted(a) ['A', 'E', 'Z', 'a', 'e', 'z', '?'] >>> sorted(a, key=locale.strxfrm) ['A', 'E', 'Z', 'a', 'e', 'z', '?'] >>> while it produces this on you interactive shell (python.org): In [10]: import locale In [11]: locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8") Out[11]: 'fr_FR.UTF-8' In [12]: a = ["A", "E", "Z", "a", "e", "?", "z"] In [13]: sorted(a) Out[13]: ['A', 'E', 'Z', 'a', 'e', 'z', '?'] In [14]: sorted(a, key=locale.strxfrm) Out[14]: ['a', 'A', 'e', 'E', '?', 'z', 'Z'] which is correct. ---------- messages: 2927 nosy: pnugues priority: urgent status: unread title: Sorting with locale does not work properly with Python3 on Macos _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Jan 8 16:06:58 2015 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Thu, 08 Jan 2015 15:06:58 +0000 Subject: [Tracker-discuss] [issue561] Sorting with locale does not work properly with Python3 on Macos In-Reply-To: <1420726107.29.0.866027643228.issue561@psf.upfronthosting.co.za> Message-ID: <1420729618.67.0.544162942887.issue561@psf.upfronthosting.co.za> R David Murray added the comment: This is the tracker for problems with the functioning of the bugs.python.org tracker. python bugs should be reported to the bugs.python.org tracker itself, not here. ---------- nosy: +r.david.murray priority: urgent -> wish status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 13 07:30:59 2015 From: metatracker at psf.upfronthosting.co.za (Karan Goel) Date: Tue, 13 Jan 2015 06:30:59 +0000 Subject: [Tracker-discuss] [issue556] Server error when trying to change homepage In-Reply-To: <1415622766.7.0.921930828439.issue556@psf.upfronthosting.co.za> Message-ID: <1421130659.05.0.350951373556.issue556@psf.upfronthosting.co.za> Karan Goel added the comment: Can confirm this bug. Still happens and isn't fixed. issue 458 seems to be of different nature (auth error in that, and an unknown error in this case). ---------- nosy: +karan status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From techtonik at gmail.com Sat Jan 17 14:17:30 2015 From: techtonik at gmail.com (anatoly techtonik) Date: Sat, 17 Jan 2015 16:17:30 +0300 Subject: [Tracker-discuss] mime-types on bugs.python.org Message-ID: JFYI, here is the list of mime-types on bugs.python.org Uniques ones were added before 2007. when this detector was added https://hg.python.org/tracker/python-dev/file/51dd28d02f07/detectors/no_texthtml.py import xmlrpclib roundup_server = xmlrpclib.ServerProxy('https://bugs.python.org/xmlrpc') types = roundup_server.list('file', 'type') from collections import Counter stat = Counter(types) for name, c in stat.most_common(): print "%4s %s" % (c, name) 34902 text/plain 1110 application/octet-stream 305 None 173 application/zip 147 application/x-zip-compressed 139 application/x-gzip 121 image/png 90 text/x-csrc 52 image/jpeg 45 text/x-diff 30 application/gzip 30 application/x-tar 29 text/x-log 24 application/x-bzip2 23 application/x-gzip-compressed 21 application/pkcs7-signature 16 text/html 15 application/x-compressed-tar 13 application/x-zip 13 application/x-compressed 13 application/pdf 13 image/gif 13 application/x-bzip 12 text/xml 11 application/x-shellscript 10 application/x-gtar 9 application/x-tex 9 text/x-chdr 8 text 8 message/rfc822 7 application/x-pkcs7-signature 7 image/x-png 6 video/x-dv 6 text/x-vcard 5 application/x-xz 5 application/x-tar-gz 5 application/x-sh 5 application/vnd.oasis.opendocument.text 5 text/csv 4 image/pjpeg 4 application/vnd.openxmlformats-officedocument.wordprocessingml.document 4 image/bmp 4 application/x-compress 4 application/x-download 3 3 text/prs.fallenstein.rst 3 video/quicktime 3 application/rtf 3 application/bzip2 3 text/x-tex 3 application/x-tcl 3 www/unknown 3 application/empty 3 text/x-c++src 3 application/x-tgz 3 application/x-desktop 3 application/vnd.ms-excel 3 plain/text 3 text/x-comma-separated-values 3 application/download 3 text/rtf 3 application/msword 2 application/x-x509-ca-cert 2 text/x-sh 2 text/x-python 2 application/x-stuffit 2 application/x-7z-compressed 2 text/x-c-header 2 text/x-patch 2 application/octet-stream; name="make.out" 2 application/x-msdownload 2 application/x-msi 2 audio/x-aiff 2 message/delivery-status 2 application/vnd.yahoo.widget 2 audio/basic 1 application/x-gunzip 1 application/octet-stream; 1 톐 1 application/octet-stream; name="patch" 1 application/octet-stream; name="Xcompiler-patch" 1 application/x-ns-proxy-autoconfig 1 audio/x-wav 1 text/plain; name="temp.txt" 1 text/plain; chaset=utf-8 1 application/vnd.android.package-archive 1 text/text 1 application/text 1 application/x-extension-cgi 1 application/force-download 1 application/x-lzma 1 video/dv 1 application/x-python-code 1 application/octet-stream; name="py-help.el" 1 application/x-gzip; name="set.tgz" 1 application/xml 1 text/cpp 1 application/x-octet-stream 1 /home/www/vesta/services/stamper/data/eca8875f3f165feb6342fd31d36072d3: 1 application/x-bzip-compressed-tar 1 text/english 1 application/x-troff-man 1 version=1.1.2 1 text/x-sql 1 image/svg+xml 1 application/octet-stream; name="urllib_proxies_docs.cdiff" 1 text/x-java 1 application/mbox 1 image/tiff 1 application/octet-stream; name="spam1" 1 application/octet-stream; name="bdist_rpm-patch" 1 text/x-retext-rst 1 application/rar 1 image/x-icon 1 application/x-rar-compressed 1 text/css 1 application/vnd.oasis.opendocument.spreadsheet 1 text/x-rpm-spec 1 text/plain; charset=gbk 1 application/xml-dtd 1 application/x-sharedlib 1 application/x-msdos-program 1 text/plain;charset=utf-8 1 text/x-c 1 text/x-perl 1 application/x-itunes-itlp 1 application/x-gtar-compressed 1 text/x-tcl 1 dropload/binary 1 text/patch 1 application/octet-stream; name="urllib_proxies_patch.cdiff" -- anatoly t. From metatracker at psf.upfronthosting.co.za Sun Jan 25 04:44:16 2015 From: metatracker at psf.upfronthosting.co.za (C. P. Burns) Date: Sun, 25 Jan 2015 03:44:16 +0000 Subject: [Tracker-discuss] [issue562] Gmail (google) marks registration email as spam Message-ID: <1422157456.62.0.726959967661.issue562@psf.upfronthosting.co.za> New submission from C. P. Burns: Gmail (google) marks registration emails as spam. This occurred when registering for both and . Gmail indicated they were marked as spam because "It is in violation of Google's recommended email sender guidelines. Learn more ". ---------- messages: 2930 nosy: cpburnz priority: bug status: unread title: Gmail (google) marks registration email as spam _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Jan 25 18:01:35 2015 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Sun, 25 Jan 2015 17:01:35 +0000 Subject: [Tracker-discuss] [issue562] Gmail (google) marks registration email as spam In-Reply-To: <1422157456.62.0.726959967661.issue562@psf.upfronthosting.co.za> Message-ID: <1422205295.87.0.0922033420734.issue562@psf.upfronthosting.co.za> R David Murray added the comment: Mail is consistently sent from report at bugs.python.org, always from the same IP address, 46.4.197.70. 46.4.197.70 resolves to bugs.python.org. So, we are meeting the requirements set forth in the article you link. I've asked about adding SPF records, which I don't *think* we currently publish, but per the linked doc, that shouldn't be *necessary* to satisfy google. We have a suspicion that they are marked as spam because spammers fake from addresses and send messages to the tracker, which automatically sends back the registration email (since it hasn't seen that email address before), and the from address recipient marks the message as spam...which information then makes its way into one or more pattern recognition databases. At this point I'm not sure there's much we can do about it, though I would be in favor of eliminating the auto-registration response (ie: generate a registration email only if registration is requested via the web interface, not implicitly via email). But I'm not at all sure that fixing that now would have any affect on whatever database it is that has the registration emails marked as "likely spam". If I'm right about the above, though, it means that google's bounce email is...well, lying is probably to strong a term, but misrepresenting, at least...the reason the email is being marked as spam. ---------- nosy: +r.david.murray status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Jan 26 22:51:33 2015 From: metatracker at psf.upfronthosting.co.za (Ethan Furman) Date: Mon, 26 Jan 2015 21:51:33 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date Message-ID: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> New submission from Ethan Furman: Only issues with last activity on that date are returned; issues with activity on that date and more activity on subsequent dates are not returned. I'm happy to work on a patch if somebody could point me in the right direction (or towards the correct files). ---------- messages: 2932 nosy: ethan.furman priority: bug status: unread title: activity date search does not return all issues with activity on that date _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 27 00:23:48 2015 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Mon, 26 Jan 2015 23:23:48 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422314628.11.0.827101393874.issue563@psf.upfronthosting.co.za> R David Murray added the comment: Well, the correct fix would be to change the search template so that the form says "last activity date". That field is really there to be sorted on, not searched on. ---------- nosy: +r.david.murray status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 27 00:25:26 2015 From: metatracker at psf.upfronthosting.co.za (Ethan Furman) Date: Mon, 26 Jan 2015 23:25:26 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422314726.69.0.968944636519.issue563@psf.upfronthosting.co.za> Ethan Furman added the comment: That is one possible fix -- but if it is not to be searched on, why are we allowed to enter a date? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 27 00:38:43 2015 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Mon, 26 Jan 2015 23:38:43 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422315523.58.0.394099183536.issue563@psf.upfronthosting.co.za> R David Murray added the comment: Well, it *can* be searched on, its just that it is 'last activity date' because it is really there to be sorted on. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 27 01:51:43 2015 From: metatracker at psf.upfronthosting.co.za (Ethan Furman) Date: Tue, 27 Jan 2015 00:51:43 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422319903.48.0.658824025662.issue563@psf.upfronthosting.co.za> Ethan Furman added the comment: Hmmm... okay, changing to an RFE. ;) ---------- priority: bug -> feature _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 27 02:01:31 2015 From: metatracker at psf.upfronthosting.co.za (Ethan Furman) Date: Tue, 27 Jan 2015 01:01:31 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422320491.77.0.454342348306.issue563@psf.upfronthosting.co.za> Ethan Furman added the comment: Argh. The activity date is a single field on the issue, isn't it? So the type of search I'm looking for would actually be on the messages, wouldn't it? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 27 02:44:43 2015 From: metatracker at psf.upfronthosting.co.za (Ethan Furman) Date: Tue, 27 Jan 2015 01:44:43 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422323083.82.0.847225597989.issue563@psf.upfronthosting.co.za> Ethan Furman added the comment: Okay, I think the change needed would be to match the activity date against the _msg table, and pull any items that have messages matching the date. I don't think I could even rewrite the sql for that, let alone the code to create the sql. Anybody else feel like taking on that task? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Jan 27 03:14:54 2015 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 27 Jan 2015 02:14:54 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422324894.6.0.149266443166.issue563@psf.upfronthosting.co.za> R David Murray added the comment: Since I have no need for the feature, not me :) This wouldn't really belong in the issue search page anyway, unless someone completely rewrote it. Instead you'd create a search template for msg, which could list the issue the message is linked to as part of the search results. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jan 28 12:49:01 2015 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 28 Jan 2015 11:49:01 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422445741.33.0.107537257299.issue563@psf.upfronthosting.co.za> Ezio Melotti added the comment: Are you asking for something like http://bugs.python.org/msg?%40sort0=activity&%40sortdir0=on ? ---------- nosy: +ezio.melotti _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jan 28 17:12:24 2015 From: metatracker at psf.upfronthosting.co.za (Ethan Furman) Date: Wed, 28 Jan 2015 16:12:24 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422461544.31.0.953503419297.issue563@psf.upfronthosting.co.za> Ethan Furman added the comment: No, although that may be as close as I can get. Ideally I would put a date in the activity date field, and get back a list of issues that had any activity on that date. Having looked into it further and realizing that (nearly?) every piece of information has its own activity date field I see that this is not the simple request I had imagined. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jan 28 18:53:47 2015 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 28 Jan 2015 17:53:47 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422467627.36.0.530459437356.issue563@psf.upfronthosting.co.za> Ezio Melotti added the comment: Have you tried entering a date range like the ones in the second bullet list at http://roundup.sourceforge.net/doc-1.0/user_guide.html#date-properties in the search page? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Jan 28 19:11:24 2015 From: metatracker at psf.upfronthosting.co.za (Ethan Furman) Date: Wed, 28 Jan 2015 18:11:24 +0000 Subject: [Tracker-discuss] [issue563] activity date search does not return all issues with activity on that date In-Reply-To: <1422309093.29.0.326095953743.issue563@psf.upfronthosting.co.za> Message-ID: <1422468684.56.0.112041104475.issue563@psf.upfronthosting.co.za> Ethan Furman added the comment: Just verified that a date range behaves the same on my tracker, this tracker, and the b.p.o. tracker. Note that I'm interested in the Last Activity Date field, not the Creation Date field. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Jan 31 17:23:59 2015 From: metatracker at psf.upfronthosting.co.za (Ian Kelly) Date: Sat, 31 Jan 2015 16:23:59 +0000 Subject: [Tracker-discuss] [issue564] Password reset sends new password to wrong email Message-ID: <1422721439.89.0.840459452488.issue564@psf.upfronthosting.co.za> New submission from Ian Kelly: I lost my password for bugs.python.org and tried to use the password reset tool, entering my personal email address. I received the confirmation email with the password reset link, but when I followed it, the tracker indicated that it had reset the password and sent email to a separate address, a work-related email address that I no longer have access to. No email showed up in my personal account. Instead of or in addition to the primary email address on the account, it seems to me that these emails should at minimum be sent to the email address that was used to initiate the password reset. ---------- messages: 2944 nosy: ikelly priority: bug status: unread title: Password reset sends new password to wrong email _______________________________________________________ PSF Meta Tracker _______________________________________________________