plit the
code, and give access to some but not others. This is still doing things
the hard way! If possible, work with reliable people with contracts to
remove those barriers. If not, make the code work for your business
constraints, such as an API to give a clean separation between insiders an
continuous
deployment. It is also tricky enough that it would benefit from a full-time
effort to implement and refactor.
- John
On Tue, Nov 15, 2022 at 3:11 AM Carlton Gibson
wrote:
> Hi all.
>
> Google Summer of Code (GSoC) for 2023 has just been announced.
>
> https://opensource.g
base64
encoded, and potentially compressed.
The second section is the encoded timestamp, used to determine if it was
created too long ago on decode
The third section is the HMAC signature, base64 encoded.
- John
On Wed, Oct 5, 2022 at 4:45 PM 'Adam Johnson' via Django develop
Hi folks,
According to the Django's release process document[1], there should be a
signed tag for 4.1.1 yet I do not see it listed:
https://github.com/django/django/tags
Thanks.
[1] https://docs.djangoproject.com/en/dev/internals/release-process/
--
You received this message because you are su
I do exactly this for every new Django project, so it's +1 from me as well.
John
On 20/04/2022 12:01, da...@springbourne-tech.com wrote:
+1 for me - this would be really useful.
On Monday, April 18, 2022 at 9:02:02 PM UTC+1 pyt...@ian.feete.org wrote:
Hi Tim,
This feels like a
Alex I find the notion that you think changing terms that have bad racial
connotations to be "embarrassing" to be entirely without merit. It is not
embarrassing to consider the feelings of Black and other minority people
when using language. Moreover, racism is not simply a US only phenomenon.
Would it be possible to expand the scope of the recently accepted secret
key rotation ticket to include the ability to live rotate other credentials
as well, such as the DB credentials?
Or would this be a separate thing all together?
https://groups.google.com/forum/#!searchin/django-developers
try to get some more concrete numbers about
current engagement level by looking at the data. It might be worth it to
then compare this projects of a similar nature / size, though I'm not sure
how much validity that would have, being apples and oranges.
~John
On Wednesday, August 7, 2019 at
one of those three could do what is ultimately needed, which is a
centralized and consistent development platform.
On Wednesday, August 7, 2019 at 12:33:59 AM UTC-7, Aymeric Augustin wrote:
>
> Hello John,
>
> This was discussed before, when we moved from self-hosted svn to
> Git
o-developers/aiyE__qSHBY/discussion
https://groups.google.com/d/msg/django-developers/5CVsR9FSqmg/qKD3QCrLCAAJ
On Tuesday, August 6, 2019 at 11:24:45 PM UTC-7, John Gooding wrote:
>
> I'd like to propose moving Django issues to github and make a real
> decision on it here in this thread.
any of the discussions on this forum into github's issue tracker. I
don't see any reason why it wouldn't be wroth the effort, and we only have
much to gain as a community from it. But that's just my 2 cents. I'd love
to hear what others think, for or against it.
John
-
To be clear, I am not saying there is a bug. It does what it is programmed
to do. I am saying the expected behavior of the API / CLI / whatever you
want to call it is inconsistent.
I am not going to get into an argument of what a "proper" django structure
is, etc. I want to focus purely on the
I wonder about the end-result payoff of this approach. In general,
Django/Python code is not going to be I/O bound, which is where
asynchronous approaches are going to get the bang for your buck. Even when
it comes to DB access—the DB is a lot faster than the python and django
code running agai
Email and password is pretty well supported out of the box using the
configuration options provided on the AbstractUser (USERNAME_FIELD). Slightly
more complex cases like username and email both being valid login parameters
require very thin wrappers. The greater discussion is about technologi
I believe this change is merited and I would be happy to help if others are
interested in working this. I have actually monkey-patched it a few times
now for two reasons:
a) I want more data fields on the group itself, or
b) I want to implement nested groups
MPTT's docs suggest one approach wh
Chiming in. As a long-time django user (nearly a decade), websockets is an
area that the project on the whole is very, very, far behind the leading
edge of the web industry. It's great, often desirable, to not be *on* the
leading edge, but in my opinion, the project is too far behind it.
There
AM UTC-4, John Obelenus wrote:
>
> Can I ask a dumb question? Why did you only discover this with adding
> Whitenoise, and not the default/common middleware stack that comes in
> django? Asking that question in another way: What is specific to whitenoise
> that this constant loadin
Can I ask a dumb question? Why did you only discover this with adding
Whitenoise, and not the default/common middleware stack that comes in
django? Asking that question in another way: What is specific to whitenoise
that this constant loading of middleware causes such a perf hit? This
question
Can I please ask a clarifying question?
You examples above ("if you had 1 clients...") spoke to clients sending
the messages. I have a use case where the clients are never (at the moment)
sending messages but rather listening for messages from the server. When
the server has something to sa
im's PR is pretty
complete.
Thanks,
John Griebel | Senior Backend Engineer | 3Blades.io | 814-227-4213
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop recei
precated immediately?
7.) view_tests - I see Sjoerd already made some small changes here and
wanted to confirm that the rest of the URL conf was not left unconverted
intentionally before converting them myself.
Feedback on 6 and 7, in particular, would be great.
Thanks,
John Griebel | Senior Bac
ironment set
up.
On Jul 29, 2017 4:49 AM, "Emil Stenström" wrote:
John: Awesome! Do you need anything to get started or is Sjoerd's review
comments and todolist enough?
On Friday, 28 July 2017 15:03:12 UTC+2, John Griebel wrote:
> Hi Sjoerd,
> I too would love to see this
Hi Sjoerd,
I too would love to see this feature in Django 2.0; in fact, I've been
following its progress quite closely. I would love to help out with it and
have the necessary time to do so.
John Griebel | Senior Backend Engineer | 3Blades.io | 814-227-4213
On Thu, Jul 27, 2017 at 5:
I would love to see this change implemented as well. I have a few models
that would benefit from having a quick entryline at the bottom of the
list_display.
Personally, I think that the first possibility, where only the items that
are in the 'list_editable' tuple would be editable in the blan
I agree that we need a replacement; the current behaviour isn't all that
useful, IMHO. My vote would for choice #2, after all it seems more natural
(to me, at least), to think of numbers as a range, especially while
searching. Option 1 seems less intuitive for a situation like this.
+1 from me, es
tive, it would solve a rather frustrating
problem.
Thanks,
John Cronan
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an
dated by
the user, compared to the values originally displayed, and do all these
changes independently of one another. From this point of view, it is
actually an optimization, to skip the update when there is no change.
-John
On Wednesday, March 16, 2016 at 8:21:40 PM UTC-5, Josh Smeaton wrote:
which is what I think they're after.
What do you think they should be doing?
John
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails fro
It should be possible to use a "RETURNING" clause to get the new row even
in the instance of a get_or_create.
I occasionally use an UPDATE ... RETURNING query with Manager.raw to update
a table and get modified instances in one shot.
On Tuesday, January 12, 2016 at 12:54:03 PM UTC-6, bliy...@re
tuple):
if not apps.ready:
apps.populate(settings.INSTALLED_APPS)
model = apps.get_model(*model_id)
Can that test instead be "if not apps.models_ready"? That would prevent
the nested call and fix my problem.
John
--
You received this message because you are su
django-cms developers.
John
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googleg
7;m using are
doing reasonable things.
I posted the details to django-users, but the only response I've gotten is
a suggestion to ask you folks:
https://groups.google.com/forum/#!topic/django-users/WiRzQ8EFOdo
John
--
You received this message because you are subscribed to the Google G
>pip install django --upgrade
Collecting django
Could not find a version that satisfies the requirement django (from
versions: )
No matching distribution found for django
This seems to only be an issue with django as all other packages in
requirements file are installing fine this morning
Looki
Python now has static type checking. All you do is follow function
parameters with ": paramType" and add "-> returnType" before the colon at
the end of the function declaration and auto-complete will work on the
return value in IntelliJ. Can you add the function parameter types and
return types
Python now has static type checking. All you do is follow function parameters
with ": paramType" and add "-> returnType" before the colon at the end of the
function declaration and auto-complete will work on the return value in
IntelliJ. Can you add the function parameter types and return type
Definitely seems like a good idea to me. Even as a frequent CBV user, it
always takes me a few seconds to remember to import from generic.
John Paulett
On Tue, Sep 22, 2015 at 10:41 AM, Tim Graham wrote:
> Class-based view users, does this proposal from
> https://code.djangoproject.com/
Hey all,
I would also be interested to contribute to this effort.
Is there a ticket/github issue to track it?
Best,
John
On Sun, Apr 19, 2015 at 11:18 AM, Kevin Glavin wrote:
> Hi Tim,
>
> I have been using Docker, Vagrant, and Jenkins for a while now
> independently. Would love
ven't already).
Personally, I want to ensure we stay true to the core team's wishes. So as
we proceed, please reach out if there is anything we could be doing better,
particularly clarification that this is an unofficial community effort and
encouraging the transition to the official rele
shing unofficial
distributable under Django's PyPI project is advisable.
John
On Fri, Mar 27, 2015 at 10:06 AM, Tim Graham wrote:
> Instructions for requesting to be added to the security prenotification
> list are here:
> https://docs.djangoproject.com/en/dev/internals/s
hello, I added Django in www.xrefs.info to provide cross reference search
for Django development.
http://www.xrefs.info is made for open source community in
the hope of making open source developers more productive.
The site hosts many open source code projects' cross references based
on OpenGro
y Django? Is that expected behavior? Is
there a way to force Django to use the cache for subsequent inlines?
I'm also experiencing a similar problem with a ManyToMany field. (But it
seems to generate even more queries that the ForeignKey)
Any help on this issue would be most appreciated
or request.GET". If request.REQUEST ends up being removed,
I would not be upset, but I did want to state that I use it.
John
On Wed, Oct 16, 2013 at 8:04 AM, Marc Tamlyn wrote:
> +1 to deprecating this. In the rare cases where it is useful (mainly
> 'next' for redirects) i
again in django-users. I've not seen any
so far.
John
[1] This is unlikely to ever happen. Please don't ask for schedule updates.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and sto
Hey I am currently working on a geolocation based game that utilizes a
geodjango application to manage querying, parsing, and server geographical
data to our client. We are currently using PostGIS to store our OSM data.
We are using the OSM tilename system throughout our project and some of our
xcept for
management commands.
https://code.djangoproject.com/ticket/14952
https://code.djangoproject.com/ticket/12206
John
On Wed, Feb 29, 2012 at 3:38 PM, KACAH wrote:
> Hi, django developers,
>
> I think it would be useful to add *.pyc and *.pyo files into commands
> list (not onl
On Jan 30, 2012, at 6:22 AM, Etienne Robillard wrote:
> John, even with your reply your putting politics on the topic.
Yes, apparently I did prolong this, even by replying off list. I won't again.
Apologies, everyone.
--
You received this message because you are subscribed to th
Sounds similar to what django-sentry already provides:
http://blog.disqus.com/post/1178923988/django-sentry
(we may want to move this discussion to django-users)
On Sun, Nov 13, 2011 at 7:51 AM, Ric wrote:
> oh fantastic... but i read about security issue...
>
> and what about create a model, sa
Hi All,
This is in regards to ticket #13614 (Back button breaks many to many
widget). I'm hoping that bringing this up might bring some attention
to it. This is a rather nasty bug affecting the filter horizontal
widget's use with webkit browsers. It causes data loss and incorrect
data to be sav
I like the idea too, since I've run into a lot of situations where
some more convention here would make a decision much easier to make.
However, it isn't clear what exactly should be better defined and I
think the first step to a serious proposal would be to figure that
out.
The only example that
On Feb 4, 2011, at 12:23 PM, Łukasz Rekucki wrote:
> With Django 1.3 almost out, I would like to ask, what's the current
> deprecation plan of old Python versions (namely 2.4 and 2.5). The
> major argument against dropping 2.4 was RHEL support. RHEL6 seems to
> support Python 2.6 (dunno about Cen
Hello,
I'm working on a Django project. I'm running on cloudservers hosting,
with nginx/uwsgi as the server. I'm trying to get an image upload form
working with POST, but I'm running into some problems.
Basically, it comes down to this: if I comment out this line:
uwsgi_param CONTENT_TYPE
rested in seeing these results every time
buildbot ran the full test suite. So we just wrote a test runner that skipped
any app in installed apps that started with 'django.'.
As long as you're willing to trust that Django and the third party apps only
release code that passes th
Sounds good to me I'll try to get a wiki page up with the content you
described by next weekend so that we can get this discussion going.
On Jun 21, 5:15 pm, Russell Keith-Magee
wrote:
> On Mon, Jun 21, 2010 at 10:41 PM, John Williams wrote:
> > There is a known issue with
There is a known issue with using various middlewares that check
content-length consuming the content of iterators. There are many
tickets up regarding the various incarnations of this behavior all of
which appear to be stuck at about the same problem: what is the right
way to fix this. I think
On Jun 14, 10:59 am, Hooshyar wrote:
> Hello all,
>
> I am new to this group, although I am 4 years old with Django. I have
> a question. If this is not the right place, I apologize in advance.
> Please refer me to a proper mailing list. Please reply here or you can
> e-mail me directly, if you wi
On Dec 30, 7:06 am, Russell Keith-Magee
wrote:
> Secondly, IMHO raw truncation based on characters is bad practice for
> human readable text. A sentence is composed of words, not characters.
> Truncating a sentence mid-word isn't a typographical practice that I
> particularly want to encourage.
truncatewords.
It's especially unclear to new developers that they should accomplish
this with slice (and an if statement checking the length of the
string) - and it's not very DRY. The convenience of having slice is
undermined by the fact that many aren't clever enough to use it this
ut after seeing this thread I'm going to take a shot at implementing
FormSetField (or something like it) myself. If anyone has any code -
or more arguments for or against that haven't been covered - I'd love
to hear them before diving in.
John Debs
--~--~-~--~~~--
On Aug 11, 7:50 am, Richard Davies
wrote:
> Hi all,
>
> With 1.1 out of the door (great!), here's a thought for 1.2...
>
> I often end up writing the same couple of template tags and filters. I
> think some of these are general enough and useful enough that they
> should be considered for basic D
On Jul 27, 9:08 am, Russell Keith-Magee
wrote:
> That's certainly one possible solution. However, I suspect a better
> solution would be to find the place that is raising an 404 exception
> that isn't populating the 'tried' attribute. Can you help out by
> telling us the conditions that lead to y
Hi,
Running Django 1.1rc1 via wsgi. Here's the stdout including the
request that raised the exception:
125.65.165.139 - - [26/Jul/2009 23:02:46] "GET
http://pv.wantsfly.com/prx.php?hash=65B15474B46964654834EDB41F4020883D0D9A08F7F9
HTTP/1.0" 500 59
Traceback (most recent call last):
File "/usr/
I found the Actions feature soon after my posting, I was a little
hesitant to update to a beta version though.
The feature works well and with the filter search I can at least
narrow down what could possibly be a very large list.
Thanks
--~--~-~--~~~---~--~~
You re
My first django application is a very basic tool for modifying data. I
have no need to a public interface since its all administration stuff.
The application will allow the user to create/edit/save data into a
database. One feature I'd like to add is the ability to "publish".
What publish will do
x27; behavior doesn't seem to jive with the code and previous
documentation. I understand the worries about backwards compatibility, but
the behavior and documentation seems to be inconsistent in its current
state. It's not my call whether to make the documentation consistent with
the cod
g users.
Clearly, I'm missing why this is a 'good thing'. But since Malcolm usually
knows what he's talking about, I'll assume I'm the one missing something
here. Clue-stick me, please and thank you.
Cheers,
John-Scott
[1] http://code.djangoproject.com/changeset/9176
Thanks Karen!
On Sep 19, 10:24 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 19, 2008 at 9:42 AM, John <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> > I was wondering if nested inlines' will be supported in the admin in
> > any p
Hi,
I was wondering if nested inlines' will be supported in the admin in
any post 1.0 release. I remember seeing it mentioned in the road map
for the 1.0 release but I guess it was dropped due to time issues.
Thanks!
--~--~-~--~~~---~--~~
You received this messag
I started working on a patch 6 months ago to implement App objects,
but unfortunately never got to finish it because at the time I was
swamped at work.
Because of the all the work which has happened on trunk the code is
pretty much useless.
> The following can be addressed with app objects.
>
> 1
On Mon, Aug 25, 2008 at 8:38 PM, Jonathan Nelson <[EMAIL PROTECTED]>wrote:
>
> I tried to contact the TWID gusy through their website, but I haven't
> heard back from them. Anyone know if they're still planning a get
> together?
Kevin Fricovsky (one of the co-founders of django-nyc) helps out w
As one of the original whiners about this issue, I salute you! And a shout
out to Karen for being persistent. I give up too easily sometimes ;)
John-Scott
On Mon, Jul 7, 2008 at 6:19 PM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
>
> Hi folks --
>
> OK, I finally figured
Thanks Brian,
Reposted:
http://groups.google.com/group/django-users/t/2ccf2bb1dc06058e
On Jul 2, 8:47 am, Brian Rosner <[EMAIL PROTECTED]> wrote:
> On Jul 2, 2008, at 9:08 AM, John Boxall wrote:
>
>
>
> > But in NFA - it seems the save method isn't called!
>
to return
>
> super(YourModelForm, self).save(commit)
>
> in it.
>
> On Jul 2, 9:10 am, John Boxall <[EMAIL PROTECTED]> wrote:
>
> > Hi everyone!
>
> > I'm just trying out newforms admin - it's fantastic. I can't wait
> > until this make
method of a model form in
NFA?
Cheers,
John
--~--~-~--~~~---~--~~
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 unsubscri
> * Start a "train release" schedule: schedule a couple of 1.0 betas, a
> rc or two, and then a final release. Features that are done by the
> dates get released, those that aren't, don't. Make these dates
> aggressive but not crazy. And -- here's the controversial part -- make
> newforms-admin a
;s a problem
> at all.
>
> Thus I'm hugely +1 on this no-silent-failures bit, whether optional or
> not.
I'm very much on the +1 to no silent failures ever side, but one thing
that makes it work in ZPT is the |nothing thingie, that allows you to
explicitly ask for silence when need
g and patch writing. INSTALLED_APPS is Adrian's baby and I don't
> know what his current thinking is there; maybe he can offer some
> guidance about whether help is needed.
Thanks for the guidance. It looks like there might be a couple of
other things to poke around at, so perhap
roject closer
to release. And in this particular case, I want to help Django get to
1.0.
And yes, I know trunk is pretty darn stable... but the thing I'm after
is no more painful API changes. :-)
-John
--~--~-~--~~~---~--~~
You received this message because y
oproject.com/documentation/faq/#how-can-i-see-the-raw-sql-queries-django-is-running
Cheers,
John-Scott
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send emai
Jeremy Dunck wrote:
> DId this ever get fixed for you? :-/
>
Yep, Jacob helped me out.
John
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
idea. :-) )
My problem is, I've forgotten my username and password. How can I find
out what they are?
John
http://seeknuance.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gr
Add to that list:
http://en.wikipedia.org/wiki/Internationalized_domain_name#ASCII_Spoofing_and_squatting_concerns
It's not too hard to imagine other sorts of mischief that lookalike
characters could cause.
Thanks for the feedback, guys.
On Jan 29, 2008, at 9:09 AM, Ivan Illarionov wrote:
>
Usernames in django.contrib.auth are restricted to ASCII
alphanumerics. Allowing Unicode seems fairly simple: compile the
validator's regular expression with the re.UNICODE flag.
To a Midwesterner with hardly any language competency beyond English,
it seems like an obvious improvement -- su
the part
> I don't have the time or energy for at the moment. Coding the backend
> itself should be very straightforward. After all, that's the whole
> point of #5361!
>
> -Gul
>
Thanks for your work, I'll try to take a look at it thi
first_name, etc.). However, fields without values still get added
to the GET request (e.g. /?user__first_name='John-Scott'&hometown='') so
the problem with this is that the Django ORM then tries to filter
results where the User object's first_name is 'John-Scott&
> You cannot debug a single Django file in isolation. Instead, insert this
> line:
>
>import pdb; pdb.set_trace()
>
> in sql.py, at the point you're interested in. Then run Django normally,
> and
> go to a db-based URL: you'll get a debugger prompt.
>
ok, thanks. I was just trying to debug wit
I'm trying to debug sql.py
the steps I've taken so far:
python /usr/lib/python2.5/pdb.py manage.py sql polls
(python manage.py polls works just fine)
(Pdb) b django/core/management/sql.py:271
(Pdb) c
Traceback (most recent call last):
File "/usr/lib/python2.5/pdb.py", line 1213, in main
p
Hi Jose,
I know of one preexisting CAS authentication backend which is
available on Google Code [1]. For some background on that project you
might also check out the author's blog posts [2] [3].
/John/
[1] http://code.google.com/p/django-cas/
[2] http://blog.case.edu/bmb12/20
On 8/23/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> Thanks. I've added a few missing svn:ignore properties, including the
> ones you mentioned, in [5993].
Thank you. There's one other directory that should be changed -
tests/regressiontests/test_client_regress has an svn:ignore of
"__ini
On Aug 8, 8:12 pm, "Jay Parlar" <[EMAIL PROTECTED]> wrote:
> On 8/8/07, John-Scott <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > Hello all,
>
> > I'm trying to integrate S3 support into my Django app using
> >http://code.djangopro
or to S3, plus additional
options specific to S3 storage (bucket and key values, etc.). Obviousy
this would involve tinkering with Django's models code directly so I
want to solicit feedback from the Python/Django pros before I go down
this path.
We use this in Satchmo:
Discounts
Discount code {{
form.discount }}
{% if form.discount.errors %}*** {{
form.discount.errors|join:", " }}{% endif %}
Does that give you enough control?
--~--~-~--~~~---~--~~
You received this message be
Thanks for the quick response and help!
I'll be sure to post in the right group moving forward.
Regards,
John
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To pos
ngo_0.95/trunk/django/
-I HAVE included 'django.contrib.markup' in INSTALLED_APPS in the
settings file.
-I HAVE set PYTHONPATH="/home/python/django_0.95/trunk:/var/devel" in
my fastcgi startup script for that site.
I'd be very appreciative for any help. Thanks!
John
--~--~-
I started implementing this a few months ago.
I've factored out SessionWrapper as SessionObject, as a base class and
(re)implemented the database session store on top. I've also got a
working implementation of a FileSession class.
Summary of changes:
Added a SESSION_ENGINE to settings.py
Added
On Jun 2, 12:02 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> Hi All,
>
> I recently raised ticket #4418 to add media descriptors to newforms.
> It was discussed on the following thread:
>
> http://groups.google.com/group/django-developers/browse_thread/thread...
>
> To my reading, Jaco
On 5/21/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > #3896 - pass value to field specific clean function [2]
>
> Grr...don't put two issues in one ticket!
>
> I'm -1 on the first part because it's an unnecessary backwards
> incompatibility change for the most part. It's not like it's a ma
mented, but it was
handy when we found it.
Cheers,
John.
[1] <http://mercurytide.com/>
--
john sutherland
<http://sneeu.com/>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
On 5/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> That was exactly why I didn't change clean_data (my initial "fix" was
> just to name it cleaned_data). It's already used in lots of code, so the
> impact of change it is larger. Changing the undocumented feature is less
> disruptive. Unne
Evening,
I've put the RESTful API code that I mentioned in ticket 2553[1]. A
few people have requested the code and so it's now in a Google code
project:
<http://code.google.com/p/django-crudapi/>
Ideas? Suggestions? Requests?
Cheers,
John.
[1] <http://code.djangoproj
w I would use this with my team.
I presume, if developer A had already applied the first couple
migrations to their testdb, they'd do something like:
migration_list = [
# 'migration1',
# 'migration2',
'migration3',
'migration4'
1 - 100 of 140 matches
Mail list logo
