I'd like to add support for fixture load/dump to deal with compressed
(gzip) files transparently.
# django-admin.py dumpdata --compress > foo.json.gz
# django-admin.py loaddata foo #looks for foo.json, foo.json.gz, etc.
# django-admin.py syncdb #looks for initial_data.json,
initial_data.json.gz,
On Wed, Sep 17, 2008 at 12:11 PM, zvoase <[EMAIL PROTECTED]> wrote:
...
> I'll post soon. For the meantime, take a look at http://dpaste.com/hold/78671/
That won't do what you want, since the "raise" on line 13 will prevent
line 14 from executing.
I agree, you seem to want process_exception.
--
On Wed, Sep 17, 2008 at 6:30 PM, zvoase <[EMAIL PROTECTED]> wrote:
>
> Sorry, here: http://dpaste.com/hold/78774/
>
> On Sep 18, 1:29 am, zvoase <[EMAIL PROTECTED]> wrote:
>> Yeah, that's it, process_exception is *definitely* what I need :)
>> But as for the idea, how do you feel about it?
>> By t
Note that in some cases, dynamic imports are done to avoid loading a
Django subsystem, large external library, or optional dependency until
it is strictly necessary.
There are certainly still examples where none of those good reasons
apply.
On Sep 24, 2008, at 2:37 AM, David Cramer <[EMAIL
On Wed, Oct 15, 2008 at 3:58 PM, Jesse Young <[EMAIL PROTECTED]> wrote:
...
> I was thinking it would be useful to add a setting like
> EXCEPTION_NOTIFIER = 'path.to.custom.notifier' , where the default
> would look something like this:
>
> def mail_exception_to_admins(request, exc_info):
>
On Wed, Oct 15, 2008 at 6:26 PM, Jesse Young <[EMAIL PROTECTED]> wrote:
>
> I see there is a got_request_exception signal already... so one could
> effectively do the same thing by adding a signal handler and making
> settings.ADMINS the empty list so that mail_admins effectively becomes
> a no-op
On Tue, Dec 6, 2005 at 9:37 AM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
...
> Looks like vary_on_get is the most popular choice. So here's how that
> might work:
>
> @vary_on_get('id')
> def my_view(request):
>id = request.GET.get('id', None)
To be clear, the generated cache key would stil
On Sat, Nov 1, 2008 at 8:32 PM, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> On Nov 2, 2:52 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>> Assuming vary_on_get() with no parameters means no variance (other
>> than the HTTP Vary headers), then [...]
>
On Tue, Nov 18, 2008 at 9:20 PM, Nathaniel Whiteinge
<[EMAIL PROTECTED]> wrote:
>
> On Nov 18, 5:43 pm, Ludvig Ericson <[EMAIL PROTECTED]> wrote:
>> Isn't that a generic view?
>
> Yes. It's built into Django and already does exactly what some people
> want render_to_response to do, so why all the
On Thu, Nov 20, 2008 at 6:19 AM, zvoase <[EMAIL PROTECTED]> wrote:
...
> # Using RequestContext
> def myview(request, *args):
># some code here...
>request.render('template_name.html', {...})
...
>
> That just seems logical to me. Rather than (potentially) break
> backwards compatibility,
On Tue, Nov 25, 2008 at 10:34 AM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> The biggest issue is that we can't edit anything. There's no "Edit
> Page" button, and when I manually add "?action=edit" to the URL, it
> gives me an editor form, but upon submission, I see the culprit: 403
> Forbidden (
It seems like cache keys need to be created using various
cross-cutting bits of data. As an example, maybe I have localized
data, and any caching should include the requestor's locale, but also
the content type / object ID, and maybe some other consumer
differentiation.
This sort of key generat
On Fri, Nov 28, 2008 at 7:15 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> I'd be -1, that would mean storing some sort of global(thread local
> probably) instance of the request, plus any other object that you'd
> want to cache on. And that just seems like a bad idea. There's no
> reason
On Sun, Dec 7, 2008 at 8:55 AM, Calvin Spealman <[EMAIL PROTECTED]> wrote:
>
> Using the caching api backed by memcache, i started hitting the 1MB
> object size limit of memcache and I was thinking of a way around it by
> storing a list of keys to segments of the full object, each up to 1MB
> each
On Wed, Dec 10, 2008 at 3:04 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> To be perfectly honest, I'm +1 on a solution. I didn't realize this
> was happening either.
>
> Time to monkey-patch QuerySet's delete() method :)
>
> (I'm also a bit curious as to how its handling cascades in MySQL when
On Thu, Dec 11, 2008 at 10:49 AM, oggie rob <[EMAIL PROTECTED]> wrote:
>
> On Dec 10, 6:25 am, AcidTonic <[EMAIL PROTECTED]> wrote:
>> I'm building an application to track IP addresses on many corporate
>> networks with a single subnet having around 65535 rows for IP
>> addresses. Now this app
On Thu, Dec 11, 2008 at 12:06 PM, sed...@gmail.com wrote:
...
> As of r8165 of Django (post qs-refactor), model_instance.delete() does
> *not* null out instances with nullable foreign keys that point to the
> about-to-be deleted instance. It deletes them instead. We have a
> special field calle
We've locally implemented an asynchronous mailing system and made it
have the same function signatures.
So .mail has all the same function names and signatures
as django.core.mail.
Since sending email can block for an arbitrarily long time, I'd like
to make it so that when an exception occurs in
On Tue, Dec 16, 2008 at 3:44 PM, Jacob Kaplan-Moss
wrote:
>
> On Tue, Dec 16, 2008 at 11:56 AM, Jeremy Dunck wrote:
>> Since sending email can block for an arbitrarily long time, I'd like
>> to make it so that when an exception occurs in
>> django.core.handlers.b
On Tue, Dec 16, 2008 at 6:53 PM, Malcolm Tredinnick
wrote:
...
> You only have to override the handle_uncaught_exception() method --
> that's where the mailing is restricted to.
Bah, that's what I get for looking at my pre-1.0 django rev. Sorry
for the noise. :-(
--~--~-~--~~-
On Wed, Dec 17, 2008 at 11:14 AM, samira wrote:
>
> I active admin site for Django 1.0.2, it is correct on my local, but I
> see below error on server:
>
> emplateSyntaxError at /site/admin/
>
> Caught an exception while rendering: Tried activateAccount in module
> site.site_app.views. Error was:
Aquí está una lista para preguntas en español:
http://groups.google.com/group/django-es
Bueno,
Jeremy
On Mon, Jan 12, 2009 at 2:15 PM, Patrick Taylor wrote:
>
> Por favor, disculpame por mi Español, msmtotti.
>
> Esta lista es dedicada a el developmento de Django mismo, la lista que
> tu quie
On Tue, Jan 13, 2009 at 6:45 AM, Alex Gaynor wrote:
>
>
> On Tue, Jan 13, 2009 at 7:40 AM, Russell Keith-Magee
> wrote:
>> Can anyone shed any light on the workaround for this? Is the only
>> solution to rewrite the test so that it doesn't depend on the output
>> format of __repr__?
>>
>> Y
I'd like to do some processing any time a flatpage is requested.
I can accomplish this by using a view middleware and testing for the
resolved view, but it seems a like a signal would be useful so I could
have a reference to the flatpage object itself.
Any opposition to the idea?
--~--~
On Tue, Feb 17, 2009 at 6:40 AM, NitinHayaran wrote:
>
> Hi All,
> Today i read this article and was wondering whether django orm is
> really that bad.
>
> http://dayhacker.blogspot.com/2009/02/why-django-orm-sucks-it-takes-hell-lot.html
>
> I think this is the right place to ask?
This seems to
On Tue, Feb 17, 2009 at 3:12 PM, Jeremy Dunck wrote:
> Even so, it seems like it'd be useful to have a built-in filter which
> uses iter(object)?
>
> {% for question in poll.questions.all()|iterate %}
Ugh.
Sorry, I'm an idiot.
{% for question in poll.questions.all.itera
On Tue, Feb 17, 2009 at 2:11 PM, Alex Gaynor wrote:
...
>
> Neither is completely correct ;). Both do chunked reads from the
> DB(__iter__ using iterator for getting the data), however __iter__ also
> caches them, so if you reiterate you don't do a second db query, whereas
> iterator doesn't cac
On Tue, Feb 17, 2009 at 3:15 PM, Jeremy Dunck wrote:
...
> {% for question in poll.questions.all.iterator %}
> works just fine.
>
OK, last one from me.
As a 2.0 wish, I'd like to make .iterator the default behavior, and
the cached-version a special case. I realize this
On Tue, Feb 17, 2009 at 3:52 PM, James Bennett wrote:
>
> On Tue, Feb 17, 2009 at 7:40 AM, NitinHayaran wrote:
>> Today i read this article and was wondering whether django orm is
>> really that bad.
>>
>> http://dayhacker.blogspot.com/2009/02/why-django-orm-sucks-it-takes-hell-lot.html
>
> Well
On Tue, Feb 17, 2009 at 6:49 PM, Malcolm Tredinnick
wrote:
...
> I'd be somewhat against this, I think. It's *very* easy to reuse
> querysets and inadvertently cause extra database queries.
...
> we're trading memory
> usage for speed and ease of use (and providing a way to improve the
> former i
On Tue, Feb 17, 2009 at 7:13 PM, Malcolm Tredinnick
wrote:
...
>> if settings.DEBUG and self.prior_iteration:
>>warnings.warn("dope!")
>
> This certainly sounds reasonable and doable today without any real
> overhead. Go ahead and make a patch/ticket.
OK.
Do you think there should be a Perf
The Django docs for TransactionMiddleware state:
"When a request starts, Django starts a transaction. If the response
is produced without problems, Django commits any pending
transactions."
This is apparently not actually true.
I have some code using cursor.execute while doing no operations usin
On Fri, Mar 6, 2009 at 9:34 AM, Karen Tracey wrote:
> On Fri, Mar 6, 2009 at 10:28 AM, Jeremy Dunck wrote:
>>
>> The Django docs for TransactionMiddleware state:
>> "When a request starts, Django starts a transaction. If the response
>> is produced without prob
On Tue, Mar 10, 2009 at 11:12 AM, Vinicius Mendes wrote:
...
> What do you think in saving the author value in the blog instance if it is
> achieved through the author instance? It's something like telling blog who
> is his author in the moment you are retrieving it from the author.
You're descr
On Fri, Mar 13, 2009 at 7:55 AM, Shai Berger wrote:
...
> Or has some other solution surfaced lately for distributed transactions?
A big fat documentation warning and careful selection of distribution strategy?
--~--~-~--~~~---~--~~
You received this message beca
On Sat, Mar 14, 2009 at 6:33 PM, Rodrigo Guzman wrote:
...
> So, it seems like it'd be a straight forward change to
> django.core.context_processors.debug to implement it. However, it
> seems that this functionality would be better placed in the settings
> module.
Django only uses INTERNAL_IPS
On Sat, Mar 14, 2009 at 11:05 PM, Alex Gaynor wrote:
...
> Why are you subclassing list if you're going to just add a cidrs attr that's
> the list :)
I'm handling INTERNAL_IPS which are multiple CIDR blocks. I could
have constructed with [IP('...'),IP('...')], but that's tomayto
tomahto. __con
Yeah, dumb bug. :)
On Mar 15, 2009, at 4:12 PM, Ludvig Ericson
wrote:
>
> On Mar 15, 2009, at 05:02, Jeremy Dunck wrote:
>
>> class CIDR_LIST(list):
>> def __init__(self, cidrs):
>> from IPy import IP
>> self.cidrs = []
>>
On Thu, Mar 19, 2009 at 4:20 PM, Jacob Kaplan-Moss
wrote:
...
>
> /me looks meaningfully at Justin.
FWIW, I've been a terrible contributor on GIS. All praise to Justin's
great work.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
I have a need for dynamic URL definition, but I see that
RegexURLResolver.reverse uses a cache, _reverse_dict.
Option 1):
Make a RegexURLResolver subclass which sets _reverse_dict back to
an empty MultiValueDict when a URL is added or removed
Option 2)
Make me do it in my app ;-)
Which do
Malcolm, Jacob pointed me at you, since the code in question was a
commit around QSRF-time.
I'm aware of ticket #7539, but would prefer to keep the scope narrower
and ask the hopefully-useful question-- is #9308 a bug? If so, I'd
like to close it for 1.1.
In summary, #9308 describes a situation
Hey all, I was considering putting on a Dallas sprint for 1.1. I'm
not sure exactly when 1.1 will ship, but soon-ish, so I was thinking
about trying to make the sprint the weekend of 4/10 (Easter weeked) or
4/17.
Any preference? Who can make it or will consider making it?
--~--~-~--~--
Gary, Justin?
On Fri, Apr 3, 2009 at 9:47 AM, Alex Robbins
wrote:
>
> I live in the Dallas area and would be interested in coming, whenever
> it happens.
>
> On Apr 2, 12:45 pm, Jeremy Dunck wrote:
>> Hey all, I was considering putting on a Dallas sprint for 1.1. I'
We've firmed up the Dallas Django sprint plans:
Django 1.1 is around the corner, but there are lots of bugs left to
squash. Come meet the other Django people around Dallas and check out
Cohabitat, the great coworking spot in uptown.
We'll start Saturday, April 18, 2009 at 9:00am through Sunday,
On Tue, Mar 31, 2009 at 5:47 PM, Malcolm Tredinnick
wrote:
>
> On Tue, 2009-03-31 at 14:48 -0500, Jeremy Dunck wrote:
...
>> I'm aware of ticket #7539, but would prefer to keep the scope narrower
>> and ask the hopefully-useful question-- is #9308 a bug? If so, I'd
On Mon, Apr 20, 2009 at 3:04 PM, Jacob Kaplan-Moss wrote:
...
> So, with no further ado, I'm happy to announce Django's Summer of Code
> 2009 projects are:
>
> Honza Král, "Model aware validation"
> Mentor: Joseph Kocherhans
>
> Kevin Kubasik, "Upgrade the Awesomness Quotient of the Django Test
>
On Fri, Apr 24, 2009 at 6:19 PM, Zain Memon wrote:
> Hello,
> As you might know, I'm one of the Django GSoC students this year. My mentor
> is (the) Jacob Kaplan-Moss, and he's already started corrupting my innocent
> mind.
> This summer, I'm implementing a collection of ideas with the goal to im
On Wed, Jun 17, 2009 at 3:50 PM, ccahoon wrote:
...
>
> Does anyone have a use-case they could share with me?
>
I hear Malcolm's hovercraft is full of eels.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django de
I've had this issue and have used {% with %} or moved the my.bonnet() call
into the view/context.I agree, not ideal, but I was never moved to make
it better in general.
If you're suggesting a general caching layer in the template such that a
given expression is only called once in the course o
It may be useful to place a comment where @wraps was removed, lest some later
do-gooder "fix" it.
On Sep 17, 2013, at 12:06 AM, Marc Tamlyn wrote:
> Can't say I'm hugely worried about perfect tracebacks and introspection with
> internal kind of functions here if it affects performance. The pat
I recently had a need for a LazyObject which was callable. The __call__
meta method isn't forwarded to _wrapped, so it's an error to call, even if
the underlying _wrapped does support it.
In my case, was trying to do the following:
User = SimpleLazyObject(lambda: get_user_model())
User()...
I
2014 at 8:12 AM, Luke Plant wrote:
> On 05/03/14 23:05, Jeremy Dunck wrote:
>
> > if ...
> > elif isinstance(value, LazyObject):
> > pass
> > elif callable(value):
> > ...
>
> My gut instinct is that if Django's template code has to be patched a
On the None -> IS NULL issue, I presume there are, for any given use case,
not that many argument permutations of None and not None passed. I suggest
that the PreparedStatement abstraction map to multiple actual prepared
statements, one for each None/not None permutation. Then when executing,
you
How about adding a flag to Operations? implied_null, perhaps.
On May 14, 2014 7:52 AM, "Andrew Godwin" wrote:
> Hi,
>
> That's currently the only approach I'm afraid - there's an open issue
> (raised by Shai Berger I believe) that column_sql should be broken down
> into more component pieces so i
I'm attempting to implement narrow writes (that is, writing only fields
which have changed).
I would be able to do this as a 3rd-party Mixin library if some changes
were made to Model.save_base.
1) returned whether the row was created or updated, e.g. if .save_base
returned the `updated` value
I use this method on my own test subclasses, and I find it useful as a
tripwire: a cause for review and consideration, more than a hard error. Did
the number of queries go up on this change? Is that reasonable or a
mistake? Have we blown the perf budget so we should refactor? Or maybe the
number sh
As someone affected by an issue that would fall under the proposed change
[1], I still support an explicit guideline about external behavior
influencing internal acceptance. The safety of all members is more
important than the risk of misapplication of the rule.
[1]
http://doubleunion.tumblr.com/
Right now, I think that static/media handling is fairly confused in the
documentation, and a bit confused in the code itself.
We have a few special-cases floating around:
default_storage (needed for legacy before storage backends)
staticfiles_storage (needed for collectstatic/handling)
{
er hand changing the APIs will create confusion again.
>
> Finally, static and media (user-uploaded) file have different
> requirements, especially in terms of security. I think it’s useful to keep
> the concepts separate, even if they ultimately depend on the same APIs —
> ba
An alternative that might work well is to triage tickets to mentors, so
that a list of tickets with willing mentors is available. It would feel
less judge-y than "easy pickings" and also broaden the pool of tickets that
could be worked by a newcomer. Of course it hinges on a willing pool of
mento
I've had this scenario before - you have two interleaving units of work
(through composition of code from different sources or concerns). You want
progress recorded for one unit of work, but perhaps not the other. Without
django, you'd have two open connections. In my experience the simplest way
You can use atomic just over the section that causes the error. The issue
is that different db engines have different semantics under error during
transaction. Rolling back to the last savepoint (as atomic does when
nested) recovers the ability to complete the remainder of the transaction.
With a
On 5/18/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> Well, I did try something like that at first, but the problem is that
> the proxy object is instantiated once, when assigned to the class. So
> ultimately, all instances of the Model use the same instance of the
> Proxy, which means that any a
On 5/4/07, benk <[EMAIL PROTECTED]> wrote:
...
>
> text length = 3998, saved length = 3998
> text length = 3999, saved length = 3999
> text length = 4000, saved length = 4000
> text length = 4001, saved length = 2001
> text length = 4002, saved length = 2002
>
...
> Django on Linux + Oracle on Lin
On 5/25/07, Clint Ecker <[EMAIL PROTECTED]> wrote:
...
> So, I've talked with Adrian and he said I should put this out there in
> front of the community.
I think getting a regular, central update is good for publicity and
activation, but I also think it's less critical now that googling for
"djan
In [3226], the multi-auth branch landed.
It introduced a backwards incompatibility in existing sessions, which
are used for session-based auth.
The code responsible for supplying request.user prior to that rev was
e.g. handlers.modpython.ModPythonRequest._get_user. After that rev,
it's contrib.au
On 6/1/07, kernel1983 <[EMAIL PROTECTED]> wrote:
>
> Now session can be only storaged in the database.
>
> I think,django should be friendly with both new users and the mature
> python users.
Yeah, I agree, though I haven't gotten around to supplying a patch for
other backends. I do like the per
On 6/10/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 6/10/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> > Aside from that, would really help if I had a clue what folks are
> > actually using dispatch for with django- which signals, common
> > patterns for implementing their own signals (pr
On 6/18/07, Clint Ecker <[EMAIL PROTECTED]> wrote:
>
> Everyone:
>
> *** I sent this to Adrian this afternoon and I just ...
> Technica), I think it would be most prudent to publish these before
> noon on Mondays when there are likely to be the most eyeballs. Does
> this sound reasonable?
It so
I haven't been tracking the newforms-admin branch, so this may already
be done, but I think it'd be a good idea to allow querysets (or Q's)
to be used for list_filter.
For example, I'd like to make it easy for an admin to see just the
list of un-geocoded objects, which is where latitude == None (
On 6/25/07, Clint Ecker <[EMAIL PROTECTED]> wrote:
> Ah, I think I had meant: "integrated into the trunk this week"
FWIW, both Jacob and Adrian are on trips this week. I'm not sure who
else could grant you blog posting permission.
I'm sure they'll respond as soon as they can.
--~--~-~-
Hello all,
I'm trying to document uses of django signals in preparation for a
presentation.
I'm having some trouble finding any uses of class_prepared.
I imagine this is because the class_prepared signal is sent so early
in Django's startup, but am curious:
Does anyone know of an example
On 6/26/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
...
> Has anybody on here ever had a need to do something like this? If so,
> are there other decent solutions available?
Assuming I've understood the issue, and if you don't expect concurrent
writes, consider a BDB.
Also, these may or may not
On 6/27/07, Kevin Tonon <[EMAIL PROTECTED]> wrote:
> I'm using Django 0.91
Hi, Kevin. Please ask this question on django-users. The
django-developers list is for people developing Django itself rather
than using Django for a project.
When you do, it'd help to include the template you're testin
On 7/1/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
>
> The d-users list is getting pretty high volume, and I think it would help to
> split some off that isn't really django but "something built with django."
It doesn't seem like 3rd-party announcements compose much of that
volume. Are you tryin
I understand how newforms validation occurs (Field.clean,
Form.clean_FIELD, Form.clean).
However, people (myself included) are surprised that newforms
form_for_model doesn't include validators from validator_list in the
generated Form.clean method.
Is validator_list going away entirely, or is it
On 7/4/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Is validator_list going away entirely, or is it desirable for
> form_for_model to implement the needed clean method based on the
> validator_list's of the form fields?
FWIW, I've read this thread, but it doesn
On 7/4/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> I haven't given this a ton of thought, but my own opinion is that
> validator_list should go away, in favor of custom Field subclasses
> that know how to validate themselves, and/or validate_FOO() method
> hooks on the model. Basically, it wo
On 7/5/07, David Cramer <[EMAIL PROTECTED]> wrote:
> http://www.davidcramer.net/code/50/django-cachemanager.html
>
> Criticism welcomed!
I think the order of bits returned from _get_sql_clause is dependent
on how the queryset is built up, so that you'll cache equivalent
result sets repeatedly.
A
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
>
> Ok, thanks. That's the answer I was afraid of, unfortunately.
>
> Just in case anyone knows, is it the same with the other frameworks
> for Python, like Pylons, Turbogears, etc?
Yes.
Why is the answer unfortunate? The answer is not bad-- the ques
On 7/5/07, Honza Král <[EMAIL PROTECTED]> wrote:
> We haven't tested it for performance (we are building a high-volume
> site) yet and we still haven't figured out how to deal with multiple
> web servers connecting to one cache (our working version includes
> propagating the post_save signal via s
On 7/9/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> A fair number of the questions asked regularly on the users list could
> be avoided if the point was made that Django code is just Python code
I think a fair number of people start learning Python at the same time
the start learning Djan
On 7/12/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
> Am I just being dense, or is there no way in django's trac to monitor a bug
> for changes (and receive and email when it does) or even to add a bug to
> a "my bugs" list?!
In the "change properties" section, you want "CC".
--~--~-~--~-
When using the low-level cache and memcache as the backend, you're
likely to run into this stack trace:
...
File "/pegasus/code/current/django/core/cache/backends/memcached.py" in set
48. self._cache.set(key, value, timeout or self.default_timeout)
File "/usr/lib/python2.5/site-packages/memcach
On 7/12/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
...
> It may be that only the memcache backend has this problem, but the
> general solution I'd suggest is to use smart_str on the key given to
> each low-level cache's backend set method. Works-for-me.
To be clear,
On 7/12/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I
> just wanted to point out that it seemed strange to me to consider it a
> core requrement for the serializer, and in fact of Django itself.
If you consider the testing framework core, then serialization is,
because the testing framework use
On 7/12/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2007-07-12 at 05:34 -0500, Jeremy Dunck wrote:
...
> > What's going on here is that the memcache.py library does this with
> > the passed parameters:
> >
> > fullcmd = "%s %s %d
On 7/12/07, Bryan <[EMAIL PROTECTED]> wrote:
> trying to do a .set with bytestrings that contain non ascii char
> values doesn't work. It has to do a .encode('UTF-8') on the string I
> was attempting to push into memcached. and likewise on pulling it
> back out I had to do a .decode('UTF-8').
On 7/12/07, Collin Grady <[EMAIL PROTECTED]> wrote:
> For instance, if I have an input with name="語" and request.POST
> doesn't support unicode, how do I then get the value for that? :)
I believe the issue is that *names* for kwargs can not be unicode.
In [1]: u='語'.decode('utf-8')
In [2]: {u:1
I just ran into a subtle backwards incompatibility introduced in [5091].
I've been pushing an instance of xml.sax.xmlreader.AttributesImpl onto
my Context. AttributesImpl tries to implement a dictionary-like
interface, including __getitem__, but not __contains__.
Somehow, no matter what the val
Since I'm fiddling with the memcache backend post-unicode, I decided
to run tests against all the backends while I was at it.
(Apparently the cache tests aren't run against memcache very often,
because test_not_existent has been there since 3661 and never would
have worked against memcache.
More
On 7/12/07, Simon G. <[EMAIL PROTECTED]> wrote:
>
> #4845 is probably related here in some way, giving this traceback:
I've attached my patch and tests to that ticket.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
On 7/31/07, Forest Bond <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 31, 2007 at 09:58:57PM -, mamcx wrote:
> > I have a requeriment to support Sql Server in a outsourced contract.
> > Is a must, a requeriment for delivery. So, I can't wait anymore for
> > free open source hacking...
>
> You know,
On 7/31/07, mamcx <[EMAIL PROTECTED]> wrote:
> So, I can devote dev time to fix the non-sql server support. I have
> read the code, see all the patch (and be confused for its). I'm not a
> python guru but have 3 years of expertise in develop against Sql
> server.
Start with pymssql, not adodbapi.
On 7/31/07, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> Which patch did you look at and what version of Django are you using?
> You might be able to get some SQL Server support working in 3 weeks,
> but I don't think you will be able to solve the pagination problem in
> that amount of time.
Her
On 8/3/07, pk11 <[EMAIL PROTECTED]> wrote:
> - django's admin log model object_id's type is changed from text to
> integer (is there a reason why object_id is declared as textfield?)
object_id is whatever the arbitrary model's PK is, and you can't
assume it's an integer in the general case. The
On 8/3/07, pk11 <[EMAIL PROTECTED]> wrote:
> the issue with object_id is that mssql can not insert an integer PK
> into a TEXT field.
>
I guess I'm confused. Admin LogEntryManager forces object_id to a
string before saving. Do you see somewhere that's directly filling
LogEntry.object_id with
On 8/23/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> Oh wow, I hadn't noticed Jython 2.2 yet (I've been out of town)! I'm
> wondering this myself, since my employer uses strictly Java,
$ java -jar jython.jar -Dpython.path=/home/jeremwork/djtrunk
~/work/djtrunk/tests/runtests.py
Traceback (inne
On 8/23/07, Leo Soto M. <[EMAIL PROTECTED]> wrote:
...
> That's easy to solve: Just copy optparse.py from the python 2.3
> distibution to the jython Lib directory.
Odd; I thought it must be a C module, since Jython is under the Python
license and it'd make a lot more sense for them to ship the mo
On 7/11/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
...
> In any case, I listed the important packages in use on the system:
> postgresql-server-8.2.4-5
> python-2.5.1-12
> python-psycopg2-2.0.6-2.5
> python-django-snapshot-5646-1
>
> While these are all new packages, the only one which is "unstabl
401 - 500 of 577 matches
Mail list logo
