go sites if they could answer 5 or
6 questions (e.g. pownce, tabblo, etc)
If you get a few "big" names in there, then others should follow.
--Simon G.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
Excellent, thanks!
--Simon
On Jul 28, 5:47 am, Sebastian Macias <[EMAIL PROTECTED]>
wrote:
> I just added it to the wiki:
>
> http://code.djangoproject.com/wiki/BestPracticesToWorkWith3rdPartyApp...
--~--~-~--~~~---~--~~
You received this message because you are
Hi all,
Every so often we get a few tickets popping up about ReST errors in
the docs. I've just patched one (#4995) where some hideously glaring
mistakes like, say, missing a space after an asterisk, or one too few
empty lines caused nasty error messages like:
testing.txt:584: (WARNING/2) Inline
There is a wiki page on this sort of thing:
http://code.djangoproject.com/wiki/DosAndDontsForApplicationWriters
...but it hasn't been updated in a while. If anyone comes up with
useful things, could you (or them) update that page?
Thanks,
Simon
On Jul 25, 11:41 am, Sebastian Macias <[EMAIL PROT
I can help too - I generally keep a close eye on the timeline to
monitor any changes (i.e. spam) but it'd be great if there was more
activity in the wiki and a few people who'd keep things in check.
Is it easy to give out permission to delete attachments (often the
spam consists of attaching some
#4845 is probably related here in some way, giving this traceback:
PythonHandler django.core.handlers.modpython:
MemcachedStringEncodingError: Keys must be str()'s, not unicode.
Convert your unicode strings using mystring.encode(charset)!
There's a few patches there which force the keys to ASCII
... and while you're working out how to do it, it would be good to
write it up for future reference :)
(see: http://code.djangoproject.com/ticket/4223)
--Simon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
Just thinking out loud here -
We've warned people off using the svn version to run production sites
because of the post-1.0 code breakage that's going to be happening.
So, we don't need to worry as much about stability of trunk, since
0.96 is the stable, recommended version.
Therefore, why don't
Evening all,
There's been a long history of people asking for some way of easily
using the MEDIA_URL setting in templates. At a quick glance, I get
#1278, #3818, #2532, and #4105.
These have all been marked wontfix, and I closed this last one to
match. The reasoning for the wontfix is that this
-1 What's the benefit of that over our current system where 0.96 is
stable (except for major security fixes), and the active development
is going on in trunk? This has been documented:
http://www.djangoproject.com/weblog/2007/apr/06/changes/ - people
should be using the 0.96 release on productio
This locmem one is a case in
point here.
Maybe we could tag these somehow ("outstanding"?) so that the next
time a dev. gets some ticket time, they can glance over them and give
some feedback (wontfix, pls. improve patch, will-do-it-when-I-have-
time, etc).
--Simon G.
--~--~-~-
A patch, some docs and a few tests would be most welcome.
--Simon
--~--~-~--~~~---~--~~
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
Sorry - I just skim read the discussions on it in "AutoEscape" and
"AutoEscaping Alternative" where that was mentioned. Wasn't making any
value judgements :-)
--Simon
On Apr 18, 2:49 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Tue, 2007-04-17 at 0
This is one of those issues which is never going to please everyone.
So - I've started a list of the various proposals (1), and could you
all add any other proposals to this page, along with any pros/cons,
and vote on the one(s) you prefer.
This way we can get some idea of what a consensus view
My preference would be to have it as either a package in contrib, or a
third party package that users can install. I don't know how easy it
would be to override Django's default debug handler but shouldn't be
too hard. This way we don't have any on-by-default situations, and it
should be fairly sa
Hi Jay,
Someone reported that issue a few weeks ago, and I added a quick patch
for this here:
http://code.djangoproject.com/ticket/3830
It can probably be enhanced beyond that though.
--Simon
On Apr 11, 4:43 am, "Jay Parlar" <[EMAIL PROTECTED]> wrote:
> Recently in [1], someone ran into a pro
I believe that the plan for 1.1 is to rewrite Django in Lisp or
Haskell. Or is Scheme the cool one now?
j/k
--Simon
On Apr 8, 4:34 am, "Noah" <[EMAIL PROTECTED]> wrote:
> I'm worried about a trend I've seen before in other frameworks etc.
> They start off easier to use and over time get more an
This was reported way back in the triple-digit days:
http://code.djangoproject.com/ticket/987
I took a couple of stabs at it a while ago. I patched
HttpResponseRedirect to prepend the domain to the current site
specified by settings.SITE_ID, as long as it's not the default
"example.com" (anyone
Hi Alex,
I marked that as invalid since (as I understand it), we're trying to
get rid of edit_inline. However, I'm not sure how far off the admin-
newforms rewrite is, and it's probably a good idea to get this simple
fix in anyway (especially if people are having problems with).
--Simon.
--~--
Hi Malcolm,
Should ALL the strings in these be unicode objects, even if they don't
have any extended characters? I'm looking at the already checked in fr
localflavor, and these are all ASCII with the respective file set to
UTF-8 with that -*- thing (what is that called?), there's also a
Brazilian
I've had a first pass at documenting these in #3883 - any comments?
http://code.djangoproject.com/ticket/3883
--Simon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
Hi all,
We're starting to see some localflavour patches drift in, which is
great (e.g. it: #3866, fi: #3847, ja: #3715 ). However, we should be
briefly documenting these - it could simply just be a list of what's
in there so far.
I'll work up a patch for this sometime, but just wondered where to
Ok, my reading of the general consensus here is that everyone thinks a
BinaryField is a good idea, so I've kept #2417 as accepted, with the
patch needing a few improvements.
The second issue - a (say) BinaryStorageField for large bin. data
hooked up to Image/File uploads seems to be one that's wa
Hi folks.
Digging through the tickets, it appears we have a few near-duplicates
requesting some form of binary storage inside the database. Whilst I'm
-0 (RDBMSes are not for binary data!), but I can see the use for them
in some circumstances (#2417 lists a few), and these are likely to be
a fair
[Option 4] - Raise a warning for MySQLdb's that ARE 1.2.1 but not
'final', (i.e. "Your version of MySQLdb is 1.2.1 gamma, Django would
prefer 1.2.1 final. Please upgrade (see docs page for why"...) and
document this. Keep the failure on anything less than < 1.2.1.
& I just wanted to say that I'm
I actually passed this onto the security mailing address, as I thought
it was better to be safe than sorry. Adrian's response was that tying
things to the IP address is not a good idea (for the reasons that
others have stated in this thread).
One thing that I would like to suggest is that we do l
Does anyone object/disagree if I move all the tutorials off the
DjangoResources page (1), to a new page (2) to give them some more
room to 'breathe'? I'll take a crack at categorising them too - pre-
MR, components, etc.
(1) http://code.djangoproject.com/wiki/DjangoResources
(2) http://code.dja
This sounds like a good idea, and if everyone else is doing it...
It might also make #2407 cleaner (CGI Support)- some of the comments
there are stating that you need to load PATH_INFO etc into the env to
get it running properly.
http://code.djangoproject.com/ticket/2407#comment:14
--Simon
-
Good Evening Djuggernauts,
I've spent some time looking over the email related tickets in Trac,
and think I've got them sorted out a bit. I'm hoping to spur some
discussion on some of these, so here's a brief recap.
We currently have requests to:
#1541 - Add Multipart Message capability to mail
#3625 ( http://code.djangoproject.com/ticket/3625 ) looks like a good
candidate - it's a Python 2.3 issue with rsplit in the test system.
It's been reported three times, so people are definitely running into
it.
3625 has a simple patch to fix this.
--Simon
--~--~-~--~~~
I've started http://code.djangoproject.com/wiki/People and listed a
number of the core devs (the ones that came to mind at least - I'll
dig through AUTHORS later and add the rest), and the triagers. Anyone
else?
--Simon G.
On Mar 6, 10:23 am, "Jacob Kaplan-Moss" <[
Thanks Malcolm.
--Simon
--~--~-~--~~~---~--~~
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
Can someone revert http://code.djangoproject.com/wiki/DjangoPoweredSites
to the version 110, someone (220.227.72.2) deleted all the content and
I can't replace it (too many links, Akismet thinks it's spam).
We've been getting a few of these pop up recently, so it would be a
good idea to block the
I thought #3579 was more of a generic thing, but well spotted Gary!
-Simon
On Mar 3, 5:21 pm, "Gary Wilson" <[EMAIL PROTECTED]> wrote:
> On Mar 2, 6:38 pm, "Simon G." <[EMAIL PROTECTED]> wrote:
>
> > Can you drop by code.djangoproject.com and create
Hi Todd,
Can you drop by code.djangoproject.com and create a ticket for this,
so we don't lose trac (sorry) of it.
Thanks :)
Simon G.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&
field in Trac, that would be great. Otherwise, just mark them all as
"other-branch" and put [multi-db] in front of the ticket title like
the others have.
--Simon G.
On Mar 1, 6:39 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I've currently uncovered two bu
Hi dchandek,
This looks like an interesting idea - could you create a new ticket
for it at djangoproject.com, so it doesn't get lost?
Thanks,
Simon G.
On Feb 24, 9:44 am, "dchandek" <[EMAIL PROTECTED]> wrote:
> FWIW, I didn't see anything like this in the distribut
Hi Rob,
This looks good, thanks. I've triage'd that ticket on to "Ready to
checkin" and we'll let one of the core developers check it out and see
if it meets their approval :-)
-Simon G.
On Feb 24, 6:04 am, "Rob Hudson" <[EMAIL PROTECTED]> wrote:
things with core=True:
http://code.djangoproject.com/ticket/2724
Non-working prepopulate from:
http://code.djangoproject.com/ticket/957
A possible better way of doing things (which Adrian says is
"fantastic"):
http://code.djangoproject.com/ticket/2248
--Simon G.
--~--~-~--~
39 matches
Mail list logo
