Re: RFC: "UPSERT" in PostgreSQL

Hi Peter, Thanks for asking! On Sunday 28 September 2014 02:01:59 Peter Geoghegan wrote: > > * Would you consider the syntax that I've proposed a good one? > Looks pretty reasonable. > * If it was available, would you use it in future versions of Django? > Do you think the plugins ecosystem

Migration challenges

Hi all, I gave a talk to a local user-group about the migrations in 1.7, and some people in the audience raised things they would like to be able to do, and are not supported by the current framework; thought it would be nice to bring them here. Two issues were about handling migrations at

Re: squashmigrations missing a simple optimization?

Replying to myself: On Sunday 21 September 2014 20:59:46 Shai Berger wrote: > Hi, > > I'm looking into the details of migrations a little, and I ran into this > issue. > > I have two migrations: The first creates a model, the second adds another > model and a field to

squashmigrations missing a simple optimization?

Hi, I'm looking into the details of migrations a little, and I ran into this issue. I have two migrations: The first creates a model, the second adds another model and a field to the first model. I'd expect squashmigrations to patch the AddField into the first CreateModel, but it finds "No

Bug#761252: Fixed upstream

reopen 761252 thanks I hadn't realized that having a Done entry means the bug is closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761252: Fixed upstream

reopen 761252 thanks I hadn't realized that having a Done entry means the bug is closed. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1486807.uGMhAGcoMy@deblack

Bug#761252: Fixed upstream

tag 761252 fixed-upstream thanks Hi, The upstream bug has now been fixed. Is there anything I can do to help get the fix into Sid? For me, this problem has turned kmail in sid from barely-usable to completely-useless. Thanks, Shai. -- To UNSUBSCRIBE, email to

Bug#761252: Fixed upstream

tag 761252 fixed-upstream thanks Hi, The upstream bug has now been fixed. Is there anything I can do to help get the fix into Sid? For me, this problem has turned kmail in sid from barely-usable to completely-useless. Thanks, Shai. -- To UNSUBSCRIBE, email to

Bug#761252: kmail: Some details please -- same problem encountered

Package: kmail Version: 4:4.14.0-1 Followup-For: Bug #761252 I wonder what the original reporter meant by problem is elsewhere, and whether an upstream bug was filed; I couldn't find one. Anyway, as far as I can see, the problem is live and well: Filter processing fails to read the List-Id

Bug#761252: kmail: Some details please -- same problem encountered

Package: kmail Version: 4:4.14.0-1 Followup-For: Bug #761252 I wonder what the original reporter meant by problem is elsewhere, and whether an upstream bug was filed; I couldn't find one. Anyway, as far as I can see, the problem is live and well: Filter processing fails to read the List-Id

Re: Two proposals for the Django Code of Conduct.

Ben, Two points: A) Your description of the threat-of-use-of-CoC incident, which appears to be quite central to your argument (as a piece of evidence), is, as far as I can see, inaccurate. The person who was threatened had started out reasonable, but later made several disrespectful and

Re: @load_fixture annotation for test cases.

On Tuesday 02 September 2014 15:27:53 Josh Smeaton wrote: > > As far as I'm concerned, using fixtures is the wrong way to populate data > for tests. You're much better off creating the objects you need for each > test within the test, or creating them directly inside the setUp method. +1. > You

Setting dictionaries (was Re: integrating django-secure)

This thread has had very little to do with django-secure for some time... On Sunday 31 August 2014 18:07:04 Carl Meyer wrote: > > In the case of the email settings, I think introducing a deprecation > that requires people to update their settings files, for zero gain in > capability, is a much

Re: manage.py migrate doesn't call createsuperuser

This was a deliberate change, I think it was discussed on the list but maybe just IRC. The tutorial was changed to reflect it, if any documentation still says otherwise it is a documentation bug. On 31 באוגוסט 2014 18:23:58 GMT+03:00, Yo-Yo Ma wrote: >(continued) >

Re: Changes to database-to-python conversions

