Re: GSOC 2015: Improving the less popular database backends

On Sunday 15 March 2015 03:45:16 Yichun Duan wrote: > Thank you. When you say "backend-provided tests", do you mean MySQL > scripts, Oracle scripts or something else like these? Or just some tests > based on django standard, which have marks to tell test runner the backend > they suite? > I mean

Re: GSoC 2015: Template engine optimisation

On Wednesday 11 March 2015 23:40:39 Oleksii Oleksenko wrote: >- Profiling > - run profiler (cProfile?) on all of these tests. As I see, basic > algorithm (pseudo code) will look like this: > > for context, template in zip(contexts, templates): > t = Template(template) > c

Re: Don't understand regex-urls and DetailView...

On Wednesday 11 March 2015 22:56:15 inoyon artlover KLANGRAUSCH wrote: > > url(r'^(P?\w+)$', views.ProductView.as_view()), > > Where is the mistake here That should be url(r'^(?P... The question mark before the P In the future, please direct questions about using Django to the

Re: inspectdb database defaults

On Tuesday 10 March 2015 19:39:19 Michael Manfre wrote: > I agree with Tim. > > I would support refactoring inspectdb so that it would be easier for anyone > to subclass the command and add additional logic to the introspection > process. +1. Shai.

Re: GSOC 2015: Improving the less popular database backends

One point which may be relatively easy and valuable is to get Django to support backend-provided tests, and do the final clean-up of backend-specific tests from the general test suite. That is, put all the postgres-specific tests somewhere in django.db.backends.postgresql_psycopg2 etc, and have

Re: Password validation in Django revisited

Hi Erik and all, The approach, indeed, seems fine, which is far from trivial. Some details, of course, still need to be worked out. I like Aymeric's suggestion re help_text -- I would take that one step further and allow every validator to give its own list of requirements. I have one

Re: A general way to batch SQL queries in Django

On Saturday 28 February 2015 23:05:56 Ram Rachum wrote: > > Here is what I'm currently thinking about: Can we make Django do multiple > separate queries (SQL queries are separated by a semicolon right? Sorry for > being a noob) and send them one after another before blocking on reading > any of

Re: אספות מקוונות

כמה נקודות עובדתיות: א. הדרישה לא היתה להראות כתיבה של קוד פתוח, אלא תרומה לקוד הפתוח. היסטורית, זה פורש בצורה די מרחיבה, וידוע לי רק על בקשה אחת שנדחתה אי פעם. ב. אף אחד לא גורש מהעמותה אף פעם. בפרט, עבור ידידים ההקפאה של המעמד על אי-תשלום היא חסרת משמעות לחלוטין (מאחר וממילא אין להם זכויות

Re: באגים בעברית ב־Wine

אני אראה איזה Wine יש לי בבית, אבל בכל מקרה, ההודעה הזו מתאימה יותר לרשימה הייעודית: http://hamakor.org.il/cgi-bin/mailman/listinfo/heb-bugzap אם וכאשר אעדכן, זה יהיה שם. שי. On Monday 23 February 2015 14:23:59 Yaron Shahrabani wrote: היי חברים, עבר זמן רב מאז התעסקתי ב־Wine ובבעיות התצוגה

Re: האם יש עדיין צורך בעמותת המקור

On Thursday 19 February 2015 20:43:30 Lior Kesos wrote: תוכלו להזכיר מה הבעיה להצביע מרחוק? בהצבעות הרלוונטיות, המתקיימות באסיפה הכללית, צריך לאמת את זהות המצביעים ברמת ודאות גבוהה למדי. מאחר ובאינטרנט אף אחד לא יודע שאתה כלב, הצבעה מרחוק דורשת מנגנון אימות לא טריויאלי. אם כל ההצבעות היו

Re: האם יש עדיין צורך בעמותת המקור

שניסינו להרים. אלי 2015-02-17 21:04 GMT+02:00 Shai Berger s...@platonix.com: אלי, On Tuesday 17 February 2015 19:11:11 E L wrote: אי ההסכמה היא על מובילה את הקהילה, עמותה אפורה ומשעממת שלא מובילה כלום והיא רק צינור כספי היא לא רלווטית. ההצעות שלי ושל נדב נועדו בדיוק למצב את

Re: המקור, לאן?

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

Re: האם יש עדיין צורך בעמותת המקור

אלי, On Tuesday 17 February 2015 19:11:11 E L wrote: אי ההסכמה היא על מובילה את הקהילה, עמותה אפורה ומשעממת שלא מובילה כלום והיא רק צינור כספי היא לא רלווטית. ההצעות שלי ושל נדב נועדו בדיוק למצב את העמותה כמובילה קהילתית. אתה שלחת מספר הודעות בפתילים של היומיים האחרונים, ובכולם קראת לעמותה

Re: המקור, לאן?

אלי, On Monday 16 February 2015 10:20:10 E L wrote: למה שמישהו יטרח לתרום לעמותה שבאופן מוצהר לא רוצה לעשות כלום חוץ מלשמש כצינור? כרגע זה לא „לא רוצה”. זה „לא מסוגלת”. הוועד צריך להיות מנהיג ומלהיב, ואנחנו נותרנו רק עם אנשים אפורים ומשעממים. תודה, גם אני אוהב אותך :) תעבירו את ההצעה של

Re: המקור, לאן?

On Sunday 15 February 2015 11:34:44 Meir Maor wrote: אני לא מבין מה המטרה בפירוק העמותה. הדבר היחיד שנחסך היא התקורה של החזקת עמותה, שהיא לא גבוהה במיוחד. בתיאוריה היא לא גבוהה במיוחד. בפרקטיקה, כאשר רמת הפעילות של חברי הועד מספיק נמוכה, נוצרים פערים שהופכים כל שטות לקשה. לכך מתלווה היסטוריה

Re: המקור, לאן?

On Sunday 15 February 2015 14:16:48 Omer Zak wrote: האם יש לעמותה הרבה כסף והאם יש צפי שייכנס לעמותה הרבה כסף שאינו קשור לפעילויות שהעמותה כיום אינה מארגנת? לעמותה יש היום מעט כסף. למעט דמי חבר והכנסות תלויות־פעילות, הכסף היחיד שצפוי להיכנס הוא תרומות ייעודיות (כמו למשל זו שקפלן הזכיר קודם

Re: Psycopg2 version support

Hi all, On Saturday 14 February 2015 22:53:13 Marc Tamlyn wrote: > > Django 1.8 will necessarily be the first version with a true minimum > requirement on psycopg2 version. Historically we have never documented a > required version. > FWIW, we have long had minimum requirements for other

Relations to non-trivial fields

Hi all, This comes from trying to fix #24343[1] -- a problem where a UUIDField is used as a PK (legitimate and common practice), and we wish to test a FK to that model. The problem is that, on database backends which do not support native UUIDFields (that is, all but postgres), the underlying

Re: המקור, לאן?

הי שוב כולם, תודה על התגובות הערות, על מלות העידוד, וגם על הביקורת. אי אילו נקודות עלו כאן, ואני רוצה להתייחס לכמה מהן. On Friday 13 February 2015 19:45:46 Lior Kaplan wrote: אני חושב שצריך לקבל החלטה עקרונית שהועד נשאר ברמת ניהול העמותה ולא עוסק בניהול האירועים השונים. הוא יספק תשתיות למי

המקור, לאן?

חברי וידידי המקור, בימים אלה אנו מתכוננים לכינוס אספה שנתית, בה אנחנו אמורים לבחור ועד וועדת ביקורת חדשים, לאשר דו״חות ולדון בפעילותנו השנה. כאחד מהצעדים לקראת זה, תישלח בקרוב לכל אחד מחברי העמותה הודעה על מצב תשלום דמי החבר שלו (לפי התקנון שלנו, מי שמפגר בתשלום דמי חבר מאבד את זכותו לבחור

Re: Adding missing aggregate functions to contrib.postgres ?

On Monday 09 February 2015 02:01:03 Russell Keith-Magee wrote: > > The only other thing I'd flag is that if any of these aggregates are recent > additions (e.g., added in Postgres 9), the failure mode for earlier > versions should be relatively clean. > Nitpick: Django 1.8 -- the first to have

Re: discontinue shipping tests with contrib apps?

On Monday 09 February 2015 17:38:27 Markus Holtermann wrote: > I'm +1 on moving the contrib tests to tests/_tests/ . > I'm +1 on preventing tests from being packaged with the contrib apps; I'm also +1 on moving them out of the app folders in the source -- +0 for the move's inherent value, but +1

Bug#777198: command-not-found: refers to wrong package for docker

Package: command-not-found Version: 0.2.38-1 Severity: normal Dear Maintainer, When I tried to run docker, I got this output: $ docker pull doesnt/matter The program 'docker' is currently not installed. To run 'docker' please ask your administrator to install the package 'docker' docker:

Re: resurrecting an old friend, whitespace in forms, #6362

On Wednesday 04 February 2015 11:00:50 Tom Christie wrote: > > it will be backwards incompatible for every Django installation out > > there, but also because throwing away data that the user actually entered > should be an opt-in, not opt-out behavior. > > If adequately called out I think

Re: Logout buttons no longer work

On Wednesday 04 February 2015 00:06:52 Brad Alexander wrote: What exactly happens when you try to logout? Nothing happens? Nothing. The menu doesn't even come up when I click the logout button in the tray, and when I click the K button and click Leave - Logout, nothing happens. This

Bug#735261: mutiple upstream bugs

On Monday 19 January 2015 00:54:41 Michael Gilbert wrote: On Sun, Jan 18, 2015 at 5:44 PM, Shai Berger wrote: I am asking about serious vs. non-serious because those are the terms used by reportbug (non-serious data loss is a reason to mark a bug grave). Both grave and critical refer

Bug#735261: mutiple upstream bugs

On Monday 19 January 2015 00:54:41 Michael Gilbert wrote: On Sun, Jan 18, 2015 at 5:44 PM, Shai Berger wrote: I am asking about serious vs. non-serious because those are the terms used by reportbug (non-serious data loss is a reason to mark a bug grave). Both grave and critical refer

Bug#735261: mutiple upstream bugs

On Sunday 18 January 2015 23:51:01 Michael Gilbert wrote: On Sun, Jan 18, 2015 at 4:14 PM, Shai Berger s...@platonix.com wrote: Those easily recreatable bits represent a significant part of my mail workflow. Almost any data can be recreated by repeating the work that created it. Your claims

Bug#735261: mutiple upstream bugs

On Sunday 18 January 2015 23:51:01 Michael Gilbert wrote: On Sun, Jan 18, 2015 at 4:14 PM, Shai Berger s...@platonix.com wrote: Those easily recreatable bits represent a significant part of my mail workflow. Almost any data can be recreated by repeating the work that created it. Your claims

Bug#735261: mutiple upstream bugs

On Sunday 18 January 2015 21:46:52 Michael Gilbert wrote: On Fri, Jan 16, 2015 at 8:07 AM, Shai Berger wrote: On Friday 16 January 2015 01:45:53 Michael Gilbert wrote: However, the problem reported here is not a usability problem. If a mail client losing record of which mails have been

Bug#735261: mutiple upstream bugs

On Sunday 18 January 2015 21:46:52 Michael Gilbert wrote: On Fri, Jan 16, 2015 at 8:07 AM, Shai Berger wrote: On Friday 16 January 2015 01:45:53 Michael Gilbert wrote: However, the problem reported here is not a usability problem. If a mail client losing record of which mails have been

Bug#735261: mutiple upstream bugs

On Friday 16 January 2015 01:45:53 Michael Gilbert wrote: However, the problem reported here is not a usability problem. If a mail client losing record of which mails have been read and which haven't isn't non-serious data loss, I can't tell what is. Actual data loss. So, the bits

Bug#735261: mutiple upstream bugs

On Friday 16 January 2015 01:45:53 Michael Gilbert wrote: However, the problem reported here is not a usability problem. If a mail client losing record of which mails have been read and which haven't isn't non-serious data loss, I can't tell what is. Actual data loss. So, the bits

Bug#735261: mutiple upstream bugs

Hi Michael, On Wednesday 14 January 2015 04:45:16 Michael Gilbert wrote: This is a usability problem, so it doesn't really qualify as release critical. Debian developers get to call the severity of bugs in general, and the criticality for a specific release in particular. However, the

Bug#735261: mutiple upstream bugs

Hi Michael, On Wednesday 14 January 2015 04:45:16 Michael Gilbert wrote: This is a usability problem, so it doesn't really qualify as release critical. Debian developers get to call the severity of bugs in general, and the criticality for a specific release in particular. However, the

Bug#727800: kmail: KMail goes bonkers following Qt update

So, I've tried again, this time restarting Akonadi when the migration script said it was done. I tried two variations: 1) akonadictl restart before pressing ok on the window showing the kmail resource migration. Surprisingly, this did not cause KMail to shut down. It also didn't really work --

Bug#727800: kmail: KMail goes bonkers following Qt update

So, I've tried again, this time restarting Akonadi when the migration script said it was done. I tried two variations: 1) akonadictl restart before pressing ok on the window showing the kmail resource migration. Surprisingly, this did not cause KMail to shut down. It also didn't really work --

Bug#727800: kmail: KMail goes bonkers following Qt update

So, I've tried again, this time restarting Akonadi when the migration script said it was done. I tried two variations: 1) akonadictl restart before pressing ok on the window showing the kmail resource migration. Surprisingly, this did not cause KMail to shut down. It also didn't really work --

Re: intended security model for templates

On Wednesday 24 December 2014 20:35:09 Tim Graham wrote: > I was hoping to get clarification on what security model we intend to > support for template authors. In ticket #12772 > it's proposed to allow > loading template tags using a dotted Python

Re: Bypassing 1.7+ migrations

Hi Markus, On Thursday 18 December 2014 08:54:30 Markus Holtermann wrote: > > manage=False won't gain you anything, since those models will still show > up in migrations, because they need to be able to be referenced by > managed models. The migration database operations are noops though. > As

Re: Bypassing 1.7+ migrations

FWIW, the approach I would go for is to try to monkeypatch managed=False into the base model Meta. Shai. On Tuesday 16 December 2014 14:49:25 Andrew Godwin wrote: > Hi Marcin, > > You can't bypass migrations as much as you can't bypass syncdb; that is, > the commands are separate and you can

annotate() and generic relations

Hi everyone, First, there was ticket #10461[1] -- a complaint that annotate doesn't work well with generic relations. Then, it was documented[2] as not working. But then, people continued looking at the ticket, and in the end, it was declared as fixed and a test was added[3]. But deeper

Bug#727800: kmail: KMail goes bonkers following Qt update

On Sunday 14 December 2014 21:35:45 Diane Trout wrote: The migration bug is the one kmail bug I've been able to reproduce repeteadly. I have a work-around patch that basically does akonadictl restart when the migrator says Migration Done Oh, I haven't followed that advice. I'll try

Bug#727800: kmail: KMail goes bonkers following Qt update

On Sunday 14 December 2014 21:35:45 Diane Trout wrote: The migration bug is the one kmail bug I've been able to reproduce repeteadly. I have a work-around patch that basically does akonadictl restart when the migrator says Migration Done Oh, I haven't followed that advice. I'll try

Re: Bug#727800: kmail: KMail goes bonkers following Qt update

reproducibility, because (I think) the root cause is extreme sensitivity to anything being slightly off in the environment; and go figure which combination of factors, exactly, causes which undesired behavior. On Monday, December 15, 2014 01:21:18 Shai Berger wrote: A little off-topic, w.r.t

Bug#727800: kmail: KMail goes bonkers following Qt update

On Sunday 14 December 2014 21:35:45 Diane Trout wrote: The migration bug is the one kmail bug I've been able to reproduce repeteadly. I have a work-around patch that basically does akonadictl restart when the migrator says Migration Done Oh, I haven't followed that advice. I'll try

Bug#727800: kmail: KMail goes bonkers following Qt update

Finally got to it. The upgrade was not smooth at all; the update script ended quickly enough, but the real upgrade only happened when I opened KMail. I had the same experience as last time -- KMail shows blank folders, nothing seems to be going on, except if you look for it. At some point

Bug#727800: kmail: KMail goes bonkers following Qt update

Finally got to it. The upgrade was not smooth at all; the update script ended quickly enough, but the real upgrade only happened when I opened KMail. I had the same experience as last time -- KMail shows blank folders, nothing seems to be going on, except if you look for it. At some point

Bug#727800: kmail: KMail goes bonkers following Qt update

Finally got to it. The upgrade was not smooth at all; the update script ended quickly enough, but the real upgrade only happened when I opened KMail. I had the same experience as last time -- KMail shows blank folders, nothing seems to be going on, except if you look for it. At some point

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Well. Logoff, logon, and inbox is back to normal behavior (double-clicking the message in the list opens it for reading, not editing). Sent-mail is still exactly as described. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#772612: not reproducable

Hi, On Sat, 13 Dec 2014 12:37:23 +0100 Sandro =?ISO-8859-1?Q?Knau=DF?= b...@sandroknauss.de wrote: I would suggest you test with a clean user and/or check all identities. It sounds like one identity uses the sent folder as outbox. There is no UI way to set the outbox for an identity; one

Re: Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Well. Logoff, logon, and inbox is back to normal behavior (double-clicking the message in the list opens it for reading, not editing). Sent-mail is still exactly as described. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#772612: not reproducable

Hi, On Sat, 13 Dec 2014 12:37:23 +0100 Sandro =?ISO-8859-1?Q?Knau=DF?= b...@sandroknauss.de wrote: I would suggest you test with a clean user and/or check all identities. It sounds like one identity uses the sent folder as outbox. There is no UI way to set the outbox for an identity; one

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Well. Logoff, logon, and inbox is back to normal behavior (double-clicking the message in the list opens it for reading, not editing). Sent-mail is still exactly as described. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#772612: not reproducable

Hi, On Sat, 13 Dec 2014 12:37:23 +0100 Sandro =?ISO-8859-1?Q?Knau=DF?= b...@sandroknauss.de wrote: I would suggest you test with a clean user and/or check all identities. It sounds like one identity uses the sent folder as outbox. There is no UI way to set the outbox for an identity; one

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Hi, On Tuesday 09 December 2014 11:12:42 Diane Trout wrote: Hello, I tried to duplicate this with 4.14.1. I had to hit T in order to actually edit the message, and then if I make a change and save it, the save button says Save to Draft, for me the modified message moved to the Drafts

Re: Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Hi, On Tuesday 09 December 2014 11:12:42 Diane Trout wrote: Hello, I tried to duplicate this with 4.14.1. I had to hit T in order to actually edit the message, and then if I make a change and save it, the save button says Save to Draft, for me the modified message moved to the Drafts

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Hi, On Tuesday 09 December 2014 11:12:42 Diane Trout wrote: Hello, I tried to duplicate this with 4.14.1. I had to hit T in order to actually edit the message, and then if I make a change and save it, the save button says Save to Draft, for me the modified message moved to the Drafts

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Package: kmail Version: 4:4.14.2-2 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Double-click a message in any folder; unlike in kmail1, the message opens as editable (in kmail1 this was only true for Outbox). However, if the message is opened from the sent-mail

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Package: kmail Version: 4:4.14.2-2 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Double-click a message in any folder; unlike in kmail1, the message opens as editable (in kmail1 this was only true for Outbox). However, if the message is opened from the sent-mail

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

Package: kmail Version: 4:4.14.2-2 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Double-click a message in any folder; unlike in kmail1, the message opens as editable (in kmail1 this was only true for Outbox). However, if the message is opened from the sent-mail

Re: Experimental APIs DEP

I like the general idea of experimental API, although Carl and Aymeric's notes are important: If we do this, we need to very picky in its use, or else it just becomes an easy route to avoid committment. In particular, there should be a hard-and-fast rule that nothing should be made an

Bug#760707: Workaround: Restart Akonadi

Package: kmail Version: 4:4.14.2-2 Followup-For: Bug #760707 Dear Maintainer, I have recently experienced the send side of the above report, repeatedly. This may be related to the fact that I tend to leave my KDE session open for days -- I think that crossing midnight triggers tris, but I may be

Bug#760707: Workaround: Restart Akonadi

Package: kmail Version: 4:4.14.2-2 Followup-For: Bug #760707 Dear Maintainer, I have recently experienced the send side of the above report, repeatedly. This may be related to the fact that I tend to leave my KDE session open for days -- I think that crossing midnight triggers tris, but I may be

Bug#727800: kmail: KMail goes bonkers following Qt update

Hi, On Wednesday 26 November 2014 15:21:15 you wrote: Hi! As Sandro pointed out, this seems fixed in newer versions. Can you please test if this is still an issue for you? I have no means to reconstruct the update as it was. I am using two systems: One of them is a sid which I keep

Bug#727800: kmail: KMail goes bonkers following Qt update

Hi, On Wednesday 26 November 2014 15:21:15 you wrote: Hi! As Sandro pointed out, this seems fixed in newer versions. Can you please test if this is still an issue for you? I have no means to reconstruct the update as it was. I am using two systems: One of them is a sid which I keep

Bug#727800: kmail: KMail goes bonkers following Qt update

Hi, On Wednesday 26 November 2014 15:21:15 you wrote: Hi! As Sandro pointed out, this seems fixed in newer versions. Can you please test if this is still an issue for you? I have no means to reconstruct the update as it was. I am using two systems: One of them is a sid which I keep

Re: DB Migrations: Proposed fix for "Index name collisions after objects are renamed then re-created"

Hi, Just noted this thread, and I have two points: 1) Using the migration name in the index isn't really "predictable", and isn't even completely stable (the name changes when migrations are squashed), unless I'm missing something. 2) The current practice of identifying indexes by the columns

Re: Configurable safety options for high performance Django systems

Hi Rick, On Sunday 23 November 2014 14:11:13 Rick van Hattem wrote: > > So please, can anyone give a good argument as to why any sane person would > have a problem with a huge default limit which will kill the performance of > your site anyhow but isn't enough to kill the entire system? >

Re: [Python-il] [pyweb-il:4286] pdb talk

On Friday 21 November 2014 21:37:22 Dotan Cohen wrote: Thanks. I also noticed that the course description does in fact mention Python, as in build several automated debugging tools in Python. It doesn't mention that the tools are for debugging Python code, though I suppose that is implicit.

Re: Backend-specific lookups

I just wanted to drop a line here saying "it will take me another couple of days to deal with this". On one hand, I want to wait with this for Marc's work to land. On the other, there are more urgent issues even in Oracle-land (the broken Py3 tests). And yes, I'm with Anssi on removing

Re: Q: How to correct monitor resolution?

On Monday 17 November 2014 22:16:56 D. R. Evans wrote: D. R. Evans wrote on 11/17/2014 12:43 PM: I just installed KDE debian wheezy 7.7 on a new system, and the monitor size is being reported by KDE system settings as 1280 x 1024 (0.0 Hz). The same resolution appears to be being used for

Backend-specific lookups

Hi, I'v been working on an old Oracle bug[1], and realized that a nice way to solve it would be by overriding some builtin lookups with custom lookups for Oracle. However, I had some doubts about where to place the code: On the one hand, I could just add an "as_oracle()" to the builtin lookup

טוב, בחזית הזאת ניצחנו

http://news.microsoft.com/2014/11/12/microsoft-takes-net-open-source-and-cross-platform-adds-new-development-capabilities-with-visual-studio-2015-net-2015-and-visual-studio-online -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.___

Bug#735261: kmail2 randomly marks read messages as unread

On Saturday 01 November 2014 00:34:56 Scott Kitterman wrote: KMail randomly marks single messages as unread. This makes my normal workflow, where I leave messages unread for later, deeper consideration, tedious and bordering on impossible. KMail also randomly creates new duplicates

Bug#735261: kmail2 randomly marks read messages as unread

On Saturday 01 November 2014 00:34:56 Scott Kitterman wrote: KMail randomly marks single messages as unread. This makes my normal workflow, where I leave messages unread for later, deeper consideration, tedious and bordering on impossible. KMail also randomly creates new duplicates

Bug#735261: kmail2 randomly marks read messages as unread

On Saturday 01 November 2014 00:34:56 Scott Kitterman wrote: KMail randomly marks single messages as unread. This makes my normal workflow, where I leave messages unread for later, deeper consideration, tedious and bordering on impossible. KMail also randomly creates new duplicates

Re: Unicode SlugField design decision (#16501)

On Wednesday 05 November 2014 17:29:20 Michael Manfre wrote: > We can change the internal type of SlugField for option 1 based upon > whether or not the field should be unicode. Whether or not an existing > backend stores SlugField in an ascii char datatype shouldn't dictate > whether we go with

Re: Setting database default values in migrations (postgres)

On Friday 31 October 2014 19:16:15 Jon Dufresne wrote: > On Fri, Oct 31, 2014 at 9:46 AM, Andrew Godwin wrote: > > So, bear in mind that you can easily set these defaults yourself in a > > migration with RunSQL if you need them for legacy purposes; that way > > they'll get

Re: Django's problem with db-level defaults on Oracle

On Saturday 01 November 2014 11:55:26 Kääriäinen Anssi wrote: > Quick question: could django set the default to to_date('2014-31-01', > '-mm-dd')? Yes, apparently we could, and it would solve the problem I described earlier, thanks. If we decide to start using defaults in the database (which

Django's problem with db-level defaults on Oracle

Hi Everyone, I just mentioned in another thread that db-level defaults are particularly troublesome on Oracle. I didn't want to burden that discussion with the detais, but having been asked about it on IRC (thanks Josh), here they are. The problem is caused by a combination of factors: 1)

Re: Setting database default values in migrations (postgres)

On Thursday 30 October 2014 23:00:18 Andrew Godwin wrote: > > If this does happen, I'd probably want some way to declare what defaults to > keep. (South actually used to have this with a keep_default option on the > add_column method but it was kind of unmaintained) > IIRC, in the few South

Re: sys.exit(1) from makemigrations if no changes found

On Thursday 30 October 2014 15:22:01 Dan Poirier wrote: > Wouldn't enabling this by default cause a problem for any automated > deploys? The discussion is about the makemigrations command, not migrate. The OP wants to use it to find automatically if there are model changes not covered by

Re: Overwrite mode in collectstatic

I agree with Tim completely. I do see one thing that could help here: Add a check that STATIC_ROOT is not a subfolder of any app. This check cannot be really reliable (that is, a particularly careless and unlucky user could set things up so that their STATIC_ROOT is in an app but the check

Re: cursor.callproc()

On Thursday 23 October 2014 06:14:19 Carl Meyer wrote: > > On Oct 22, 2014, at 5:56 PM, Shai Berger <s...@platonix.com> wrote: > >> On Wednesday 22 October 2014 19:35:49 Carl Meyer wrote: > >>> On 10/21/2014 04:04 PM, Shai Berger wrote: > >>> I'd argu

Re: cursor.callproc()

Hi Carl, On Wednesday 22 October 2014 19:35:49 Carl Meyer wrote: > On 10/21/2014 04:04 PM, Shai Berger wrote: > > I'd argue that in the common case, the user shouldn't care if the > > function they are calling is implemented in Python or Procedural SQL > > (assuming it

Re: Why doesn't ModelChoiceField.queryset support slicing?

On Wednesday 22 October 2014 10:50:51 Marc Tamlyn wrote: > > As for a work around, using a ChoiceField directly shouldn't be > particularly difficult in this case. ModelChoiceField has some nice > features but it is limited. > Using a ChoiceField as a substitute for ModelChoiceField isn't hard,

Re: cursor.callproc()

On Monday 20 October 2014 21:26:50 Carl Meyer wrote: > Hi Marc, > > On 10/19/2014 12:54 AM, Marc Tamlyn wrote: > > I guess now with migrations we have a nice way of running the SQL > > against the database to create the stored procedures. > > > > However if we plan to make this a public API, it

Re: cursor.callproc()

On Tuesday 21 October 2014 18:23:44 Chris Foresman wrote: > Is there some benefit to using `.callproc()` over this? > > ``` python > query = 'CALL sp_recommendation_engine(%s, %s)' > profile = user.get_profile() > cursor = connection.cursor() > cursor.execute(query, [user.id,

Re: cursor.callproc()

On Monday 20 October 2014 00:38:52 Marc Tamlyn wrote: > I was thinking in the context of a project - creating a procedure to use in > the code. Oh, I see. Your API suggestion is also perfect for that use. > Naturally cursor.execute() is perfectly fine for tests, which > would need to be backend

Re: Django Get Related with Multiple Models

Hi Ronaldo, This forum is dedicated to discussions about the development *of* Django; for questions about development *with* Django, please use the django-users list. Thanks, Shai. -- You received this message because you are subscribed to the Google Groups "Django developers

Re: cursor.callproc()

ke its siblings execute(), fetchone() etc; that is why I am not even suggesting to modify it to the obvious callproc(procname, *args, **kwargs). Cursor.execute() is documented, public API -- are there reasons to deny callproc() the same status? Shai. > On 19 October 2014 00:25, Shai Berge

cursor.callproc()

Hi all, For a very long time -- as far as I'm aware, forever -- we've had, in our cursor classes, a "callproc()" method that follows the callproc() definition of pep249[1]; this allows database stored procedures to be called. Recently, we've had a ticket[2] and PR[3] to enhance this method --

Re: A new approach for migrations?

Hi Uri, On Friday 17 October 2014 01:30:10 Uri P wrote: > Thanks Andrew for enlightening me. That was helpful. > > Anyway, for me personally, data migration is the easiest part, I can do it > in a heartbeat by a simple script. > In contrary, solving circular dependencies seems to be very

Bug#764705: postgresql-9.4: ERROR: The database format changed between beta 2 and 3. Please dump, but how?

Package: postgresql-9.4 Followup-For: Bug #764705 Dear Maintainer, I, like a previous poster, have this: postgres@deblack:~$ pg_lsclusters Ver Cluster Port Status OwnerData directory Log file 9.3 main5432 online postgres /var/lib/postgresql/9.3/main

Re: kmail email filtering only works sometimes

On Tuesday 14 October 2014 11:42:53 Kevin Krammer wrote: On Monday, 2014-10-13, 16:41:58, john Culleton wrote: When the switch was made from KDE3.5 to KDE4 I struggled with KDE and kmail for a while but ultimately adopted the XFCE GUI and also Claws Mail. Thus far I have seen no

[Pkg-postgresql-public] Bug#764705: postgresql-9.4: ERROR: The database format changed between beta 2 and 3. Please dump, but how?

Package: postgresql-9.4 Followup-For: Bug #764705 Dear Maintainer, I, like a previous poster, have this: postgres@deblack:~$ pg_lsclusters Ver Cluster Port Status OwnerData directory Log file 9.3 main5432 online postgres /var/lib/postgresql/9.3/main

Re: kmail email filtering only works sometimes

On Friday 10 October 2014 15:10:05 Brad Alexander wrote: I am using kmail (through kontact) for my work email, and everr since I upgraded to 4.14.1-1, mail filtering has been hit or miss. At times, you have to right click on a message and click apply all filters, and it will properly apply the

Re: South's --update equivalent for Django 1.7 migrations

On Thursday 09 October 2014 09:53:44 Andrew Godwin wrote: > > The logic is not too complex, but the feature would need to be > dependency-aware and delete any migrations that depended on the updated > migration before it re-ran makemigrations; in addition, if no migration > name is provided (as

Re: RFC: "UPSERT" in PostgreSQL

On Sunday 28 September 2014 09:33:06 Simon Riggs wrote: > On 28 September 2014 02:22, Shai Berger <s...@platonix.com> wrote: > > Upon reading the docs, I was a little surprised to see that in terms of > > triggers etc, the operation is always considered an INSER

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