47 rows where "changetime" is on date 2012-10-15

View and edit SQL

Suggested facets: changetime, stage, component, type, version, resolution, owner, easy, has_patch, needs_better_patch, needs_docs, ui_ux, created (date), last_pulled_from_trac (date)

changetime (date)

  • 2012-10-15 · 47
id ▼ created changetime last_pulled_from_trac stage status component type severity version resolution summary description owner reporter keywords easy has_patch needs_better_patch needs_tests needs_docs ui_ux
6648 2008-02-22 21:07:15 2012-10-15 03:58:55 2019-06-24 01:26:28.459673 Accepted closed Core (Other) Cleanup/optimization Normal master worksforme random seed identical among preforked FastCGI instances While writing a basic captcha module, I was encountering a lot of duplicate strings of "random" text that I could not explain. Then I remembered seeing this comment on a separate session issue: http://code.djangoproject.com/ticket/1180#comment:20 Based on that info, I setup some extra logging, and it did appear that each of my FastCGI threads were producing identical random values. I was specifically using a call like this: random.choice('ABCDEFGHIJKLMNOPQRSTUVWXYZ'). It's possible other random methods are not affected, I was only interested in that one. It seems the random seed is set prior to the fork, and each forked process thereafter produces identical random output as a result. In my setup, I run manage.py with method=prefork, runfcgi, and a static number of processes. This is on an Ubuntu Gutsy AMD 64-bit (on Xen) with Python 2.5.1. I'm currently running against SVN Django, revision 7049. My workaround was to add a middleware class with an init function that sets the random seed. This gets called at "startup" in each of the new FCGI processes, giving them unique random output. Obviously not ideal, but it gets the job done in my case. {{{ import logging, logging.config import os, random, time class ReseedRandom(object): def __init__(self): logging.debug("setting new random seed for this process") random.seed("%d%s" % (os.getpid(), time.ctime())) }}} It would be much cleaner if the manage.py FCGI launcher could seed its random number generator AFTER the fork occurs, rather than before (or not at all, as the case may be). nobody nezroy@gmail.com random seed fastcgi fcgi prefork 0 1 0 0 0 0
7023 2008-04-15 02:24:41 2012-10-15 21:16:47 2019-06-24 01:30:37.616079 Accepted closed contrib.localflavor New feature Normal master invalid Improve validation and add extra attributes to PLNationalIdentificationNumberField Attached patch includes: * `PLNationalIdentificationNumberField`: * gender recognition (`PLNationalIdentificationNumberField.gender`), * birthday calculation (`PLNationalIdentificationNumberField.birthday`), * birthday-based validation, * tests, * Polish locale. nobody Piotr Lewandowski <django@icomputing.pl> pl, polish, pesel, localflavorsplit 0 1 1 0 0 0
7463 2008-06-16 10:05:25 2012-10-15 21:16:47 2019-06-24 01:35:19.888636 Accepted closed contrib.localflavor New feature Normal master invalid alternate phone regex for US flavor forms A growing subset of US organizations are starting to allow a slash as an area code delimiter ({{{xxx/xxx-xxxx}}}). Modulo tests by the core Django team, this patch enables that. nobody kevin@caktusgroup.com localflavor, forms, areacode, delimiter, localflavorsplit 0 1 1 0 0 0
7994 2008-07-27 20:38:54 2012-10-15 21:16:47 2019-06-24 01:41:04.361525 Accepted closed contrib.localflavor New feature Normal master invalid Dutch Bank Account Number Field I created a Dutch Bank Account Number Field to the Dutch localflavor and also included tests. nobody Rudolph localflavorsplit 0 1 1 0 0 0
8273 2008-08-13 02:13:52 2012-10-15 19:37:28 2019-06-24 01:44:13.941678 Accepted closed contrib.localflavor Cleanup/optimization Normal master wontfix Reduce amount of redundant code in django.contrib.localflavor There is a plenty of somehow redundant code in {{{django.contrib.localflavor}}} which leads to potentially more bugs and what is quite inconvenient -- many translation strings. I would like to propose the patch that handles all fields with a checksum verification. Pros: * a lot fewer translation strings, which is more consistent and means less work when translating Django to 50 languages, * DRY compatible (and all benefits that it implies). Cons: * backwards incompatible, * new code may contain bugs (although all tests were OK). I volunteer for further modifications of {{{django.contrib.localflavor}}} code to use {{{NumberWithChecksumField}}} if this patch is accepted. nobody Piotr Lewandowski <django@icomputing.pl>   0 1 1 0 0 0
8798 2008-09-02 15:44:42 2012-10-15 21:16:47 2019-06-24 01:50:46.335620 Accepted closed contrib.localflavor New feature Normal master invalid Add DEPhoneNumberField to German localflavor module This ticket tries to add a {{{DEPhoneNumberField}}} class to the German localflavor module. There are several valid standards in Germany: DIN 5008, E.123 and an informal format which have national and international notations. More information: http://de.wikipedia.org/wiki/Rufnummer#Schreibweisen jezdez jezdez locale, localflavor, german, phone, number, localflavorsplit 0 1 0 0 0 1
8934 2008-09-07 23:36:58 2012-10-15 21:16:47 2019-06-24 01:52:14.132591 Accepted closed contrib.localflavor New feature Normal 1.0 invalid Add ARPhoneNumberField to Argentina localflavor module Add a ARPhoneNumberField class to Argentina localflavor module. nobody fperetti localflavorsplit 0 1 1 1 1 0
9622 2008-11-18 14:18:57 2012-10-15 21:18:51 2019-06-24 01:59:36.642874 Accepted closed contrib.localflavor New feature Normal   invalid Bulgarian Local Flavor The attached .tar.gz file contains the following structure: ontrib/localflavor/bg/ contrib/localflavor/bg/ contrib/localflavor/bg/bg_cities.py contrib/localflavor/bg/__init__.py contrib/localflavor/bg/forms.py The forms.py file contains the following form fields, with proper validation: * BGPostalCodeField -- A Bulgarian postal code field * BGEGNField -- A Bulgarian EGN (Social Security) number * BGPhoneNumberField -- A Bulgarian phone number field * BGCountySelect -- A Select widget that uses a list of Bulgarian counties as its choices Additionally, the bg_cities.py file contains: * BG_COUNTIES -- a choices tuple * BG_CITIES -- a tuple of tuples containg information about all Bulgarian cities, including city name, phone code, postal code, and the abbreviation used on license plate numbers for that city * A helper function get_by_city(city, attribute), which returns an attribute by city name, using the BG_CITIES tuple ~ Jordan Dimov <jdimov@a115.bg> nobody jdimov bulgarian, localflavorsplit 0 1 1 1 1 0
9697 2008-11-25 23:35:54 2012-10-15 21:16:47 2019-06-24 02:00:25.504623 Accepted closed contrib.localflavor New feature Normal 1.0 invalid Adding the Australian Tax File Number field validator This patch adds the Australian Tax File Number field validator to the Australian local flavour. nobody PaulWay australian, tax, file, number, localflavorsplit 0 1 1 1 1 0
10087 2009-01-21 16:01:56 2012-10-15 21:16:47 2019-06-24 02:04:38.585788 Accepted closed contrib.localflavor New feature Normal 1.0 invalid Missing models.py in django.contrib.localflavor.fr To use french flavored PhoneNumberField in models, one need the models.py file like in django.contrib.localflavor.us. Here's the diff to add it. nobody lstep localflavorsplit 0 1 1 0 1 0
10203 2009-02-06 21:31:28 2012-10-15 21:18:51 2019-06-24 02:05:54.275006 Accepted closed contrib.localflavor New feature Normal 1.0 invalid Nicaragua LocalFlavor I made the local flavor for nicaragua including Departament Select, Cedula number and phone number input. Check the attachment for the svn diff. Any correction just let me know. nobody fitoria Nicaragua, localflavor, localflavorsplit 0 1 1 0 0 0
10204 2009-02-06 21:55:39 2012-10-15 21:16:47 2019-06-24 02:05:54.962322 Accepted closed contrib.localflavor Bug Normal master invalid Validation fails in spanish localflavor ESIdentityCardNumberField The spanish localflavor ESIdentityCardNumberField accepts the syntax of the spanish official cards type, but due the new revision of the law (http://www.boe.es/boe/dias/2008/07/15/pdfs/A30880-30880.pdf), it need to be updated. meaksh meaksh ESIdentityCardNumberField, NIE, localflavorsplit 0 1 1 0 0 0
10456 2009-03-10 18:53:28 2012-10-15 21:16:47 2019-06-24 02:08:38.666421 Accepted closed contrib.localflavor Bug Normal master invalid Canada localflavor improvements/fixes The Canadian localflavor package uses incorrect postal abbreviations for Newfoundland (NF, should be NL) and the Yukon (YK, should be YT). Previous bugs: #10365, #8478. There's a discussion in #10365 about the merits of changing the abbreviation and potentially breaking existing data. It's a tough question, since the abbreviation isn't simply an internal representation: it's a very common use case to use the postal abbreviation in addresses, and so the current version of ca.localflavor will generate incorrect output. This doesn't help with the issue of existing data, though, and I'm not quite sure what to do there. Two patches are attached. One updates to the correct abbreviations. The other maintains the current, incorrect abbreviations but normalizes the correct abbreviations (NL, YT) to the incorrect ones (NF, YK) instead of rejecting them, as the current version does. Both patches also include some other fixes and improvements: - More abbreviations and misspellings are accepted and normalized for province names - French province names are now accepted - CAPostalCodeField accepts and normalizes common postal code formats ('h4u5h7' -> 'H4U 5H7') nobody mmulley localflavor, ca, localflavorsplit 0 1 1 0 0 0
10895 2009-04-22 20:16:36 2012-10-15 21:16:47 2019-06-24 02:13:26.038069 Accepted closed contrib.localflavor Bug Normal master invalid Improvements in BRCPFField and BRCNPJField in localflavor.br.forms When using the fields `BRCPFField` and `BRCNPJField` in `django.contrib.localflavor.br.forms` I missed a uniform return format in the cleaned value of these fields, as they validate formatted and digits only inputs and the cleaned data preserves the same format as the entered value. If you're not enforcing a particular format with JavaScript, you may end up with a non standardized values on the database. Ex.: For `BRCPFField `the values cleaned can be '999.999.999-99', '99999999999', '999999999-99', etc... My suggestion is to keep the diversity of valid input formats, but provide a way to uniform the format of the cleaned value. The implementation consists of adding two optional keyword arguments: * `always_return_formatted`: a boolean which indicates if the cleaned value must always be in a particular format, the default is `False` to prevent unexpected behavior to the current users of this `FormField` class. * `return_format`: a string to format the output, defaults to '%s.%s.%s-%s' in `BRCPFField` In addition to these, I've changed the parent class of `BRCNPJField` from `Field` to `CharField` to take advantage of `max_length` and `min_length` validators. Tests for these features included and fixed some errors in previous doctest that were expecting a unicode string. waa luizvital localflavor, brcpffield, brcpnjfield, br, localflavor, localflavorsplit 0 1 1 0 0 0
10936 2009-04-27 15:51:01 2012-10-15 23:56:53 2019-06-24 02:13:55.863345 Accepted closed Documentation Cleanup/optimization Normal master fixed Detailed instructions for getting Django and MySQL and MySQLdb working on various OS X versions Getting MySQLdb working on OS X is an absolute nightmare, which has resulted in a flurry of blog posts such as the following: http://www.keningle.com/?p=11 This really shouldn't be our problem since it's not a Django issue - but OS X / MySQL are an extremely common development platform for our user base and it makes a really bad impression if people can't get up and running with this (especially since PHP + MySQL on OS X works pretty much out of the box). I just had to talk someone through this over the phone and it was a bit embarrassing having to admit how miserable the MySQL / OS X installation experience for Django actually is. We could do this as part of a larger project to bulk out our installation instructions for other platforms as well. nobody simon mysqldb 0 1 0 0 0 0
11002 2009-05-04 14:45:28 2012-10-15 18:20:47 2019-06-24 02:14:37.803956 Accepted closed GIS New feature Normal master wontfix Databrowse does not have map widgets for GIS fields. Databrowse should have a way to configure a map widget for GIS fields instead of just showing the WKT jbronn ingenieroariel databrowse 0 0 0 0 0 0
11217 2009-05-27 14:30:11 2012-10-15 21:18:51 2019-06-24 02:16:55.417687 Accepted closed contrib.localflavor New feature Normal   invalid Add Hungarian localflavor The attached patch adds 4 localflavor classes for Hungary: * HUIBANField * HUPhoneNumberField * HUVatNumberField * HUZipCodeField moreover, it add a localflavor.generic.util.validate_iban method. The code for this latter comes from localflavor.ro.forms.ROIBANField. nobody nagyv localflavorsplit 0 1 0 1 0 0
11517 2009-07-21 06:42:36 2012-10-15 21:16:47 2019-06-24 02:20:08.243801 Accepted closed contrib.localflavor New feature Normal master invalid Chilean(cl) localflavor car plate field. Chilean car plate field for localflavor, support old and new type. Patch contains CLPatenteField. nobody alej0 chile, patente, car, plate, field, localflavorsplit 0 1 0 1 1 0
11537 2009-07-23 18:42:22 2012-10-15 21:16:47 2019-06-24 02:20:21.053358 Accepted closed contrib.localflavor Bug Normal master invalid localflavor for india's state choices are not tuples See: http://code.djangoproject.com/browser/django/trunk/django/contrib/localflavor/in_/in_states.py The STATE_CHOICES should be an iterable of tuples to be consistent with the rest of localflavor. lars zbyte64 localflavorsplit 0 1 1 0 0 0
11626 2009-08-03 07:22:50 2012-10-15 21:18:51 2019-06-24 02:21:17.404519 Accepted closed contrib.localflavor New feature Normal   invalid Add Malaysian (my) localflavour Patch to add Malaysian localflavor. Contains form and model fields for Malaysian Identification Number, postcode, phone number and states. Only tests for form fields are included (''help:'' not sure where to put model field tests for localflavors). nobody zaim localflavor, malaysia, my, localflavorsplit 0 1 1 1 0 0
11768 2009-08-22 03:59:14 2012-10-15 21:18:51 2019-06-24 02:22:50.078248 Accepted closed contrib.localflavor New feature Normal 1.1 invalid Localflavor for Venezuela Here is some code for localflavor.ve Includes: State Selection Validation for Postal Code Validation for CI (Identity Document) Validation for RIF (Tax Id) nobody marcoslhc Venezuela, localflavorsplit 0 1 1 1 0 0
12710 2010-01-27 18:26:50 2012-10-15 21:18:51 2019-06-24 02:33:02.882302 Accepted closed contrib.localflavor New feature Normal   invalid South Korea (KR) localflavor package Patch to add South Korea localflavor. Contains form for South Korea post code , phone number , Resident Registration Number and SpecialCityAndProvinceSelect nobody darjeeling localflavor, south, korea, localflavorsplit 0 1 0 1 1 0
13050 2010-03-07 15:15:53 2012-10-15 21:18:51 2019-06-24 02:36:47.863055 Accepted closed contrib.localflavor New feature Normal master invalid localflavor contrib app for Bangladesh (bd) This is a django.contrib.localflavor.bd app for Bangladesh. It consists of five special form fields for Bangladesh Post code, Phone numbers, Divisions, Districts and Upazilas/Thanas. nobody nsmgr8 localflavor, bd, Bangladesh, form, fields, localflavorsplit 0 0 0 1 0 0
13473 2010-05-05 03:42:01 2012-10-15 21:16:47 2019-06-24 02:41:28.108402 Accepted closed contrib.localflavor New feature Normal master invalid BRCPFField and BRCNPJField updates for localflavor.br In Django 1.1 (or 1.0) are added two fields in localflavor.br.forms for CPF and CNPJ, but this ones not have a similar o models and not normalize data to save in database (look #10895). I started some changes to have model fields, number generators (useful for tests), one 'type' and integration of model fields to form fields for CPF and CNPJ. I adding here a diff of my initial work and a link to my repo at github. chronos chronos CPF, CNPJ, localflavorsplit 0 1 0 0 1 0
13645 2010-05-27 23:17:52 2012-10-15 19:47:50 2019-06-24 02:43:18.795721 Accepted closed contrib.localflavor New feature Normal 1.2 duplicate The “local flavor” add-ons for Turkey i wanna add Turkish local flavor but i don't know where to start. nobody rkirmizi turkish local flavor 0 0 0 0 0 0
13733 2010-06-10 07:08:46 2012-10-15 21:18:51 2019-06-24 02:44:16.176591 Accepted closed contrib.localflavor New feature Normal   invalid New Zealand localflavor There should be some localflavor for New Zealanders! nobody schinckel localflavorsplit 0 1 1 0 0 0
13838 2010-06-26 06:04:41 2012-10-15 21:16:47 2019-06-24 02:45:23.930857 Accepted closed contrib.localflavor New feature Normal 1.2 invalid Enhancements to Japanese localflavor module This is a patch for the Japanese localflavor module that fixes a long standing problem with the ordering of the JPPrefectureSelect widget and adds new form fields for doing common validation on Japanese text. nobody IanLewis localflavorsplit 0 1 1 1 1 0
14015 2010-07-28 08:07:41 2012-10-15 21:16:47 2019-06-24 02:47:24.055238 Accepted closed contrib.localflavor New feature Normal 1.2 invalid django.contrib.localflavor.it added italian phone number validation Hi to all, I found myself in need of an Italian phone numbers validator, so I wrote it as a localflavor element, and now I'm sharing it with the community of Django. The validation process is quite simple but yet very functional. The (eventual) international prefix (both +39 or 0039) is stripped from the number entered (something like 0039 010 1234567 -> 010 1234567). The local prefix (in example 010, the prefix for Genoa) is checked against a list of valid prefixes (both fixed line or mobile), and if the number meet all the requirements (containing only number, having a prefix between 2 and 4 digits, and a number itself between 5 and 8 digits...) is returned as a cleaned value. Hope of being of some Help, Greetings, Andrea nobody VoodooChile django.contrib.localflavor.it, ITPhoneNumberField, form, phone, number, validation, localflavorsplit 0 1 1 1 1 0
14282 2010-09-13 03:05:58 2012-10-15 21:18:51 2019-06-24 02:50:14.346311 Accepted closed contrib.localflavor New feature Normal 1.2 invalid Add Guatemala to Localflavors Hi, attached is the patch for guatemalan form helpers. nobody dmonroy Guatemalan, localflavorsplit 0 1 0 1 1 0
14308 2010-09-18 15:44:08 2012-10-15 21:16:47 2019-06-24 02:50:32.286166 Accepted closed contrib.localflavor New feature Normal 1.2 invalid Adding some fields to the Mexican local flavor. Fields like RFC, CURP and the ZIP Code are in this file attachment and in the code block here down. {{{ """ MX-specific Form helpers """ from django.forms.fields import RegexField class MXRFCField(RegexField): """ A field that accepts a 'classic' MX RFC (Registro Federal de Contribuyentes). More info about this: http://es.wikipedia.org/wiki/Registo_Federal_de_Contribuyentes_(M%C3%A9xico) """ def __init__(self, *args, **kwargs): super(MXRFCField, self).__init__(r'^[a-zA-Z]{3}[a-zA-Z\d]?(\d\d)(0[\d]{1}|1[0-2]{1})(0[\d]{1}|[1-2]{1}\d|3[0-1])[a-zA-Z\d]{3}$', *args, **kwargs) def clean(self, value): value = super(MXRFCField, self).clean(value) return value.upper() class MXCURPField(RegexField): """ A field that accepts a 'classic' MX CURP (Clave Unica de Registro de Poblacion). More info about this: http://es.wikipedia.org/wiki/Clave_%C3%9Anica_de_Registro_de_Poblaci%C3%B3n_%28M%C3%A9xico%29 """ def __init__(self, *args, **kwargs): super(MXCURPField, self).__init__(r'^[a-zA-Z]{4}(\d\d)(0[\d]{1}|1[0-2]{1})(0[\d]{1}|[1-2]{1}\d|3[0-1])([hmHM]{1})[a-zA-Z]{5}\d{2}$', *args, **kwargs) def clean(self, value): value = super(MXCURPField, self).clean(value) return value.upper() class MXZIPCodeField(RegexField): """ A field that accepts a 'classic' MX ZIP Code. More info about this: http://es.wikipedia.org/wiki/C%C3%B3digo_postal_mexicano """ def __init__(self, *args, **kwargs): super(MXZIPCodeField, self).__init__(r'^(\d){5}$', *args, **kwargs) }}} Thanks. nobody srpoder Mexican, Fields, localflavorsplit 0 1 1 1 0 0
14400 2010-10-05 17:48:20 2012-10-15 21:18:51 2019-06-24 02:51:31.467218 Accepted closed contrib.localflavor New feature Normal master invalid Latvian localflavor latvian local flavor, with identity code, postal code and phone number phone fields nobody krikulis localflavorsplit 0 1 1 0 0 0
15753 2011-04-04 16:46:18 2012-10-15 19:12:34 2019-06-24 03:06:10.339970 Accepted closed contrib.sitemaps Bug Normal master fixed test_simple_sitemap fails after executing test_requestsite_sitemap when Sites app and FetchFromCacheMiddleware are installed. test_simple_sitemap fails after executing test_requestsite_sitemap when Sites app and FetchFromCacheMiddleware are installed. The error: {{{ ====================================================================== FAIL: test_simple_sitemap (django.contrib.sitemaps.tests.basic.SitemapTests) A simple sitemap can be rendered ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/Django-1.3-py2.6.egg/django/contrib/sitemaps/tests/basic.py", line 70, in test_simple_sitemap """ % (self.base_url, date.today().strftime('%Y-%m-%d'))) AssertionError: '<?xml version="1.0" encoding="UTF-8"?>\n<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">\n<url><loc>http://testserver/location/</loc><lastmod>2011-04-04</lastmod><changefreq>never</changefreq><priority>0.5</priority></url>\n</urlset>\n' != '<?xml version="1.0" encoding="UTF-8"?>\n<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">\n<url><loc>http://example.com/location/</loc><lastmod>2011-04-04</lastmod><changefreq>never</changefreq><priority>0.5</priority></url>\n</urlset>\n' }}} The way to reproduce it: 1. Use Sites app in your project 2. Use FetchFromCacheMiddleware middleware in your project 3. Run the sitemaps.SitemapTests suite The code that triggers the problem is this [http://code.djangoproject.com/browser/django/trunk/django/contrib/sitemaps/tests/basic.py#L144] {{{ # Which does that - setting the Site app as not installed and requesting the url Site._meta.installed = False response = self.client.get('/simple/sitemap.xml') }}} If I execute the test case separate (./manage.py test sitemaps.SitemapTests.test_simple_sitemap) no error is observed, but executing the whole test suite leads to error in test_simple_sitemap which is executed right after the test_requestsite_sitemap. If I comment out the test_requestsite_sitemap, no problem is observed. If I '''don't use (comment out) FetchFromCacheMiddle… nobody lucho test 0 1 0 0 0 0
17355 2011-12-06 20:36:47 2012-10-15 21:16:47 2019-06-24 03:23:37.422537 Accepted closed contrib.localflavor Bug Normal 1.3 invalid Perform proper NANP validation in US/CA localflavor phone number Patch attached. http://en.wikipedia.org/wiki/North_American_Numbering_Plan Long story short: 1-NPA-NXX-XXXX * NPA: 3 digits, 1st is [2-9], 2nd/3rd are [0-9]. 2 and 3 cannot both be '1'. * NXX: 3 digits, 1st is [2-9], 2nd/3rd are [0-9]. 2 and 3 cannot both be '1'. * XXXX: 4 digits, no restrictions. Former code allowed any digit in all locations, meaning the following bogus phone numbers (now in tests as invalid) were accepted: {{{ '023-234-5678' '123-234-5678' '323-134-5678' '312-034-5678' '311-134-5678' '312-211-5678' }}} nobody toofishes areacode, nanp, localflavorsplit 1 1 0 0 0 0
17591 2012-01-25 17:27:10 2012-10-15 21:16:47 2019-06-24 03:26:08.080747 Accepted closed contrib.localflavor Bug Normal 1.3 invalid USSocialSecurityNumberField doesn't validate the same when entered without hypens In the us localflavor USSocialSecurityNumberField, if you enter an SSN without hyphens, the 'Woolworth' validations aren't run properly because they're explicity '078-05-1120' and '219-009-9999' instead of checking against the parts. I refactored the field and created a patch that fixes it, plus added much better tests (in my opinion... added a test for each scenario). Lastly, sometimes a user might NOT want to force the output to xxx-xx-xxxx. It might be useful to just leave it without hyphens. (in my case, need to pass ssn to a credit report service and will never need the dashes and I don't want to strip them out every time.) So, I added an optional keyword argument 'no_hyphen' to the ssn field which just forces the output to not have hyphens. Please include or give feedback on the patch. Thanks! nobody aaron.l.madison@gmail.com localflavor, ussocialsecuritynumberfield, localflavorsplit 1 1 1 0 1 0
17614 2012-01-30 13:40:50 2012-10-15 21:16:47 2019-06-24 03:26:22.700062 Design decision needed closed contrib.localflavor New feature Normal 1.3 invalid Fields for django.contrib.localflavor.ar I attached a models.py file to add in django.contrib.localflavor.ar This file has the same Fields as forms.py but it's to use in models. nobody croldan fields, models, localflavor, argentina, localflavorsplit 0 1 0 1 1 0
17632 2012-02-03 09:01:58 2012-10-15 19:53:57 2019-06-24 03:26:34.105163 Accepted closed contrib.localflavor New feature Normal 1.3 wontfix new filter for localflavor 'The Netherlands' I've created a small filter that can be used in the same way as 'pluralize'. It basically adds 'en' (most common pluralized word in Dutch) when used. {{{#!python from django import template from django.template.defaultfilters import stringfilter register = template.Library() @register.filter def meervoud(value, arg=u'en'): if not u',' in arg: arg = u',' + arg bits = arg.split(u',') if len(bits) > 2: return u'' singular_suffix, plural_suffix = bits[:2] try: if int(value) != 1: return plural_suffix except ValueError: # Invalid string that's not a number. pass except TypeError: # Value isn't a string or a number; maybe it's a list? try: if len(value) != 1: return plural_suffix except TypeError: # len() of unsized object. pass return singular_suffix }}} nobody lkeijser   0 0 0 1 1 0
18337 2012-05-17 23:10:56 2012-10-15 00:02:54 2019-06-24 03:34:11.751485 Design decision needed closed Forms New feature Normal 1.3 wontfix django.forms.BoundField should be injectable within django.forms.Form I would like to create the following html from a single reusable field {{{ <div class="contactnumber colourless" id="id_friends_parent"> <input type="checkbox" name="friends" id="id_friends"> <label for="id_friends">Friends (156)</label> </div> <script type="text/javascript"> $('#id_friends').click(function() { $('#id_friends_parent').removeClass('colourless'); if (this.checked) { console.log('checked'); } else { console.log('not checked');$('#id_friends_parent').addClass('colourless'); } }); </script> }}} In order to keep the label html in the BoundField and the widget html in the widget and to allow a mechanism for adding wrapping html to a field widget it would seem elegant to allow access to BoundField by making BoundField an overridable property in the django.forms.BaseForm class in the same way the widget property is overridable in the Field class. nobody eamonnfaherty   0 1 0 0 0 0
18536 2012-06-28 15:31:21 2012-10-15 21:16:47 2019-06-24 03:36:22.035090 Accepted closed contrib.localflavor Bug Normal master invalid BRPhoneNumberField: Telephone numbers with area code 11 must start with an extra 9 digit Until last year all telephone numbers in Brazil should have had the format XX-XXXX-XXXX but from now on all phone numbers starting with area code 11 must have the format 11-9XXXX-XXXX. All the other area codes will main the previous mask. All production instances using this form field are currently broken. Official announcement (in pt-br): http://www.anatel.gov.br/Portal/exibirPortalNivelDois.do?acao=&codItemCanal=1722&codigoVisao=4&nomeVisao=Cidad seocam seocam localflavorsplit 0 1 0 0 0 0
18715 2012-08-04 20:25:38 2012-10-15 23:53:18 2019-06-24 03:38:16.382478 Accepted closed Documentation Cleanup/optimization Normal 1.4 fixed Tutorial Page 3 Refactor * URL definitions * Text cleanup * Implementation of Class based views pydanny pydanny   0 1 0 0 0 0
18775 2012-08-16 11:10:26 2012-10-15 21:16:47 2019-06-24 03:38:54.799774 Unreviewed closed contrib.localflavor Bug Normal master invalid ROPhoneNumberField does not support several Romanian phone number formats The {{{ROPhoneNumberField}}} form field only supports 10 digit phone numbers. It does not accept valid formats like the short national phone numbers (3 or 6 digits), or geographic short numbers (7 digits). danniel danniel romanian, phone, field, localflavorsplit 0 1 0 0 0 0
18792 2012-08-18 17:38:46 2012-10-15 21:18:51 2019-06-24 03:39:05.842632 Design decision needed closed contrib.localflavor New feature Normal master invalid localflavor for Iranian users Recently i decide to add some of my local related codes to django, like: form and model fields for Jalali calender, National ID Number, phone number fields, etc, here is my current code: https://github.com/lxsameer/django I'll do a pull request as soon as my work done. nobody lxsameer localflavor, localflavorsplit 0 0 0 0 0 0
18910 2012-09-06 07:57:37 2012-10-15 21:16:47 2019-06-24 03:40:20.918290 Unreviewed closed contrib.localflavor Bug Normal 1.4 invalid Russian phone numbers may be validated improperly The regex in django/contrib/localflavor/ru/forms.py should be tested. phone_digits_re regex looks a bit improper. Working on this ticket in my Github fork, will issue a PR when complete. nobody kix validation, forms, localflavorsplit 0 0 0 1 0 0
19037 2012-09-28 12:54:21 2012-10-15 21:18:51 2019-06-24 03:41:43.904850 Unreviewed closed contrib.localflavor New feature Normal 1.4 invalid Add Singapore (SG) local flavour Add local flavour for SG phone numbers, postal codes, NRIC numbers and FIN numbers. yarbelk yarbelk localflavorsplit 1 0 0 0 0 0
19047 2012-10-01 08:15:39 2012-10-15 21:52:58 2019-06-24 03:41:50.448406 Unreviewed closed contrib.admin Bug Normal 1.4 duplicate FilteredSelectMultiple gets cleared when using back button In the admin all fields that use a FilteredSelectMultiple will be cleared if the user leaves the page and then returns via the back button in the browser. The reason seems to be that the FilteredSelectMultiple widget removes all selected items from the original select widget and moves them to another select widget. This confuses the browser about which items were selected. The attached patch works around this by setting all items that were originally selected by default as selected. Then at least the widget gets back to the state it had on initial page load, though any changes the user may have done before leaving the page will not be kept so there's probably a better way to solve it. nobody olofsj@gmail.com   0 1 0 0 0 1
19116 2012-10-12 07:28:49 2012-10-15 08:58:02 2019-06-24 03:42:35.594976 Unreviewed closed contrib.admindocs Uncategorized Normal 1.4 invalid documentation models skips some methods Admin docs are brilliant and the documentation at https://docs.djangoproject.com/en/dev/ref/contrib/admin/admindocs/#model-reference optimistically says "The models section of the admindocs page describes each model in the system along with all the fields and methods available on it." In fact it skips methods unless they have exactly one argument. This bothers me because I sometimes want model methods to have additional args. It would be better to permit any number of args. In contrib/admindocs/views.py at the end of line 235 if one adjusts {{{ == 1 }}} to {{{ > 0 }}} it reveals the skipped methods with no apparent side effects. There must be a reason it was set this way but maybe it is no longer an issue. Here is the patch: {{{ +++ contrib/admindocs/views.py Fri Oct 12 16:31:45 2012 @@ -232,7 +232,7 @@ # Gather model methods. for func_name, func in model.__dict__.items(): - if (inspect.isfunction(func) and len(inspect.getargspec(func)[0]) == 1): + if (inspect.isfunction(func) and len(inspect.getargspec(func)[0]) > 0): try: for exclude in MODEL_METHODS_EXCLUDE: if func_name.startswith(exclude): }}} If this patch is accepted, it makes the app match the documentation so no change to the docs would be required. nobody miked@dewhirst.com.au skip methods 1 1 1 0 0 0
19122 2012-10-12 18:27:28 2012-10-15 18:21:11 2019-06-24 03:42:39.413576 Unreviewed closed Uncategorized New feature Normal 1.4 needsinfo Allow .warning and .error classes on more attributes in base.py In https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.list_display there's an example: {{{ class Person(models.Model): ... def colored_name(self): return '<span style="color: #%s;">%s %s</span>' % (self.color_code, self.first_name, self.last_name) colored_name.allow_tags = True class PersonAdmin(admin.ModelAdmin): list_display = ('first_name', 'last_name', 'colored_name') }}} This sort of thing could be really useful for reporting potential problems in the admin, both in list views and with readonly_fields, if it were possible to use classes that already exist in base.css for errors and warnings: https://github.com/django/django/blob/master/django/contrib/admin/static/admin/css/base.css#L524 for some other HTML attributes as well (<span> for example). At present the Django admin does very well at informing the user of errors when something is saved in the admin. With a bit of effort it's quite easy to provide warnings too. Being able to make use of classes for warnings and errors would make it easier to give information to the user about problematic conditions that already exist through the standard Django admin. Does this seem like a good idea? nobody EvilDMP   0 0 0 0 0 0
19129 2012-10-15 21:14:53 2012-10-15 23:06:35 2019-06-24 03:42:43.829627 Unreviewed closed Uncategorized Uncategorized Normal 1.4 invalid Please add my feed to Community blog posts feed Hi. My name is Alex Clark. I am a Python Web Developer; I blog regularly about Mozilla, Plone, Python and would like to start blogging about Django. Is this the right place to ask? If so, please add: - http://blog.aclark.net/feeds/Django.atom.xml The content will, at least initially, be about my current Django project involving PCI compliance: - https://github.com/aclark4life/django-pci-auth Thanks, Alex nobody aclark@aclark.net   0 0 0 0 0 0

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE "tickets_full" (
        id int primary key,
        created datetime,
        changetime datetime,
        last_pulled_from_trac datetime,
        stage text,
        status text,
        component text,
        type text,
        severity text,
        version text,
        resolution text,
        summary text,
        description text,
        owner text,
        reporter text,
        keywords text,
        easy boolean,
        has_patch boolean,
        needs_better_patch boolean,
        needs_tests boolean,
        needs_docs boolean,
        ui_ux boolean