Big +1. I suspect this also opens the door to a significant speed improvement for Oracle's number column handling, but I'll have to investigate further (ask me about numbers_as_strings if you're interested in details). Thanks for the great work, Shai. -- You received this message because

Re: Requiring GitHub login for actions on Trac

On Sunday 24 August 2014 20:44:30 Aymeric Augustin wrote: > > Eventually, I managed to set up DjangoProject and GitHub auth in parallel. > > Contributors who refuse GitHub's ToS can participate on Trac again. > > Issues created by username mismatches have been dealt with. Thanks, Aymeric, for

Re: [ANN] django-synth, a bridge to Synth's C++ template engines

Hi, As this is the 4th example I see of a templating engine that is inspired by the Django Template Language, I started a small collection of them on the wiki[1]. I usually work with other parts of Django, but thought people who are more into the front-end might find this interesting. HTH,

Re: GSoC Meta refactor: Bikeshedding time!!

Hi Daniel, On Thursday 21 August 2014 22:53:36 Daniel Pyrathon wrote: > > On Wednesday, August 20, 2014 8:21:36 PM UTC+2, Shai Berger wrote: > > makes me itch a little as well -- mostly, because each of the objects > > returned by the property is not a related-object, bu

Re: GSoC Meta refactor: Bikeshedding time!!

Hi again, Below, ">D" are quotations from Daniel's message I'm replying to, and ">R" are from Russell's message that opened this thread. >D *Regarding FileField* It took me some time to clear for myself why FileField is a data field, and not like FK: The point is not where the data is stored

Re: Would AssertMaxQueries (similar to AssertNumQueries) be a useful addition

On Sunday 17 August 2014 17:36:12 Michael Manfre wrote: > AssertNumQueries is often a problem for 3rd party backends. > AssertMaxQueries would become the same and likely result in poorly written > tests because of the inherent slop factor in the arbitrarily chosen max > value. > I agree with the

Re: GSoC Meta refactor: Bikeshedding time!!

Hi, It seems to me that the taxonomy doesn't handle well FileField and ImageField. It could be bundled in with ForeignKey (as the data it really represents is only pointed at by the related column data), but not with the current wording. For ImageField, there is -- in addition to the above --

Re: ORM Optimization for filtering by related existence

On Wednesday 13 August 2014 09:55:33 Anssi Kääriäinen wrote: > > But, how about .filter(Q(somefield__exists=False) | > Q(somefield__othercol=2))? This one should return results only if there > are no somefield related instances at all, or if there are related > instances, then at least one of

Re: ORM Optimization for filtering by related existence

On Friday 08 August 2014 10:41:20 Anssi Kääriäinen wrote: > > As for addition of .exists lookup - how > should .filter(somefield__exists=False, somefield__othercol=2) work? It should be noted that __exists is a little special. For the False case above, .filter(somefield__exists=False,

Bug#576386: #576386 - nautilus: with --no-desktop and exit_with_last_window==false, a quit menu option is needed

Hi Pedro, The context in which this came up was that nautilus was started as an application and then started to manage the desktop. In the setting which you describe, nautilus is explicitly used to manage the desktop; I don't see much value in a quit option in this use-case. Thanks, Shai. On

Bug#570314: #570314 - nautilus: --no-desktop should imply exit_with_last_window and !media_automount_open

Hi again, If you are using nautilus to manage the desktop, then you don't have --no-desktop (or whatever that option is called today). This use is irrelevant to the bug. The two bugs asked for seperate (though related) features, but it seems both of them can be closed now. Thanks, Shai. On

Re: Requiring GitHub login for actions on Trac

On Saturday 09 August 2014 01:38:32 Curtis Maloney wrote: > For what it's worth, I can understand the opposition to requiring a GH > login [ostensibly a "coders" account] in order to make comments on tickets. > > However, if you're opinionated on a ticket you're either a coder, or feel > strongly

Bug#576386: #576386 - nautilus: with --no-desktop and exit_with_last_window==false, a quit menu option is needed

Hi Pedro, On Saturday 09 August 2014 03:02:22 Pedro Beja wrote: this is an old bug. Could you please still reproduce this issue with newer nautilus version like 3.4.2-1+build1 or 3.12.2-1 ? See the bug[1] this was spun off from -- according to my tests with 3.4.2-2, a quit menu option

Re: Requiring GitHub login for actions on Trac

On Friday 08 August 2014 01:49:55 Ben Finney wrote: > Aymeric Augustin writes: > > GitHub doesn't require creating a new account, since anyone interested > > in contributing to Django should have a GitHub account already to > > submit pull requests. > > This

Re: Requiring GitHub login for actions on Trac

Hi, > On 08/06/2014 03:30 PM, Tim Graham wrote: > > I proposed the idea a couple months ago and got several +1's. The main > > concern was from Shai, "not quite -1, but a strong -0 on "blessing" any > > single oAuth provider. GitHub is fine, but so are Google, StackExchange, > > and even the Evil

Re: Updating the organization of the Django Project

+1 What they said. On Wednesday 23 July 2014 23:47:41 Paul McMillan wrote: > +1 > > Thanks for your hard work, Aymeric. > > -Paul > > On Wed, Jul 23, 2014 at 12:25 PM, charettes wrote: > > +1 > > > > Thanks for putting this up together Aymeric > > > > Simon > > > >

Bug#576384: #576384 - nautilus: --no-desktop and media_automount_open==false should imply no automount

Hi there, On Friday 18 July 2014 17:39:24 you wrote: Hey Shai, this is an old bug. Could you please still reproduce this issue with newer nautilus version like 3.4.2-1+build1 or 3.8.2-3 ? I tried to reproduce: Version: 3.4.2-2 It seems that even with media_automount and

Bug#570314: #570314 - nautilus: --no-desktop should imply exit_with_last_window and !media_automount_open

Hi, On Friday 18 July 2014 17:12:42 Pedro Beja wrote: this is an old bug. Could you please still reproduce this issue with newer nautilus version like 3.4.2-1+build1 or 3.8.2-3 ? With 3.4.2-2, I found nautilus to exit with closure of its last window, with or without --no-desktop, and

Re: use semantic versioning after 2.0?

On Monday 14 July 2014 20:07:16 Collin Anderson wrote: > Hi All, > > I just saw #23015 come through (1.9 -> 2.0 not an earth-shattering > release). I think it's a little ridiculous that decimal point doesn't > really mean anything. > > I'm wondering if it would make sense, after 2.0, to follow

Bug#752467: python-virtualenv: what mike said

Package: python-virtualenv Version: 1.11.6-2 Followup-For: Bug #752467 Dear Maintainer, The virtualenv package now exists in testing. However, As Mike Hommey pointed out, nothing installs it by default on a system which used to get the virtualenv command from python-virtualenv. Installing

[Python-modules-team] Bug#752467: python-virtualenv: what mike said

Package: python-virtualenv Version: 1.11.6-2 Followup-For: Bug #752467 Dear Maintainer, The virtualenv package now exists in testing. However, As Mike Hommey pointed out, nothing installs it by default on a system which used to get the virtualenv command from python-virtualenv. Installing

Re: הצעה: המקור צריכה: 1. לא לפחד מכסף. 2. לשכור מנהלים של הקופה, וכו במקום שהכל יהיה בהתנדבות.

שלומי, אף חברה רצינית לא תתמוך בעמותת המקור לשם קיום העמותה עצמה. תרומות יגיעו לקידום איזשהן פעולות ספציפיות – וזה דבר ש„המקור”, כיום, לא עושה. „המקור” הוקמה וממשיכה לתפקד כגוף משפטי עם חשבון בנק עבור פעילי קוד־פתוח שצריכים אחד כזה. לפעמים, עמותות שעושות דברים כאלה – מתפקדות בעצם כצינור כספים

Re: Building a library of SQL functions into Django

On Monday 30 June 2014 17:11:22 Josh Smeaton wrote: > This is how we think we can ask 3rd party backends to provide > implementations for functions they need to modify: > > > class DatabaseWrapper(BaseDatabaseWrapper): > > def __init__(self, *args, **kwargs): >

Re: Cron mirror@tux $HOME/rsync-run gentoo-portage

Date: 2014-06-21 12:11 GMT+03:00 Subject: Fwd: Cron mirror@tux $HOME/rsync-run gentoo-portage To: Hamakor Board bo...@hamakor.org.il Cc: Adir Abraham a...@hamakor.org.il, Amit Aronovitch aronovi...@gmail.com, Shai Berger s...@platonix.com היי, אודה אם מישהו יוכל להסדיר את

Bug#752467: python-virtualenv: no command virtualenv

Package: python-virtualenv Version: 1.11.6-2 Severity: important Dear Maintainer, The package is installed, but the command is not found. $ virtualenv The program 'virtualenv' is currently not installed. To run 'virtualenv' please ask your administrator to install the package

Bug#752467: python-virtualenv: unstable is ok

Package: python-virtualenv Followup-For: Bug #752467 Dear Maintainer, I just realized that, in unstable, the missing command is provided by a separate package named virtualenv. However, it seems that this package does not (yet?) exist in testing. -- System Information: Debian Release:

[Python-modules-team] Bug#752467: python-virtualenv: no command virtualenv

Package: python-virtualenv Version: 1.11.6-2 Severity: important Dear Maintainer, The package is installed, but the command is not found. $ virtualenv The program 'virtualenv' is currently not installed. To run 'virtualenv' please ask your administrator to install the package

[Python-modules-team] Bug#752467: python-virtualenv: unstable is ok

Package: python-virtualenv Followup-For: Bug #752467 Dear Maintainer, I just realized that, in unstable, the missing command is provided by a separate package named virtualenv. However, it seems that this package does not (yet?) exist in testing. -- System Information: Debian Release:

Bug#752183: kdm: no login prompt

Package: kdm Version: 4:4.11.9-1 Severity: important Dear Maintainer, After an upgrade, everything seemed fine, but after an unorderly reboot, kdm no longer shows a login prompt. kdm.log says: klauncher(3169) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.

Bug#752183: kdm: no login prompt

Package: kdm Version: 4:4.11.9-1 Severity: important Dear Maintainer, After an upgrade, everything seemed fine, but after an unorderly reboot, kdm no longer shows a login prompt. kdm.log says: klauncher(3169) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.

Re: Building a library of SQL functions into Django

Hi, A minor style point: On Thursday 19 June 2014 02:56:10 Josh Smeaton wrote: > > class Lower(Func): > function = 'LOWER' > >[...] > > def mongo_lower(self, compiler, connection): > self.function = '$toLower' > return self.as_sql(compiler, connection) > > setattr(Lower,

Re: Strange behavior when running simple query via script versus view code

Hi, On Tuesday 17 June 2014 16:41:04 Jason Skicewicz wrote: > > > > AttributeError: 'str' object has no attribute '_meta' > > I'm at a loss as to why this is happening, but through debugging, when > Django attempts to get the field via script, lookup_model is a string > whereas in the view

Re: 3rd-party database backends: Do you need a "can_introspect_null" feature flag?

On Tuesday 17 June 2014 13:53:25 Aymeric Augustin wrote: > 2014-06-17 12:26 GMT+02:00 Rahul : > > It introspect Boolean field as SmallIntegerField but in the test case if > > can_introspect_boolean_field=False then it checks only for IntegerField. > > By including

Re: Ready for checkin

On Monday 16 June 2014 20:09:13 Greg Chapple wrote: > Would "Ready for merge" not be a more appropriate term? To me, check-in is > a term I would associate with SVN. > Yes, except that RFM sounds more like "Read Forgotten Manual" :) Shai. -- You received this message because you are

Re: Add an extra parameter to 'static' tag

Hi Renato, Sorry for being a little late to this party. On Sunday 01 June 2014 17:36:43 Renato Oliveira wrote: > > Yeah, i'm aware of this, and sorry for not being explicit. The goal of this > improvement is to point to many places. For exampe, if I have a project > with, bootstrap, jquery and

Re: Video playback

Hi, On Sunday 15 June 2014 23:58:10 Brad Alexander wrote: Can anyone tell me what is going on or how to get the Intel driver dialed in (or even where to look to diagnose these video problems? I recently discovered the existence of a package named i965-va-driver, which is supposed to drive

Re: Supporting and using EOL'd software (was Re: Time to drop support for Oracle < 11?)

On Sunday 15 June 2014 10:59:17 Michael Manfre wrote: > I don't see how it should be up to Django to continue to support all of > these archaic versions of Oracle. To paraphrase the mantra repeated during > various mssql discussions, "Django doesn't need to include everything in > core, it just

Supporting and using EOL'd software (was Re: Time to drop support for Oracle < 11?)

Hi guys, TL;DR -- ...sorry, there's no TL;DR here. It's a bunch of separate ideas. It's a little lengthy. Please bear with me. I'd like to compare our support for old database servers with our support for old browsers. We only recently dropped code that supported IE 6/7 (!) for a security (!)

Re: Time to drop support for Oracle < 11?

Hi Tim and all, On Saturday 14 June 2014 03:52:57 Tim Graham wrote: > > Release - GA Date - Premier Support Ends - Extended Support Ends > > 11.1 - Aug 2007 - Aug 2012 - Aug 2015 > 10.2 - Jul 2005 - Jul 2010 - Jul 2013 > 10.1 Jan 2004 - Jan 2009 - Jan 2012 > 9.2 Jul 2002 - Jul 2007 - Jul 2010 >

Re: 3rd-party database backends: Do you need a "can_introspect_null" feature flag?

On Friday 13 June 2014 08:52:29 Aymeric Augustin wrote: > > Le 13 juin 2014 à 01:30, Michael Manfre <mman...@gmail.com> a écrit : > >> On Thu, Jun 12, 2014 at 6:17 PM, Shai Berger <s...@platonix.com> wrote: > >> > >> Bug #22816[

3rd-party database backends: Do you need a "can_introspect_null" feature flag?

Hi all, Bug #22816[1] is a test failure on Oracle. It was caused by the introduction of the "can_introspect_null" database-feature-flag, which was set to True for all core database backends except for Oracle; and use of that flag in the test of introspection of NullBooleanField. The easiest

Re: Support for function application in ORDER BY

On Tuesday 10 June 2014 02:48:14 Josh Smeaton wrote: > > However, I think having some special case code in filter(), annotate() > > and anything else that takes expressions would be OK > > I strongly disagree with this. Expressions are context insensitive at the > moment, which means they can be

Re: הגיע הזמן להגיד יפה שלום לעמותת המקור

הי שלומי, On Sunday 08 June 2014 15:07:44 Shlomi Fish wrote: מה שאני מנסה לומר שכרגע יש פריחה/ריבוי גדולים של יישומים קנייניים לאנדרואיד. זה צפוי שזה יקרה, אבל במוקדם או במאוחר מרבית היישומים הללו יכתבו כקוד פתוח אן שישוחררו ככאלה, ואני מאמין שבסופו של דבר הם יהיו יותר טובים וינצחו. אתה

ענב גלילי – התביעה

http://www.haaretz.co.il/captain/net/1.2345944 ___ Discussions mailing list Discussions@hamakor.org.il http://hamakor.org.il/cgi-bin/mailman/listinfo/discussions

Re: Why not Single Table Inheritance?

Let me expand on Russell's expletives: On Friday 06 June 2014 09:42:15 Thomas Güttler wrote: > > I guess a lot of developers don't want to hear the next lines: > > I think it is a "not invented here" syndrome: Ruby on Rails did it before. > That's a reason to do it different. > This does

הצעה לסדר היום של האספה: ביטול תקנון פרס המקור

שלום, לקראת האסיפה הקרובה, ובהנחה שהעמותה לא תפורק, אני רוצה להציע לסדר היום את הצעת־ההחלטה הבאה. *ההצעה הפורמלית* : תקנון פרס המקור לא יחייב עוד את מוסדות העמותה. *הסבר* : א. לקראת כנס „אוגוסט פינגוין” האחרון, התגלו בעיות בתהליך בחירת הזוכים בפרס המקור. חלק מחברי הועד רצו להציע פתרונות

הצעה לסדר היום של האסיפה: שינוי תקנון – הודעה על הקפאת חברות

עוד הצעה לסדר, שוב בהנחה שהעמותה תמשיך להתקיים. *ההצעה הפורמלית* : סעיף 15(ד) בתקנון יוחלף לנוסח הבא: ‏ (1) במקרה של התקיימות הטעם האמור בתקנת משנה (ב)(1) תוקפא חברותו של החבר, ללא צורך באישורה של האסיפה הכללית. חבר שמעמדו מוקפא, לא יכול לבצע כל פעולה כחבר, ולא יחשב במניין

Re: הצעה לסדר היום של האסיפה: שינוי תקנון – הודעה על הקפאת חברות

הי ליאור, On Thursday 05 June 2014 13:36:20 Lior Kaplan wrote: היי שי, אתה מנסה למצוא פתרון בתקנון לבעיה טכנית - לא נשלחו הודעות לחבר בשנתיים האחרונות. הפתרון הפשוט הוא לשלוח הודעות על סיום חברות / הקפאה ועל הצורך בחידוש חברות. זה נעשה על ידי בין 2010-2012 בשני מועדים כל שנה - אחד לקראת

Re: django.utils.six.bytes_types?

On Thursday 29 May 2014 12:04:59 Aymeric Augustin wrote: > > Le 28 mai 2014 à 23:57, Shai Berger <s...@platonix.com> a écrit : > > > > So, the PR can be merged without documentation ? > > Since it's a private helper, that's OK. Actually, it isn't: https://docs.d

Re: django.utils.six.bytes_types?

On Wednesday 28 May 2014 22:38:20 Aymeric Augustin wrote: > The name seems confusing to me: it's called bytes_type but its main purpose > is to exclude bytes on Python 2. Otherwise you'd just write > isinstance(value, (bytes, six.memoryview)). > I renamed it to "buffer_types" -- because English

Re: Make url patterns group kwargs more simple

Hi Alexendr, On Wednesday 28 May 2014 18:54:05 Alexandr Shurigin wrote: > Hi all. > > What do you think about adding some extra default and more simpler syntax > for url patterns? > [looking for a way to re-write...] > > url(r'^(?P[^/]+)/(?P[^/]+)/news/(?P[^/]+)$',... > [...as...] > > >

django.utils.six.bytes_types?

Hi all, While solving #22715[1], I found myself writing these lines: elif (isinstance(value, six.memoryview) or six.PY3 and isinstance(value, bytes)): six.memoryview -- django.utils.six.memoryview, to be accurate, there's no memoryview in the original six

Re: Schema tests and .extra queryset method

Hi Maximiliano, Sorry for the delay in responding to this. On Thursday 22 May 2014 17:06:23 Maximiliano Robaina wrote: > El jueves, 22 de mayo de 2014 03:24:12 UTC-3, Shai Berger escribió: > > > > Quoting it uncoditionally would break the test on Oracle (which, by > &g

Fwd: [cx-oracle-users] cx_Oracle 5.1.3

Hi all, This release of cx_Oracle includes fixes the segfaults encountered with Python3, and includes significant performance improvements for 64-bit platforms (where long is 64-bits, so, specifically, Windows not included). Strongly recommended for all Oracle users. Have fun, Shai.

Fwd: [cx-oracle-users] cx_Oracle 5.1.3

Hi all, This release of cx_Oracle includes fixes the segfaults encountered with Python3, and includes significant performance improvements for 64-bit platforms (where long is 64-bits, so, specifically, Windows not included). Strongly recommended for all Oracle users. Have fun, Shai.

Re: Why not Single Table Inheritance?

On Thursday 22 May 2014 11:05:24 Anssi Kääriäinen wrote: > I think it is time to add a new model classmethod from_db() to Django. > > The idea is to allow customization of object initialization when loading > from database. Instead of calling directly model.__init__ from the queryset > iterators,

Re: Schema tests and .extra queryset method

Hi Maximiliano, The issue of case in quoted and un-quoted names in SQL is indeed a sad mess, bad decisions made in the 1960s that we still need to live with today. On Wednesday 21 May 2014 15:38:57 Maximiliano Robaina wrote: > > self.assertEqual(Author.objects.extra(where=["thing =

Re: Why not Single Table Inheritance?

On Monday 12 May 2014 12:27:01 Thomas Güttler wrote: > Single Table Inheritance is used by ruby-on-rails and SQLAlchemy. > > Are there reasons why it is used in django? > Essentially, STI is a form of database denormalization. I think Django should not encourage this. > I would love to see a

KMail 4.12: Still not ready

Hi, I've read some reports that KMail 4.12 was working well for people. I was looking forward to seeing it in Sid, hoping things would be better. I'm said to say, I find this not to be the case. Bug 259813[1] still makes the unread status filter unusable. I still see the bugs where messages

Re: גילוי דעת לפני האסיפה השנתית

On Saturday 10 May 2014 13:07:17 moshe nahmias wrote: עפי חוק התפקידים של ועדת הביקורת הם (העתקה ישירה): 30. אלה תפקידי ועדת הביקורת או הגוף המבקר: (1) לבדוק את תקינות פעולות העמותה ומוסדותיה, לרבות התאמת פעולות העמותה למטרותיה; (2) לבדוק את השגת יעדי העמותה ביעילות ובחיסכון; (3) לעקוב אחר

Re: גילוי דעת לפני האסיפה השנתית

חברי וידידי העמותה, שלום, ‏On Thursday 01 May 2014 08:38:24 Doron Ofek wrote:‎ כידוע לכולם, בזמן הקרוב תתקיים האסיפה הכללית השנתית של עמותת המקור [...]לצערי, מסיבות בריאותיות, לא אוכל להיות נוכח באסיפה. גם אני אעדר מהאסיפה, מסיבות הרבה יותר שמחות (כנס Django בצרפת, שהתחייבתי אליו הרבה לפני

Re: Database-dependant tests and third-party backends

Hi, On Wednesday 07 May 2014 19:40:08 Aymeric Augustin wrote: > > I'm trying to make the lives of maintainers of third-party database > backends a bit easier. > +1. > > *1) Checking database features* > > This is the correct solution for database-dependant tests in general. > In most

Timeline for 1.4.12/1.5.7/1.6.4

Hi, Since 1.4.11/1.5.6/1.6.3 introduced the reverse regression, and it was fixed already -- are we planning another release soon? Thanks, Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and

Re: Trac #22343 -- select-for-update in autocommit mode

Hi Marti, On Tuesday 22 April 2014 18:37:37 Marti Raudsepp wrote: > On Thu, Mar 27, 2014 at 4:20 PM, Shai Berger <s...@platonix.com> wrote: > > The relevant tests do a select-for-update to verify that the "for update" > > clause is, indeed, added; and they h

Re: Should there be a "is" comperator: {% if A is B %}?

Hi all, For the use case brought up originally, note https://code.djangoproject.com/ticket/20684 In that spirit, I think the better solution for the more general case brought here is a filter, say tag_attr, which takes a name and a value and renders them appropriately: {% for name, value in

Re: Unicode in validators tests

On Wednesday 02 April 2014 13:43:23 alois.guill...@gmail.com wrote: > Hi, > > I was wondering if the test inputs in the validators tests should be given > as unicode or python string. It seems to me that at the moment the > validation is done, the string is already coded in unicode. However the >

Re: Trac #22343 -- select-for-update in autocommit mode

On Monday 31 March 2014 09:18:57 Anssi Kääriäinen wrote: > On 03/30/2014 07:48 PM, Shai Berger wrote: > > While fixing this, I ran into this line in the current docs: > > """ > > Using select_for_update on backends which do not support SELECT ... FOR > > U

Re: Trac #22343 -- select-for-update in autocommit mode

On Thursday 27 March 2014 19:59:52 Aymeric Augustin wrote: > On 27 mars 2014, at 15:20, Shai Berger <s...@platonix.com> wrote: > > So I'm suggesting we change the behavior of select-for-update queries, to > > error out when executed with no transaction. This is a > > ba

Re: Migrations in Django 1.7 make unit testing models harder

On Sunday 30 March 2014 15:08:17 Harry Percival wrote: > Ah, so the reason I was confused is because it *looks* like the default is > the empty string, because that's what you get if you initialise an object, > by default. But at the database level, the default for the column is NULL. > Is that

Re: LiveServerTestCase vs StaticLiveServerCase

On Saturday 29 March 2014 19:11:17 Harry Percival wrote: > > What I *am* saying is that, in my opinion, there's not much point in > LiveServerTestCase if it doesn't do static files. So, to keep things > simple, it would be simpler to remove it, and just have on LiveServer test > class, that

Re: Add support for get_or_none?

Hi, (the below is reordered) On Wednesday 26 March 2014 21:44:22 Anssi Kääriäinen wrote: > > Actually I think we could use .get(default=None). The way to do this is: > 1. Deprecate direct use of .get(default=lookup_value), instead ask users > to do .get(Q(default=lookup_value)). > 2. After

Re: Migrations in Django 1.7 make unit testing models harder

On Thursday 27 March 2014 01:39:53 Bernie Sumption wrote: > > I'd be willing to keep the current contract of "things without a > > migrations directory don't get migrated", but I suspect you're doing > > things > > on apps that already have migrations (which makes my reticence to add a > > setting

Trac #22343 -- select-for-update in autocommit mode

Hi, Ticket #22343[1] is about a couple of tests failing under Oracle. But it raises a question that's a little deeper. The relevant tests do a select-for-update to verify that the "for update" clause is, indeed, added; and they happen to run in autocommit mode. They fail because, under

Re: Proposal for prepared statements API

On IRC, @apollo13 asked some very good questions about the lifecycle of prepared statements. I would like to elaborate. Prepared statements usually live on the server, in the context of a session -- which, for Django, means they're only valid in the thread where they were built; without

Re: APPEND_SLASH skip per URL or per base_uri

On Friday 14 March 2014 17:07:41 Val Neekman wrote: > Hi Aymeric, > > Localized solution is fine, but when I saw the number posts from people who > were trying to find a solution to this, I thought, perhaps it would be a > nice little enhancement to the APPEND_SLASH functionality. >

Re: Add support for get_or_none?

There is a family of names that would be valid -- names that cannot be used to name fields -- and that is names that begin with dunder. I would like to see neither get(__default=x) nor first(__only=True) -- I think that's quite ugly -- I just want to remind us that technically, the option

Re: Add support for get_or_none?

On Thursday 13 March 2014 14:34:18 Josh Smeaton wrote: > +1 on get_or_none. It seems to be a pattern that comes up quite a lot in > user code, and I know I've had use for it lots of times. Since 1.6, you should just be using first(). Compared to the try-get-except-DoesNotExist-return-None

Re: Add support for get_or_none?

On Thursday 13 March 2014 18:45:31 Cal Leeming [Simplicity Media Ltd] wrote: > Seems this issue was brought up several years ago, though the thread was > later hijacked for other functionality and get_or_none fizzled out. > https://groups.google.com/forum/#!topic/django-developers/Saa5nbzqQ2Q > >

Re: Automatic filtering in kmail

On Tuesday 11 March 2014 01:56:57 Stanley Schade wrote: Hi, I recently upgraded from wheezy to jessie on a 64-bit system and as far as I can tell the data migration within kmail went quite smoothly. However, for some reasons my newly set up filters are not applied to incoming mail

Re: [GSoC] Dynamic, rule-based ModelForms

On Thursday 06 March 2014 01:17:51 Paolo Coffetti wrote: > Hi Django devs, > > I want to share an idea with you and get some feedback in order to know if > it makes sense, if it could solve a common problem and maybe evolve into an > official GSoC proposal. > > Some years ago I was working on a

Re: Case handling for application verbose names

On Monday 10 March 2014 08:30:41 Russell Keith-Magee wrote: > On Mon, Mar 10, 2014 at 4:23 AM, Aymeric Augustin < > > aymeric.augus...@polytechnique.org> wrote: > > > > I'm now thinking that it's acceptable to keep capitalized application > > names and live with the inconsistency. However, if I

Re: DRY date_format and datetime objects

Hi, On Thursday 06 March 2014 23:23:50 Jon Dufresne wrote: > > I am using Django 1.6. I find myself using date_format semi-regularly > to convert datetime objects to strings in the DATE_FORMAT format. [...] > I am considering a pull request that extends Python's datetime class > that overrides

Re: Testing parameters in database settings

tafile size). Similarly, the test runner can not > create the database for Oracle RAC because of the datafile name. > > Regards, > > Josh > > On Thursday, 6 March 2014 06:41:57 UTC+11, Shai Berger wrote: > > Hi, > > > > I've put up https://github.com/dj

Re: Testing parameters in database settings

Hi, I've put up https://github.com/django/django/pull/2400 for review. It makes the changes discussed -- test settings go into a 'TEST' dictionary in the database settings, with a deprecation warning for old settings. While at it, I added (in a separate commit) a renaming of two

Re: requiring login to perform Trac actions?

On Monday 03 March 2014 16:17:13 Tim Graham wrote: > There's been some discussion on ticket > #22067 and #django-dev about > requiring Trac login to help cut down on spam and generally improve the > quality of the discussion. > +1 for requiring login,

[issue13936] datetime.time(0, 0, 0) evaluates to False despite being a valid time

Shai Berger added the comment: Just got bit by this. Tim Peters said: It is odd, but really no odder than zero values of other types evaluating to false in Boolean contexts. I disagree. Midnight is not a zero value, it is just a value. It does not have any special qualities analogous

<    3   4   5   6   7   8   9   10   11   12   >