Bug#723105: nepomuk-core-runtime: Nepomuk sends virtuoso to 100% CPU after marking KMail folder read

Package: nepomuk-core-runtime Version: 4:4.10.5-1+b1 Severity: normal Dear Maintainer, Just what the summary says. In KMail, I right-clicked the Junk folder (37400 messages, 500M, about 8000 were unread) and selected mark folder as read. This seems to have worked, but since that moment, and for

Bug#723105: nepomuk-core-runtime: Nepomuk sends virtuoso to 100% CPU after marking KMail folder read

Package: nepomuk-core-runtime Version: 4:4.10.5-1+b1 Severity: normal Dear Maintainer, Just what the summary says. In KMail, I right-clicked the Junk folder (37400 messages, 500M, about 8000 were unread) and selected mark folder as read. This seems to have worked, but since that moment, and for

Re: עזרה בפתרון בעיית שעון הקיץ באובונטו

On Monday 09 September 2013 16:36:04 Yaron Shahrabani wrote: אגב, בדביאן זה כן קרה ☺ פשוט הערוצים של unstable ו־testing עודכנו, ה־stable על 2013c (כלומר שהתקלה תופיע בעוד חודש) והישנות (wheezy ו־squeeze) נשארו בגרסאות מ־2012. תיקון: stable, כרגע, הוא wheezy (והוא באמת על 2013c). לדביאן יש

Re: Order of INSTALLED_APPS

On Monday 02 September 2013 12:34:03 VernonCole wrote: > It also affects _how_ South works, not just _whether_ it works. Only this > week I had to install a patch for the formhub package which consisted of > re-ordering INSTALLED_APPS so that tables were built in the correct order > on PostgreSQL

Bug#721312: Upgrading libclutter-1.0-0 seems to have fixed this

Hi, Upgrading libclutter-1.0-0 seems to have fixed this problem. Now at 1.14.4-3, and evolution starts. (so whoever closes this can also reassign it to libclutter while at it). Thanks, Shai. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

[Evolution] Bug#721312: Upgrading libclutter-1.0-0 seems to have fixed this

Hi, Upgrading libclutter-1.0-0 seems to have fixed this problem. Now at 1.14.4-3, and evolution starts. (so whoever closes this can also reassign it to libclutter while at it). Thanks, Shai. ___ Pkg-evolution-maintainers mailing list

Bug#721312: evolution will not start

Package: evolution Version: 3.4.4-4+b1 Severity: important Dear Maintainer, Starting evolution has ceased to work after recent updates. The problem seems to be related to clutter, but I am not a gnome user, so I cannot be sure. I usually use evolution under KDE, and there, I get this: $

[Evolution] Bug#721312: evolution will not start

Package: evolution Version: 3.4.4-4+b1 Severity: important Dear Maintainer, Starting evolution has ceased to work after recent updates. The problem seems to be related to clutter, but I am not a gnome user, so I cannot be sure. I usually use evolution under KDE, and there, I get this: $

Re: Proposal: Modifying the CSRF protection scheme

On Friday 09 August 2013 18:08:26 Luke Plant wrote: > On 03/08/13 23:57, Shai Berger wrote: > > This would work exactly like it works today, except with signed cookies. > > That is, the "user specific element" is the cookie. CSRF is about > > tricking the user int

Re: Proposal: Modifying the CSRF protection scheme

Hi, You can find my work-in-progress at https://github.com/django/django/pull/1454. It is nowhere near ready yet -- it is still missing some pieces and has commented-out debug printing, but I'm done for tonight, and I think it is advanced enough that people may want to take a look and comment.

Re: Proposal: Modifying the CSRF protection scheme

Hi, On Sunday 04 August 2013 01:26:58 Luke Plant wrote: > On 28/07/13 00:12, Shai Berger wrote: > > > > a) Use a signed cookie for csrftoken -- using Django's existing signing > > facility[4], this means signing the cookie with the SECRET_KEY from the > > settings; so

Bug#717618: kmail: Resource KMail Folders is broken. This resource is now online

Package: kmail Followup-For: Bug #717618 Possibly related: Bug #717101, where the same message is displayed; there, it is always related to problems accessing specific messages. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500,

