sses.
Regards,
David
On Wednesday, November 2, 2005, at 10:16 AM, Adrian Holovaty wrote:
On 11/1/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi. I am developing a stand alone desktop application but I like what
django can do as far as wrapping sql database interaction. Can someo
side effects from this? So far it is doing what I
expect.
As far as the code in Django that will not be utilized by my app, I
plan on writing a script to strip folders and files that do not have
any to the to the db api (ie meta, db, settings etc) prior to bundling.
Regards,
David
Hi David
Many thanks Adrian. I am really please for what this will mean to
simplify my SQL development. Thank you for a really nice api that is
very dynamic.
Regards,
David
On Thursday, November 3, 2005, at 01:52 PM, Adrian Holovaty wrote:
On 11/3/05, David Pratt <[EMAIL PROTECTED]> wro
write this code?
2. Is there a way to use a raw SQL statement within the api with a
connection obtained through settings? Let's say I have some large ugly
query with multiple related tables and I want to handle it within the
api but in a raw form.
Many thanks,
David
On Thursday, November 3, 2005, at 04:42 PM, Adrian Holovaty wrote:
On 11/3/05, David Pratt <[EMAIL PROTECTED]> wrote:
1. Is it possible to execute the sqlreset or sqlclear statement
through django-admin (opposite of django-admin install) I haven't
found
a django-admin drop o
Hi.
On Thursday, November 3, 2005, at 06:37 PM, Adrian Holovaty wrote:
On 11/3/05, David Pratt <[EMAIL PROTECTED]> wrote:
Anyway, let me know what you think so I can get started.
django-admin sqlinit mymodel * new method
django-admin init mymodel current - n
On 11/16/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
Not to fan the flames, but I think my position has been a bit distinctfrom these:3. There are requirements for the bundled apps to make use of extensiveJS functionality. If we don't bundle an existing toolkit, we will end up
inventing a new one
On 11/16/05, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
> PS: There are some people in Dojo community, who work on form widget,> which supports some validation mechanism. It would be nice to see what> they do.They do have some stuff to validate input. I found this file in their
repository:http://do
;.I'm happy to see Django folks looking at Dojo (& others, of course), and happy to see Alex interested in figuring out Django. I think the two groups have very compatible philosophies, from what I can tell so far.
--david
ing contributors of significant IP.
I have no concerns about the Journal-World, but I suspect that _if_ you had proper CLAs from contributors, the PSF would probably accept the IP (and thereby take on responsibility for defending it) if that was of interest to the Django community.
--david
change from dev to production by changing an env't variable (across all projects).Hope that's clearer.--david
it would break under apache -- Apache would still require the same environment variable to be set. But maybe I'm missing something?--david
On 11/18/05, Sune Kirkeby <[EMAIL PROTECTED]> wrote:
I guess all this just rubs me the wrong way, because it breaksthe Only One Way guideline.And it should thus be challenged, no argument here.It's very possible that the use case it supports (repeatedly switching b/w projects when invoking
django-
Overall, anything that doesn't require packages but that accomodates both modules or packages depending on the complexity of the system, and defaults to modules, strikes me as pythonic.I'm pretty new to Django's "app" concept, though, and it seems you're slightly messing with it here, so I'll +0 on
On 11/18/05, Jonathan Daugherty <[EMAIL PROTECTED]> wrote:
# * Change Django so that it looks for models in a "models" package# (as it currently does) *or* in a file called models.py. Either the# models package or models.py should live directly within the package
# pointed-to by INSTALLED_APPS.Do y
On 11/18/05, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
I don't care how many layers we are going to have in
implementation, I care for the final layer --- actual use of Ajax in templates.
RPC is not a final layer for me, because I suspect that majority of user will
need end user function
E FROM ... the rest of my query ..."
cursor = db.cursor()
cursor.execute(query)
cursor.close()
db.commit()
Many thanks
David
kits would suck people in who do not yet understand the boundaries b/w the server world and the client world. If you're trying to suck people in, you are going to have to deal w/ people who come in with all the wrong expectations about what they need. There's plenty of time later to clear up their buzz-induced misunderstandings.
I'm hoping to be able to contribute somewhat towards these goals, fwiw.--david
Ok, super. Just thought I would verify this. Many thanks.
Regards,
David
On Sunday, November 20, 2005, at 01:37 PM, Adrian Holovaty wrote:
On 11/19/05, David Pratt <[EMAIL PROTECTED]> wrote:
This seems to be fine for inserts but I found with delete statements,
I
must be explicit
Is Google being inadvertently blocked?--david
On 11/28/05, hugo <[EMAIL PROTECTED]> wrote:
There are several ideas on how to solve this:All of which seem like they would apply beyond Django, no?My first instinct in this sort of case is to find out what others are doing, i.e. Dojo folks, RoR, TG, etc.
--david
ee the specific criticisms being addressed on a case by case basis and Django becoming significant better as a result.
I wish I understood better some of Aaron's comments, though. --david
) to assume JS, IE6+, FF1+, Safari.
I worry that if fallback strategies are a strong requirement, then we can end this thread pretty quickly.--david
. Many
thanks.
David
from django.core import management
# Setup up an app
management.init()
management.install(my_app)
# Admin install ???
management.createsuperuser(username='admin',
email='[EMAIL PROTECTED]', password='apassword')
Hi Adrian. Super :-) This did the trick. Many thanks!
Regards
David
Adrian Holovaty wrote:
On 12/15/05, David Pratt <[EMAIL PROTECTED]> wrote:
Can someone fill in the blank. Many thanks.
[...]
from django.core import management
# Setup up an app
management.init()
management.i
HI. I was wondering if anyone has advice on setting up the small web
server to run in its own thread - something to see that it stays alive
as well.
Regards,
David
don't think
it would require too much to provide this functionality. I think in
light of the fact that most people are likely developing on windows
boxes, it would be a plus. I looked at the httpserver code and I don't
think it would much to fit this in.
Regards,
David
From T
Hi Ian. Thanks for your reply. It does, however I was looking at this
from the perspective of running the small httpserver as its own service
when Django is installed on a Windows machine for development. Is there
any interest in this?
Regards,
David
Ian Holsman wrote:
doesn't Apache
Thanks for this. I have been reading up quite a bit on threading and
also windows services. I am not much of a windows user but sometimes
you find yourself needing to do things with it. For me Mac is great and
Unix of course.
Regards,
David
PythonistL wrote:
David,
Check this
http
until I understand everything a bit more clearly.
Regards,
David
Adrian Holovaty wrote:
On 12/19/05, David Pratt <[EMAIL PROTECTED]> wrote:
Hi Ian. Thanks for your reply. It does, however I was looking at this
from the perspective of running the small httpserver as its own service
when
from the middleware all the way through to the
server without trouble.
Further, if cherrypy wsgiserver is used, the cgi for windows service has
already been written and get Django a bit futher along for some sort of
packaging as been suggested for Windows.
Regards,
David
Adrian Holovaty wrote
License is BSD so all is well in that regard. There is still an issue
with the app that gets passed to the server to deliver the request
properly. It would be great is there is someone interested in helping
that understands this aspect of Django well that could lend a hand.
Regards,
David
since
the use of the server creates a dependency upon CherryPy. There would be
a need to integrate a development/production server configuration and
modify management for the command line tool.
Regards,
David
License is BSD so all is well in that regard. There is still an issue
with the app
Hi there. What kind of time anticipated time line for no magic branch to
be tagged as a release? I am accumulating a fair amount of code and am
getting nervous about the number of changes that I will need to make
once this is stable.
Many thanks
David
Hi. I have a situation where I store a pickle in a field that I'd like
to unpickle for an update form and on save pickle again. What would be
the best approach for this scenario given the current or future
possibilities of admin customization.
Regards,
David
Jacob Kaplan-Moss wrote:
Can someone advise whether there is a grid type widget for dojo that
could work with model data. Many thanks.
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
Thanks Ian. Is there a plan for the development of this sort of widget
as part of dojo in general that you are aware of that could fit into django?
Regards,
David
Ian Holsman wrote:
> http://turboajax.com/turbowidgets/ might be of interestest.
>
> BTW. they are about $200 for comme
tween some very excellent open source
initiatives.
Regards,
David
Armin Ronacher wrote:
> The django ORM is the best out there. The only problem is that it's
> only working from inside django.
>
> There is a ticket for that: http://code.djangoproject.com/ticket/1321
> and
would greatly
inform how I proceed, so that refactoring to the Django way might be easier when
the time comes.
Thanks,
David S.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
David S. <[EMAIL PROTECTED]> writes:
> [snip] I am wondering if it is still planned to release some Dojo
> integration soon and if there is any idea what that will look like. I have
> not
> found any hint of if in the magic-removal branch.
Terribly sorry. I meant to p
would not work very well.
Anyhow, looking forward to testing.
Best,
David S.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
Hi there,
Is anyone working on this?
I already found some problems for the firebird adapter, or not :)
For example the LIMIT OFFSET clause, firebird uses SELECT FIRST SKIP
and the sql construction in django implies that the limit offset is
always appended with the backed.get_limit_offset_sql()
> Hi David,
Hi, thanks for the response.
> I don't know of any work being done on a Firebird adapter. Would you
> like to volunteer? :)
Shure :) at work we are building a portal that will work as bridge
between the our software (similar to SAP) and it uses Firebird, so it's
further.
On Sun, Nov 13, 2011 at 7:05 PM, Yo-Yo Ma wrote:
> Before voting for more magic to the transaction middleware, I'd vote
> to remove it altogether. Explicit is surely better than implicit in
> this case. The admin already uses commit_on_success, etc.
>
> On Oct 18,
ir examples, they are hand-crafting
the HTTP request to spoof this but I guess that is not representative of
what can be done via a browser-based CSRF attack. How much of a security
issue is this?
I'm happy to share the relevant pages of the report if anyone's interested.
All thoughts a
On Mon, 2011-12-12 at 00:46 -0600, Joseph Tennies wrote:
> While I agree it should be dropped, I was discussing this with the
> Twisted guys. They pointed out that it will actually receive security
> updates through 2013. This is thanks to Ubuntu 8.10 LTS. I'm sure
> Canonical could tap into someon
On Fri, 2011-12-23 at 08:36 -0800, Vinay Sajip wrote:
> On Dec 23, 3:23 pm, Jannis Leidel wrote:
> >
> > I would argue that Jaunty being a non-LTS release shouldn't be considered
> > as a target platform we want to support. OTOH the LTS release Ubuntu Lucid
> > (10.04) ships Python 2.6.5, so we'
So a few things we've done to take our test suite from 45 minutes to
12:
1. Implement global fixtures
These get loaded after syncing just like initial data. Obviously this
is a massive speed up
as you only reload them in between transaction test cases.
2. Don't inherit from TestCase if you aren'
rapping a broad exception class with a narrower
subclass, to make it easier to catch).
The ticket is currently in 'Design decision needed' (has been for
several months). What's next?
Thanks!
David Lowe
--
You received this message because you are subscribed to the Google Groups
"D
I may have found a bug in Django but wanted to run it by the core
developers before I filed a ticket. It concerns validation of a
ModelMultipleChoiceField when using a case-insensitive database
collation (in our case, a MySQL database with collation set to
'utf8_general_ci').
First some background
ll steps
may be enough to get to a nearly perfect solution here.
David
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send e
ly makes things more ugly.
David
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr
's more important to
have clearly purposed methods than saving a line of code.
David
On 12 October 2012 14:25, Chris Wilson wrote:
> Hi all,
>
> If the save() method returned the object itself, then we could chain it
> like this:
>
> old_status = Status(last_co
To post to this group, send email to django-developers@googlegroups.com.
>> To unsubscribe from this group, send email to
>> django-developers+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-developers?hl=en.
>>
The exact versions of Django available on Pypi are here:
http://pypi.python.org/simple/Django/
Nobody recommends installing this old version of Django for production, but
you can install 1.1.4 like so:
pip install django==1.1.4
On Wednesday, December 12, 2012 11:37:58 AM UTC-8, Will Van Wazer wr
nd turn your snippet above into a proper patch -- the most
> important part of which will be test cases. Management command discovery etc
> are all tested features, but namespace packages aren't currently tested. Even
> if your import modification *isn't* the right solution
Can we please change this so it defaults to off, and just document how to
turn it on and in what situations you should turn it on?
In my opinion this default-on feature caters to a very specific audience,
and will cause a lot of unexpected behavior with other users.
Here is the tl;dr of an argu
urrent connection is very different
than a single operation.
On Thursday, February 28, 2013 at 1:40 PM, Michael wrote:
> On Thu, Feb 28, 2013 at 4:10 PM, Christophe Pettus (mailto:x...@thebuild.com)> wrote:
> >
> > On Feb 28, 2013, at 11:09 AM, David Cramer wrote:
>
. But you need a central storage to accomplish that. (Drupal works
this way.)
Anyway, I don't think throwing UrlNotMatched is the right solution here.
David
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this
> David: The slugs wouldn't be overlapping if they inherited from some
> sort of "Organization" model with unique slug. The user could also add
> validation code to prevent company and schools having same slugs.
If you have a common base model this sounds like some p
It's worth flagging up that part of what makes WhiteNoise good for serving
static files in production also makes it not quite as good for using in
development.
Most file servers work by taking the requested URL, constructing a local
path from it, and then checking whether a file exists at that
+1 to this: I'm all in favour of supporting production-adequate static file
handling in core. A couple of small points:
We already have the views, api, and logic around for finding and serving
> the correct files.
One question that needs to be thought through is the role of
`collectstatic` and
Doesn't look that way to me in Fedora or Chrome on Linux
On Tue, Jan 13, 2015 at 1:48 PM, patrick91
wrote:
> On Tuesday, January 13, 2015 at 8:15:40 PM UTC+1, Some Developer wrote:
>>
>> I know this isn't strictly speaking a Django dev topic but since the
>> developers are the ones who changed t
Hi everybody,
Recently I've begun to use the PostgreSQL specific fields introduced in
Django 1.8. My codebase actually uses the special fields (HStoreField and
ArrayField mostly) frequently enough such that I cannot run my test suite
on an in memory SQLite database -- I have to run on a Postgr
or the section I'm working on well I
> then rely on the CI to deliver my final answers
>
I feel the same way and constantly target particular subsets of my tests,
but it's always tempting to see if everything can run a little quicker!
Thanks again for the response and advice.
-
On Friday, 5 December 2014 19:14:29 UTC, Carl Meyer wrote:
>
> On 12/04/2014 10:33 PM, Collin Anderson wrote:
> > Hi All,
> >
> > I'm pretty interested in getting secure and _somewhat_ efficient static
> > file serving in Django.
> >
> > Quick history:
> > 2005 - Jacob commits #428: a "stati
new classes/methods/functions? I couldn't
find anything on this.
Thank you so much. I hope I can contribute and help make django better!
Best regards,
David Filipovic
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contribution
utput_field type (at least in some cases? e.g (DateField - DateField)
--> DurationField) , as opposed to having to use an ExpressionWrapper,
which makes the interface slightly more complicated?
What do you think, Josh?
Best regards,
David Filipovic
On Thursday, October 15, 2015 at 11:
How about making them opt-out instead of opt-in (for instance with a
--skip-checks flag)? That way anybody who is aware of the fact that checks
are being run every time tests are run and is seeking an increase in
performance can choose to opt-out, whereas anybody not aware (or at least
not full
cases? e.g (DateField - DateField)
> --> DurationField)
>
> If you can find an appropriate place for this logic to live then I'm all
> for it. ExpressionWrapper is cumbersome, but it's also necessary for user
> based combinations where the base F/Combinable/Expressi
flag to their settings file and still use their old workflows.
On Tuesday, October 20, 2015 at 1:02:12 AM UTC-4, David Filipovic wrote:
>
> How about making them opt-out instead of opt-in (for instance with a
> --skip-checks flag)? That way anybody who is aware of the fact that chec
I have initially created the ticket
https://code.djangoproject.com/ticket/25618 which addressed the bug that
would occur if south migrations somehow ended up being still present in the
migrations module.
According to a report in:
https://code.djangoproject.com/ticket/25618#comment:7, this seem
> * django/contrib/staticfiles/views.py
> * django/contrib/staticfiles/management/commands/runserver.py
> * django/contrib/staticfiles/handlers.py
> * django/views/static.py
>
> Any objections to doing further investigation in this area?
>
> On Saturday, June 20, 2015 at 8
it up. This is then tested for in Model._perform_unique_checks
and the uniqueness checks are executed if it is set to True which it always is
after calling ModelForm.save()
Is this a bug? Surely it can't be that unusal to want to call
Model.full_clean() before each save?
--
David Reyno
On 7 Sep 2010, at 16:48, David Reynolds wrote:
> Hi folks,
>
> I am running into a validation problem with ModelForms - here is a quick
> summary of what is happening
I have opened a ticket to track this
[http://code.djangoproject.com/ticket/14234]. I'd be happy to work
Hi,
I would really appreciate some feedback on this.
Thanks,
David
On 8 Sep 2010, at 09:39, David Reynolds wrote:
>
> On 7 Sep 2010, at 16:48, David Reynolds wrote:
>
>> Hi folks,
>>
>> I am running into a validation problem with ModelForms - here is a q
equired to make this happen:
* Documentation. It looks like David Larlet has made a start on this
already, but there's lots more required.
Yes, only a start but I'm working on it, any help is really appreciated.
* Conversion of the github project into a patch on trunk.
Do you see
o.shortcuts.redirect does
Done, no more post_save_redirect argument but View.redirect_to()
#13842: XViewMiddleware fails with class-based views
Must be fixed before class-based views merge.
I hope I didn't forget one, it's really hard to search with Trac...
Best,
David
--
You re
As client-side templates become more popular, it is increasingly
likely that django's template language will not be the only one
present in a template. (jQuery's new template language makes frequent
use of curly braces in its syntax.) At the same time, the assumption
that all template syntax shou
Given 2 +1s, I've added a ticket:
http://code.djangoproject.com/ticket/14502
On Oct 19, 6:49 pm, Jacob Kaplan-Moss wrote:
> On Tue, Oct 19, 2010 at 12:24 PM, David Gouldin wrote:
> > Thoughts/opinions?
>
> Looks like a good idea to me. I've certainly used ssi as a h
%}{% cache ... %}
this will be cached content: FOOBAR {{ some_var }}
this will not be cached content: {% verbatim %}{{ user }}{% verbatim
%}
{% endcache %}{% endrender %}
I could even provide some code for a {% render %}-tag, as I use
something like this in production.
David
--
You receive
I was wondering what the prospect was of getting a CSV serializer
added to Django. It seems like it would be useful for many use cases,
especially for bulk editing of objects by non-technical users. We have
this requirement where I work, so I wrote a CSV serializer:
http://djangosnippets.org/snippe
On Oct 26, 8:05 am, Russell Keith-Magee
wrote:
> On Tue, Oct 26, 2010 at 12:01 PM, David Lindquist
>
> wrote:
> > I was wondering what the prospect was of getting a CSV serializer
> > added to Django. It seems like it would be useful for many use cases,
> > esp
For what it's worth, here are some of the decisions that I made in the
serializer I linked to above.
- m2m values are serialized as comma separated values surrounded by
brackets, like Python lists: "[1, 2, 3]"
- The Python contstants True, False, and None are serialized as the
strings "True", "Fal
ld become:
{% blocktrans count var1=foo var2=bar %}
David
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django
A common behavior I seem to have is the need to tweak the settings
object for certain test cases. The other case is that in many cases we
were (are?) relying on settings being configured a certain way for the
Django tests to even work. I brought this up in #django-dev a while
back, but wanted to op
With a decorator approach here's what I whipped up:
(This is dry code)
def with_settings(**overrides):
"""Allows you to define settings that are required for this
function to work"""
NotDefined = object()
def wrapped(func):
@wraps(func)
def _with_settings(*args, **kwar
in _orig.iteritems():
if v is NotDefined:
delattr(settings, k)
else:
setattr(settings, k, v)
return _with_settings
return wrapped
--
David Cramer
http://www.davidcramer.net
On Thu, Nov 4, 2010 at 2:26
I was going to propose the same thing Santiago. Signals seem like the
ideal candidate to solve that problem.
--
David Cramer
http://www.davidcramer.net
On Fri, Nov 5, 2010 at 4:57 AM, Santiago Perez wrote:
>> * Settings that are internally cached. For example, anything that
>&
We have been working on a new version of the API these past couple of
months, and we're nearing a public release. I wanted to take this
opportunity to see if any of the heavy API users (specific needs, etc)
would like to chime in with what they want to see, and possible give
our docs/api testing to
each using the pkgutil.extend_path() trick. However only the first one on the
path will be searched for management commands.
Hopefully Nils' patch will fix this situation too
--
David Reynolds
da...@reynoldsfamily.org.uk
--
You received this message because you are s
If I'm reading this code correctly:
https://github.com/stephrdev/django-formwizard/blob/master/formwizard/forms.py
I think this implementation misses the core point I was trying to
address with #9200, that you should not have to POST in order to
navigate to a step/form in the wizard. My implem
On Thu, Jan 6, 2011 at 4:22 PM, Stephan Jäkel wrote:
> Hi David,
>
> you should take a look at the NamedUrlFormWizard. In this second approach,
> after successful posting a form, a redirect is done to get the user to the
> next step. Is this the point you meant?
>
> Using t
ble to have different
urlconfs or templates or ...
David
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email
models. There are other internals that will
need to be modified, besides these three methods, in order to eliminate the
occasional errors I'm getting in syncdb; I'm still figuring out what those
are.
Your feedback is appreciated.
David Greisen
--
You received this message because you are s
We're going to be deploying a backwards incompatible change to all
"since" values in the API. Any endpoint which accepts this parameter
to use as a form of range pagination will now include the value sent,
as well as values before or after it (depending on the order).
For example, in the original
I have no idea how I've done this, twice.
On Feb 10, 2:16 pm, Alex Gaynor wrote:
> On Thu, Feb 10, 2011 at 5:14 PM, David Cramer wrote:
> > We're going to be deploying a backwards incompatible change to all
> > "since" values in the API. Any endpoint which acc
Check out django-startproject from lincolnloop.com
https://github.com/lincolnloop/django-startproject
Kill off all the server configs (though some of it might be cool, like
Fabric integration), and I think it'd make for a pretty good base to
work from if this were to go into core.
On Mar 13, 9:1
In our profiling we've also noticed the cloning to be one of the
slowest parts of the app (that and instantiation of model objects).
We haven't yet, but had been planning on exploring a way to mutate the
existing class in most circumstances, but haven't
dug into it too much yet.
On Mar 14, 11:16
e idea of using some
kind of context processors for JS-context is what this email is
about. ;-)
David
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
201 - 300 of 807 matches
Mail list logo