Bug#718616: kmail: aborts on session startup

Package: kmail Version: 4:4.10.5-1 Severity: minor Dear Maintainer, I use kmail always, so it is usually open when I close a session. Then, when I log in again, I expect the whole session to re-open. This has always worked well. Since kmail2, however, kmail aborts on session startup with a

Re: קול קורא למתנדבים בכנס פינגווין 2013 - הזדמנות אחרונה לאיוש תפקידים!

On Thursday 01 August 2013 18:49:34 Danniel wrote: אני לא ממש יודע אם זה המקום אבל, המקום נכון, אבל ככה כשאתה מצטרף לפתיל קיים במקום לפתוח פתיל משלך, אנשים יפספסו את ההודעה ואולי גם יחפשו אותה אח״כ ולא ימצאו. שי. ___ Discussions mailing list

Re: Proposal: Modifying the CSRF protection scheme

Hi (quotation below edited) On Monday 29 July 2013 17:59:53 Matthew Lauber wrote: > On Sat, Jul 27, 2013 at 7:12 PM, Shai Berger <s...@platonix.com> wrote: > > > > a) Use a signed cookie for csrftoken -- using Django's existing signing > > facility[4], th

Bug#718214: akonadi: caused kmail to fail storing downloaded mails

Package: akonadi-server Version: 1.9.2-2 Severity: important File: akonadi Dear Maintainer, I usually leave my session open for several days, including kdepim applications. Yesterday, by chance, I did restart. Today when I got to the computer, around 22:00, I found that it had stopped

Bug#718214: upstream ref

forwarded 718214 https://bugs.kde.org/show_bug.cgi?id=322923 thanks bug also reported upstream as https://bugs.kde.org/show_bug.cgi?id=322923 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#718214: akonadi: caused kmail to fail storing downloaded mails

Package: akonadi-server Version: 1.9.2-2 Severity: important File: akonadi Dear Maintainer, I usually leave my session open for several days, including kdepim applications. Yesterday, by chance, I did restart. Today when I got to the computer, around 22:00, I found that it had stopped

Bug#718214: upstream ref

forwarded 718214 https://bugs.kde.org/show_bug.cgi?id=322923 thanks bug also reported upstream as https://bugs.kde.org/show_bug.cgi?id=322923 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Proposal: Modifying the CSRF protection scheme

Hi everybody, TL;DR: A simple change can make Django's CSRF protection a little better; an additional, slightly less simple one, can also make it look better. Django's CSRF protection scheme is a bit unusual; unlike most such schemes, it does not rely on a value stored in the server that needs

Re: [GSoC] Revamping validation framework and merging django-secure once again

On Thursday 25 July 2013 08:37:06 Russell Keith-Magee wrote: > > Could I get you to open this as a ticket so that it isn't forgotten? > https://code.djangoproject.com/ticket/20814 Thanks, Shai. -- You received this message because you are subscribed to the Google Groups "Django

Re: [GSoC] Revamping validation framework and merging django-secure once again

Hi Christopher, While you're dealing with model validation, I wonder if you can take a look at this little example -- a minor failure in the current model validation: class General(models.Model): name = models.CharField(max_length=30) class Special(General): pass

Re: Custom Chainable QuerySets (#20625)

On Monday 22 July 2013 13:25:38 Anssi Kääriäinen wrote: > On Monday, July 22, 2013 1:16:04 PM UTC+3, Loic Bistuer wrote: > > On Jul 22, 2013, at 4:38 PM, Chris Wilson > > > > > > wrote: > > > I think that's very true. How about this? > > > > > >> class

Re: KMail 2: problems after recent changes in unstable

Hi, Martin Steigerwald wrote: Am Sonntag, 21. Juli 2013, 02:45:37 schrieb Shai Berger: But until it does get better, please avoid promoting it. What do you mean by that? At some time KDE SC 4.10 had to enter unstable. And I think its better to do it now, rather than later

Re: KMail 2: problems after recent changes in unstable

Hi, In view of this and several other problems reported on this package, I believe it is not ready for testing yet. I know some of the reported problems (though, as far as I'm aware, not the major ones) have been solved in upstream; but pending the solution of others, this is only almost

Bug#717110: link to upstream ticket

forwareded 717110 https://bugs.kde.org/show_bug.cgi?id=259813 thanks My KDE ticket turned out to be a dupe, linking to the correct ticket. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717110: link to upstream ticket

forwareded 717110 https://bugs.kde.org/show_bug.cgi?id=259813 thanks My KDE ticket turned out to be a dupe, linking to the correct ticket. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#717101: kmail: random failures to read messages

Package: kmail Version: 4:4.10.5-1 Severity: important Tags: upstream Dear Maintainer, Having used the new kmail2 for a couple of days, I keep running into this: On certain messages, when I try to select the message to have it previewed, I get (for each such message) 6 notifications: 3 pairs of

Bug#717110: kmail: status filter unread unusable

Package: kmail Version: 4:4.10.5-1 Severity: normal Tags: upstream Dear Maintainer, When the status filter on the message list is set to Unread, every message whose status changes to read is immediately removed from the list (except when messages are threaded and the message has an unread

Bug#717111: kmail: when writing mail, subject line not right-aligned when RTL

Package: kmail Version: 4:4.10.5-1 Severity: minor Tags: upstream l10n Dear Maintainer, When writing an RTL subject line in a new message, the subject line control stays left-aligned -- but it should be right-aligned; text in the message body does get the correct alignment automatically.

Bug#717113: kmail: Please default reply using HTML if present to False

Package: kmail Version: 4:4.10.5-1 Severity: wishlist Dear Maintainer, The new KMail2 has a new configuration option, reply using HTML if present (or, in the coming 4.11, reply or forward...). The default value for this option is True. However, as far as I can see, using this option creates some

Bug#717101: kmail: random failures to read messages

Package: kmail Version: 4:4.10.5-1 Severity: important Tags: upstream Dear Maintainer, Having used the new kmail2 for a couple of days, I keep running into this: On certain messages, when I try to select the message to have it previewed, I get (for each such message) 6 notifications: 3 pairs of

Bug#717110: kmail: status filter unread unusable

Package: kmail Version: 4:4.10.5-1 Severity: normal Tags: upstream Dear Maintainer, When the status filter on the message list is set to Unread, every message whose status changes to read is immediately removed from the list (except when messages are threaded and the message has an unread

Bug#717111: kmail: when writing mail, subject line not right-aligned when RTL

Package: kmail Version: 4:4.10.5-1 Severity: minor Tags: upstream l10n Dear Maintainer, When writing an RTL subject line in a new message, the subject line control stays left-aligned -- but it should be right-aligned; text in the message body does get the correct alignment automatically.

Bug#717113: kmail: Please default reply using HTML if present to False

Package: kmail Version: 4:4.10.5-1 Severity: wishlist Dear Maintainer, The new KMail2 has a new configuration option, reply using HTML if present (or, in the coming 4.11, reply or forward...). The default value for this option is True. However, as far as I can see, using this option creates some

Bug#716881: issue solved?

It appears that logging off anf then back on did sort this out. Thanks, Shai. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#716881: Yes, you must re log in

On Sunday 14 July 2013 17:56:49 Lisandro Damián Nicanor Pérez Meyer wrote: Hi! Indeed, the best way to upgrade KDE stuff it's without KDE running. At very least, restart the session as soon as you upgraded KDE. I'm thus closing this bug. That's a bit of a misinterpretation: Of course I

Bug#716881: issue solved?

It appears that logging off anf then back on did sort this out. Thanks, Shai. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1750580.WljZUksilY@deblack

Bug#716881: Yes, you must re log in

On Sunday 14 July 2013 17:56:49 Lisandro Damián Nicanor Pérez Meyer wrote: Hi! Indeed, the best way to upgrade KDE stuff it's without KDE running. At very least, restart the session as soon as you upgraded KDE. I'm thus closing this bug. That's a bit of a misinterpretation: Of course I

Bug#716881: kmail: will not send mail

Package: kmail Version: 4:4.10.5-1 Severity: important Dear Maintainer, The newly-in-sid kmail2 imported almost everything correctly from the old kmail1 setup. This was very impressive. However, it messed up a little the import of the sending accounts (in particular, it marked identities as

Bug#716881: kmail: removing unused sending account did not help

Package: kmail Version: 4:4.10.5-1 Followup-For: Bug #716881 Dear Maintainer, Continuing the above, a) The alluded to warning was: $ kmail2(4756)/kdepimlibs (mailtransport) MailTransport::SendQueuedAction::itemAccepted: Item doesn't have DispatchModeAttribute. b) Removing the unused SMTP

Bug#716881: kmail: will not send mail

Package: kmail Version: 4:4.10.5-1 Severity: important Dear Maintainer, The newly-in-sid kmail2 imported almost everything correctly from the old kmail1 setup. This was very impressive. However, it messed up a little the import of the sending accounts (in particular, it marked identities as

Bug#716881: kmail: removing unused sending account did not help

Package: kmail Version: 4:4.10.5-1 Followup-For: Bug #716881 Dear Maintainer, Continuing the above, a) The alluded to warning was: $ kmail2(4756)/kdepimlibs (mailtransport) MailTransport::SendQueuedAction::itemAccepted: Item doesn't have DispatchModeAttribute. b) Removing the unused SMTP

Thank you

Hi Debian-KDE maintainers, First of all, I'd like to thank you very much for the way you've handled the migration of KDE-PIM and, in particular, kmail2. Holding out for so long, while other distros shipped the completely premature versions released since KDE 4.6, must have been a tough call; I

Oracle users -- which first, Python 3 or Oracle 12?

Hi Oracle users, As you may be aware, Oracle 12 was released last month, and Django 1.6 declares Python 3 fully supported. As you may also be aware, Django currently cannot be tested with Oracle 12 [1] or with earlier Oracle under Python 3 [2], so these two must be declared unsupported for the

Tests -- Errors vs. Failures

Hi all, I just pushed a fix to a test failure on Oracle -- the last-executed-query test. However, I want to ask about the preferred style in writing the test itself. The test, as it is written now, is: def test_last_executed_query(self): """ last_executed_query should not

Bug#715375: virtualbox-guest-additions-iso: Fails to install on Centos 6.4

Package: virtualbox-guest-additions-iso Version: 4.2.10-2 Severity: normal Dear Maintainer, I am setting up a new Centos 6.4 VM, and I tried to install the most recent guest additions. I installed Centos from a live-cd, added development tools, added some other packages (I am installing Oracle

Bug#715375: Centos reports a patch available

After submitting, I saw this: http://wiki.centos.org/HowTos/Virtualization/VirtualBox/CentOSguest Where the centos guys give a patch, with explanations how to apply it. After applying, the installation succeeds, and the guest additions work. I suppose that means, at the very least, that the

Re: MAC adddres field

On Wednesday 26 June 2013, Patryk Ściborek wrote: > W dniu środa, 26 czerwca 2013 17:26:12 UTC+2 użytkownik Carl Meyer napisał: > > Do you have any new information to justify why the existing resolution > > of #2239 should be reconsidered? > > > > I think the existing resolution is correct. This

Re: Faster numbers for Oracle

So,... On Monday 17 June 2013 16:02:05 Shai Berger wrote: > On Thursday 16 May 2013 03:51:05 Shai Berger wrote: > > Ticket #20414[0] and PR #1071[1]. > > Over a month, and no comment from anyone on these; I take it as sign that > nobody has time for it. Unless someone wake

Faster numbers for Oracle

On Thursday 16 May 2013 03:51:05 Shai Berger wrote: > > Ticket #20414[0] and PR #1071[1]. Over a month, and no comment from anyone on these; I take it as sign that nobody has time for it. Unless someone wakes up quite quickly to oppose, I'm going to commit essentially the PR (I'm e

Re: Not calling things twice in templates

On Tuesday 04 June 2013, Daniele Procida wrote: > > [...] the {% with expensive.method as variable %} way of doing things > already exists, [...] What about my earlier suggestion that this be dealt > with in Python, not in templates [...] This thread, from its start, has mixed two separate

Re: Not calling things twice in templates

Hi, On Monday 03 June 2013, Andre Terra wrote: > Well, Russ, you asked for suggestions, so here's a couple half-hearted > attempts. > ... and here's a couple of other ones, mostly inspired by those: > {% with my_bonnet.bees as bees if my_bonnet.bees %} > {% if my_bonnet.bees with

Re: Make sure QuerySet.get() does not fetch more rows than it absolutely needs

On Monday 03 June 2013, Patryk Zawadzki wrote: > Here's the ticket: > > https://code.djangoproject.com/ticket/6785 > > tl;dr: Calling .get() on a badly filtered queryset can result in lots > of database rows being fetched and wrapped in Python objects for no > gain. > tl;dr: There's a general,

Re: Not calling things twice in templates

On Monday 03 June 2013, Russell Keith-Magee wrote: > Alternatively, add new sub tags to {% for %}: > > {% for bee in my_bonnet.bees %} > {% pre %} > > {% body %} > {{ bee }} > {% post %} > > {% empty %} > No bees in your bonnet. > {% endfor %} > > but that's starting to get verbose, and

Re: Migrations, commands and syncdb

Hi all, On Thursday 30 May 2013, Andrew Godwin wrote: > > The proposals are: > > 1. Change syncdb so that it both does the old behaviour (adds models for > unmigrated apps), and additionally runs any outstanding migrations. There > would be a separate "migrate" command for more complex

Re: Proposal/Discussion: url and template search using the directory structure of apps within django sites

Hi Jorge, On Wednesday 29 May 2013, Jorge C. Leitão wrote: > Hi there. > > Django allows the possibility of putting apps within apps to improve > structure of the code and increase portability. I find this absolutely > genial. > Actually, Django doesn't. That is, an app is a Python package, and

Re: Testing generated SQL under different backends

Hi Carl, On Monday 27 May 2013 19:37:55 Carl Meyer wrote: > Hi Shai, > > On 05/27/2013 09:26 AM, Shai Berger wrote: > > I'm working on fixing some failing tests under Oracle, and I ran into > > > > commands_sql.tests.SQLCommandsTestCase.test_sql_all() > &g

Testing generated SQL under different backends

Hi all, I'm working on fixing some failing tests under Oracle, and I ran into commands_sql.tests.SQLCommandsTestCase.test_sql_all() which collects the sql_all command's output, and verifies it is as expected. It includes, among others, these two lines: # PostgreSQL

Re: Proposal: better support for generating rest apis in django core

Hi Karol, On Saturday 18 May 2013 13:26:53 Karol Sikora wrote: > Hi, > > We was talked with Russell on djangocon eu about integrating more rich > support for working django as rest api provider, focused on dealing with > one-page web applications. > The motivations that currently without third

Re: selecting app for syncdb

On Thursday 23 May 2013, Łukasz Langa wrote: > On 23 maj 2013, at 00:52, Shai Berger <s...@platonix.com> wrote: > > If I'm not mistaken, there are some problems with the latest released > > version (0.7.6) > > FWIW, the latest released version is 0.8 as of earlier tod

Re: Passing parameters to raw()

Hi Roman, On Wednesday 22 May 2013, Roman Klesel wrote: > > howerver this woks just fine and I see no reason why this should not be done: > >>> param = dict(lname = 'Doe') > >>> qs = Person.objects \ > >>>.raw('SELECT * FROM myapp_person WHERE last_name = %(lname)s', param) > This

Re: selecting app for syncdb

On Thursday 23 May 2013, Michał Nowotka wrote: > I don't and I won't (south is not working with Oracle). This discussion is getting to a place where it belongs either on django-users or south-users; I should point out, though, that South does work with Oracle. If I'm not mistaken, there are

Re: History of datetime_cast_sql() in Oracle

On Tuesday 21 May 2013 22:11:02 Aymeric Augustin wrote: > On 19 mai 2013, at 15:33, Shai Berger <s...@platonix.com> wrote: > > > > So -- I want to fix, now, the thing that was, well, not broken, but bent, > > in 2007. And my question to you -- especially, those

Re: History of datetime_cast_sql() in Oracle

Hi Ian, Thanks for your insights. On Tuesday 21 May 2013 23:22:14 Ian Kelly wrote: > > You may be right. One thing I would be concerned about is the > reliability of only doing implicit date conversions. If you google > for "ORA-01843" you can find a good number of forum posts that >

Re: Anyone have ideas on #16550 - custom SQL before/after syncdb?

On Tuesday 21 May 2013, Donald Stufft wrote: > I run migrations in test. How else will you know your db reflects reality > :/ > When you have a few hundred migrations, that's something you're willing to do in your CI server, but not on your development machine. Shai. -- You received this

History of datetime_cast_sql() in Oracle

Hi, In my quest to solve Oracle bugs, I found the function datetime_cast_sql() in the Oracle backend. It causes a problem these days, because it gets in the way of querying a date as string (mydate__startswith='2005'). It is a function that is defined as a no-op in the base backend, and

Re: django and paramstyle: what's the actual story?

Hi Vernon and all, On Friday 17 May 2013, VernonCole wrote: > Shai: > > I think that you are showing how rotten this whole "paramstyle" mess is: > the thing you are describing is, IIUC, "pyformat" paramstyle. "named" uses > a ":name" SQL statement syntax, and expects a mapping of parameters.

Re: ORA-01882 [was Re: looking up date as str (fails under Oracle, Ticket #20015)]

Oopsie: On Sunday 19 May 2013 08:12:12 Shai Berger wrote: > ...They do pass on our CI [0],... http://ci.djangoproject.com/job/Django%20Oracle/lastCompletedBuild/database=oracle,python=python2.7/ Thanks, Shai. -- You received this message because you are subscribed to the Goo

ORA-01882 [was Re: looking up date as str (fails under Oracle, Ticket #20015)]

On Saturday 18 May 2013 19:49:58 Shai Berger wrote: > > I'm toying with a different solution now -- removing the date casting on > Oracle too. It passed the lookup tests, now I'm running the whole suite > (that takes a little time). After seeing that no other backend in core > doe

Re: looking up date as str (fails under Oracle, Ticket #20015)

On Saturday 18 May 2013 19:35:31 Anssi Kääriäinen wrote: > On 18 touko, 17:46, Shai Berger <s...@platonix.com> wrote: > > > > 1) The fixes I see would affect all backends, but AFAIK only Oracle is > > reported as failing the test; anyone wants to comment on this? Do

looking up date as str (fails under Oracle, Ticket #20015)

Hi django devs, While going through Oracle bugs, I ran into the ticket in the subject[0]. The problem there is that current code assumes that whenever we want to compare anything (pretty much) against a datetime column, in any way, we'd like to compare the column value and the given value as

Re: זכר ונקבה ב־gettext

On Saturday 18 May 2013, you wrote: @שי, אני לא מכיר את כל הבעיות השונות חוץ מבעברית. חקרת/מכיר את הנושא לעומק? לא חקרתי לעומק – כמו שאמרתי, חשבתי על זה קצת פעם; ובמקרה יצא שלפני זה למדתי קצת ערבית וקצת הולנדית. שי. ___ Discussions mailing list

[issue18009] os.write.__doc__ is misleading

New submission from Shai Berger: At least on posix systems, os.write says it takes a string, but in fact it barfs on strings -- it needs bytes. $ python Python 3.3.1 (default, May 6 2013, 16:18:33) [GCC 4.7.2] on linux Type help, copyright, credits or license for more information. import os

Re: זכר ונקבה ב־gettext

On Saturday 18 May 2013, Amir Eldor wrote: שלום, הבדל בין זכר לנקבה לא קיים ב־gettext. האם למישהו היה פעם עניין במימוש של תכונה כזו? כמה זה מסובך? חשבתי על זה קצת פעם. תלוי בהקשר שאליו אתה מתכוון – אם אתה מדבר על תרגום של פניות למשתמש\ת, כך שהבחירה נעשית תמיד על פי איזשהו פרמטר נגיש, זה

Re: django and paramstyle: what's the actual story?

On Thursday 16 May 2013, VernonCole wrote: > I noticed in a recent post that there is an outstanding patch for Oracle > for support of 'named' paramstyle. > As the author of that patch, I should probably clarify that it is a "format" style -- %(name)s -- not a "named" -- :name -- style. AFAIK,

Re: first() and last(), earliest() and latest()

Two notes: 1) I think it is better to leave the *args, **kw on the manager methods; since they are just forwarding to the qset anyways, there's no harm in that, and it makes them more "future proof" (i.e. you wouldn't need to change them next time you change the interface of the qset methods).

Re: Reminder: pending Oracle fixes and issues

Hi, Resurrecting a 4-month-old thread: On Sunday 20 January 2013 10:05:16 Anssi Kääriäinen wrote: > On 20 tammi, 02:52, Shai Berger <s...@platonix.com> wrote: > > Which still leaves two issues -- PR #393 (faster processign of numbers; I > > think I forgot to mention earli

Remote participation in sprints

Hi all, This saturday and sunday there are supposed to be sprints in DjangoCon EU in Warsaw. To my regret, I could not be present at the conference. However, I may be able to set aside the two days and participate in the sprint remotely. Will there be an effective way to do this while

Re: Perception of attitude in tickets

On Wednesday 15 May 2013, Luke Plant wrote: > > So I've gone ahead and created a wiki page, which can be longer and more > friendly, and require a shorter response on the actual ticket, something > like this: > > Closing as WONTFIX because ... > > If you want to persuade us otherwise,

Re: reconsider re-opening ticket 901

On Tuesday 14 May 2013, Alex Ogier wrote: > > It's a totally new behavior that has > plenty of corner cases such as foreign keys, and especially OneToOneFields. > Another one is initializers: get() or any other method of fetching an object from the database will call __init__() with the fields

Re: Perception of attitude in tickets

Hi Tom, On Monday 13 May 2013, Tom Evans wrote: > > You're not the only person who has time constraints, each of has a > choice of what we work on in our spare time. When I read these sorts > of tickets, perfectly valid feature requests knocked down for > precisely no reason, why should I waste

Re: Perception of attitude in tickets

Hi, On Monday 13 May 2013, Tom Evans wrote: > > Perhaps this wasn't clear, that was a member of your community trying > to make it happen. There have been several attempts over the past 5 > years by people trying to make it happen. Each time someone has tried > to make it happen, after the

Re: reconsider re-opening ticket 901

On Sunday 12 May 2013, Aymeric Augustin wrote: > On 12 mai 2013, at 10:24, Shai Berger <s...@platonix.com> wrote: > > Relatedly, we now cache back-references of 1-to-1 relations on the > > instance > > Django has cached them for a long time. It's just a bit more ef

Re: reconsider re-opening ticket 901

Hi, There's one minor issue that I'm not entirely clear of with this proposal: On Sunday 12 May 2013, Anssi Kääriäinen wrote: > > Concrete API proposal: Model.refresh() reloads all non-deferred local > field values (that is, all fields in the current model which have a > database column). In

Geeks... in... Space!!!!

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

Re: Triaging: Close as needsinfo

On Sunday 12 May 2013, Łukasz Rekucki wrote: > Hi, > > On 11 May 2013 22:58, Shai Berger <s...@platonix.com> wrote: > > In > > other communities, I have usually seen "needsinfo" as a ticket state, > > rather > > than a reason for closing; such

Re: reconsider re-opening ticket 901

[resend, reference included; sorrt for the noise] On Saturday 11 May 2013, Anssi Kääriäinen wrote: > > - While it might seem trivial to implement reload()/refresh() when > needed, Indeed, it might; which is why I would assume many people have already done it. For these people, a new

Re: reconsider re-opening ticket 901

On Saturday 11 May 2013, Anssi Kääriäinen wrote: > > - While it might seem trivial to implement reload()/refresh() when > needed, Indeed, it might; which is why I would assume many people have already done it. For these people, a new reload()/refresh() in core may go unnoticed or redundantly

Re: first() and last(), earliest() and latest()

Hi Selwin, On Saturday 11 May 2013, Selwin Ong wrote: > Hi everyone, > > I submitted a pull request implementing "first()" and "last()" here: > https://github.com/django/django/pull/1054 > > Comments welcome! > You implemented the "order_by" parameter as taking only one field name; this is

Triaging: Close as needsinfo

Hi Django devs, I would like to raise a little concern I ran into lately. When going over some Oracle-related tickets, I came across ticket #20201[0] . The ticket description was missing important details, so I commented about them. A few days later, Aymeric came around, and closed the ticket

Re: runserver fails on non-fatal model validation errors

Hi all, I've been going through what I've missed on the list, and found this 2-month- old message that seems to have gone unanswered. I'm sorry for being so late to the party, but... On Saturday 23 March 2013, Brendan Jurd wrote: > > I reported an issue with runserver on the django trac [1],

Re: Django 1.6 release timeline

On Tuesday 30 April 2013, Jacob Kaplan-Moss wrote: > Hi folks - > > Unless there are strong objections, here's what I'm thinking for the > Django 1.6 release timeline: > > Alpha: May 16 > Beta: June 20 > RC: Aug 1 > Final: as early as Aug 8, or later if more RCs are needed. > I see one issue

Re: design decisions for django-mssql: (switching on autocommit and remote proxy) advice wanted.

On Tuesday 30 April 2013, VernonCole wrote: > Dear knowledgeable persons: > > I have completed a beta-test version of a Linux remote access server for > adodbapi, and have started the process if integrating them into > django-mssql. (This is going to be an interesting experience for me -- I >

Re: Changing deferred model attribute behavior

Hi again, On Friday 26 April 2013, Anssi Kääriäinen wrote: > [...] > In almost every case it is better to try to minimize the amount of > queries than the amount of loaded fields. The cases where you have > deferred multiple fields, need only one of them later on, and there is > a field that you

Re: Changing deferred model attribute behavior

On Friday 26 April 2013, Alex Gaynor wrote: > Sorry, I misunderstood the original request. Yes, you're right Anssi and > Adrian, finding them on demand is reasonable. > Reasonable, but not entirely necessary for this. I have code that requires something like that; when it is time to "undefer"

Re: הגשת תלונה לממונה על הגבלים

On Tuesday 16 April 2013, Ori Idan wrote: 2013/4/16 Elad Alfassa e...@fedoraproject.org אתה טועה, אם הbootloader חתום עי מפתח משתמש שנמצא במאגר של הקושחה (ומשתמשים יכולים להוסיף לשם מפתחות) אז הוא ייטען אפילו אם הוא לא חתום עם מפתח של Verisign. גם ההבנה שלי היא שיש רק מפתח אחד ראשוני.

Re: הגשת תלונה לממונה על הגבלים

On Monday 15 April 2013, Ori Idan wrote: תיקון קטן. הסכום מועבר ל verisign דרך מיקרוסופט. אין למיטב ידיעתי דרך אחרת לרכוש חתימה. איזשהו reference? מה שאני הבנתי הוא שמיקרוסופט הפקידו מפתח בידי verisign, והללו מנהלים את כל העניינים וגובים את הכספים שלהם בעצמם. זה רע מאד שיש רק ספק אחד בעולם

Re: הגשת תלונה לממונה על הגבלים

On Monday 15 April 2013, Oron Peled wrote: On Monday 15 April 2013 12:25:52 Elad Alfassa wrote: טכנית גם אתה או עמותת המקור או כל אחד אחר יכול להקים CA משלו. אתם מוזמנים לעשות את זה. זה אפשרי אבל בעייתי בכמה מובנים: * אפיון המערכת מאפשר *רק* מפתח אחד (הממ... מעניין למה...) אני חושש

Re: הגשת תלונה לממונה על הגבלים

On Saturday 13 April 2013, Tzafrir Cohen wrote: אבל בוא ונבדוק על מה הוא מדווח בקישור הזה: קרן לינוקס כתבה טען בוט עם תמיכה ב־Secure Boot. חדשות מרעישות. נבדוק מה כתוב עליו באחד הקישורים מהכתבה: http://mjg59.dreamwidth.org/23113.html תרגום חופשי שלי: האם הטען הזה רצוי לשימוש

<    5   6   7   8   9   10   11   12   13   14   >