Hi, would like to partner with you on the project, I like the idea behind
it, and I think you should make it a part of Django rather than a separate
package, also there's a code am working on
On Thu, 23 Mar 2023, 14:19 Raza ul Mustafa, wrote:
> Hey Django developers,
>
> I am a Django developer
On Mon, Oct 31, 2022 at 11:52 AM Florian Apolloner
wrote:
> On Monday, October 31, 2022 at 5:27:02 PM UTC+1 pe...@lincolnloop.com
> wrote:
>
>> In my ideal scenario, the default is a hard-coded settings file for the
>> project (deprecating DJANGO_SETTINGS_MODULE env var) and we have
>> CONFIG_LOA
On Sun, Oct 30, 2022 at 7:57 AM Florian Apolloner
wrote:
> Hi Peter,
>
> On Saturday, October 29, 2022 at 6:07:16 PM UTC+2 pe...@lincolnloop.com
> wrote:
>
>> Since you asked for feedback, I'll tell you what I'd do differently (and
>>> this is also a sign
de):
>
> "We’ve included this with Django so you can develop things rapidly,
> without having to deal with configuring a production server – such as
> Apache – until you’re ready for production."
>
> https://docs.djangoproject.com/en/4.1/intro/tutorial01/
>
&
On Sat, Oct 29, 2022 at 10:06 AM Peter Baumgartner
wrote:
> Thanks for the thorough review Florian! Some comments inline...
>
> On Wed, Oct 26, 2022 at 1:30 AM Florian Apolloner
> wrote:
>
>> Hi Pete,
>>
>> this does look interesting. And I agree that this is s
project template,
>>>> which I think is related here. (That's on my list too: async this QTR, then
>>>> hoping to take on Adam's proposal to modernise the Request object for the
>>>> end of year, then 🤞 swinging back here for "OK, what does it look l
I think is related here. (That's on my list too: async this QTR, then
>>>> hoping to take on Adam's proposal to modernise the Request object for the
>>>> end of year, then 🤞 swinging back here for "OK, what does it look like,
>>>> what can we do?
ar up...)
>>
>> I think all these thoughts are really pursuable outside of core in the
>> very short run, even if the goal is to merge them — it's much easier to
>> experiment that way, and then say, "This worked".
>>
>> Anyhow, other than a "I&
d and use the terms "backend" and
"engine" pretty much interchangeably. The code is naturally more strict, but the iterable
holding the backends nevertheless is called `engines`.
If people feel this is a correct assessment, I can try improving on the wording.
Thanks,
Peter
--
https:
t; INSTALLED_APPS doesn't seem too much to ask (I think.)
>
> Was it really 4 years ago Tom left that comment on #21978 😳 (We'd finally
> close this as wontfix: Django doesn't ship a webserver.)
>
> Does that fit in your view, or would that scenario not be good eno
Hi all! I'd like to re-open the discussion around
https://code.djangoproject.com/ticket/21978
As a "batteries included" framework, Django kind of leaves people to
fend for themselves when it comes to deployment. This makes it harder
than necessary for a developer to go from works-on-my-laptop to
w
g the exception), whereas that complexity already is
in the core.
Please let me know what you think!
Thanks,
Peter
--
https://desec.io/
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To u
Hi folks,
An email with an update on ticket that I'm subscribed to has ended up in my
gmail spam folder:
[image: image.png]
I'm not sure what to suggest!
Peter.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions t
Thanks Hasan for offering to help.
Either of Carles's approaches would work -- I don't have a strong view.
Making the smaller fix (ie adding transform=str every time
assertQuerysetEqual fails) would require the least thinking. But it may
miss some good opportunities to refactor or simplify the te
of test failures.
Unfortunately I have no spare time at the moment to resolve these. Would
anybody on this list like to take the PR off my hands?
Thanks!
Peter.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)"
Hi list,
When developing on Windows I was recently bit by Windows providing wrong
MIME type mappings for file names. I filed a ticked for that which has more
details [1], but given it was summarily closed as not a bug in Django I
wanted to see if there were broader opinions on the matter.
[1]
Hi folks,
Is there any moderation for posts from new users? It can be enabled
<https://support.google.com/groups/answer/2466386?hl=en>, and I'd be
willing to be part of a team that filters posts from new users.
All the best,
Peter.
On Thu, 9 Jul 2020 at 13:59, Adam Johnson wrote:
You might find https://github.com/lincolnloop/goodconf interesting. I
see some overlap there with what you're doing.
On Mon, Mar 23, 2020 at 9:43 AM Abhirav Dilip Kariya
wrote:
>
> Hi,
>
> Thank your for the suggestion.
>
> I did look at some libraries. However, the libraries I looked into (or
ment is passed, and the second argument is not
a list of strings, then transform is set to the identity function.
As far as I can tell, this would not introduce a meaningful backwards
incompatibility.
I'm willing to do the work to add code and documentation etc.
All the best,
Peter.
--
You re
in last year
> <https://code.djangoproject.com/query?status=assigned&status=new&changetime=09%2F26%2F2018..09%2F26%2F2019&stage=Accepted>:
>
> 329
>
>
> So if we would decide to close stalled tickets after some inactivity
> period we could massively reduce the
nit__.py file to have
> something be a module (because of
> https://www.python.org/dev/peps/pep-0420/), but I wonder if there still needs
> to be a proper discovery mechanism that flags that they should be considered
> as implicit packages/modules.
>
> Andrew
>
&g
bit more, though. If we can get Django
> compatible, or work with PyOxidiser if we find a reasonable workaround they
> could implement, it would be great.
>
> Andrew
>
> On Thu, Jun 27, 2019 at 12:39 PM Markus Holtermann
> wrote:
>>
>> Hi Peter,
>>
I'm interested in using PyOxidizer [1] to create single-file executable
Django projects. This currently isn't possible because of all the places
Django assumes it is operating on a proper filesystem. I haven't done a
full audit, but templates, migrations, and static files come to mind.
Python h
So
I'm curious what people's opinions are regarding this.
Best,
Peter J. Farrell
--
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
I implemented something for this in the django-alive package via a
middleware that will bypass the host checking:
https://github.com/lincolnloop/django-alive/#disabling-allowed_hosts-for-healthchecks
https://github.com/lincolnloop/django-alive/blob/master/django_alive/middleware.py
On Fri, Sep 14
does by adding it to the
__init__ module's locals(), which makes `functions` available as a label
in the remainder of the code.
Note that I can't actually find the chapter and verse for how this works in
the Python docs, but I've been caught out by something similar in the past!
Hope this
Reporting back on some additional findings for what it's worth.
SmileyChris dumped and recreated the project in question's migrations,
manually ordering them to minimize dependencies. It was not a major
reduction in total migrations: 82 to 58 (mostly third-party migrations
and initials), but the ti
It looks like there are some other fixes in 1.9 that weren't covered
by my monkeypatch. I upgraded the project and included a new cProfile
in the ticket https://code.djangoproject.com/ticket/22608#comment:23.
It shaved 100s off, but still takes 2.5 minutes to create an empty
migration.
Florian, I'
I agree there are many ways to accomplishing things in the admin, but
cleaning that up and continuing BC is a completely other ticket /
implementation (it looks like a good Sumer of Code project similar to the
Meta API recently completed). Since the ticket was marked as accepted,
I'll double c
In our case, we need to dynamically include additional "exclude" fields in
our VersionableAdmin and not override the selections the developer has set
in their subclass. There are two options to accomplished this:
1) Override get_form() which is messy because you can't just call super
here and
We are writing a custom admin for CleanerVersion that subclasses ModelAdmin.
Just about every attribute has a hook method which makes extension easier. For
example, list_display has get_list_display(). However, exclude doesn't have one
implemented and it seems like an oversight. I'm proposing we
Official ticket:
https://code.djangoproject.com/ticket/24637
PR:
https://github.com/django/django/pull/4494
Sqlite 3.8.9 which was just released on 4/8/2015 as gold has changed
behavior with index_list() functionality by adding 2 more columns of data
the returned queryset. This breaks introspe
This thread was started in django-users, but commented that it should be
moved to developers list instead.
Take a look at the original thread
here: https://groups.google.com/forum/#!topic/django-users/F0J6fKP1un8
--
You received this message because you are subscribed to the Google Groups
"Dj
Hi Arun,
This group is for discussion of development of Django itself. Your
question is better suited to the 'Django users' group:
https://groups.google.com/forum/#!forum/django-users
All the best,
Peter
On 18 November 2014 15:51, Arun Marathe wrote:
>
>
>
> We have
want some way to declare what defaults
> to keep. (South actually used to have this with a keep_default option on
> the add_column method but it was kind of unmaintained)
>
> Andrew
>
> On Thu, Oct 30, 2014 at 1:45 PM, Peter Coles > wrote:
>
>> Thanks for the quick
have more
input on using it in practice and probably find some lurking bug somewhere.
Worst case, other people who really want this functionality could use this
as a 3rd-party dependency. Regardless, I think the docs should be clearer
about defaults not getting set in the db.
On Thursday, O
ngo-postgres-dbdefaults
and here it is in pypi:
https://pypi.python.org/pypi/django-postgres-dbdefaults/0.0.1
I'd love to hear feedback/thoughts/concerns.
-Peter
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Djang
or default?
The MySQL documentation is mostly due to INSERT...ON DUPLICATE UPDATE
completely breaking their statement-based replication. I accept that
there are other hazards, but it's difficult to have a fully general
syntax that indicates user intent WRT the unique index to merge on.
--
Peter
On Tue, Sep 30, 2014 at 12:37 AM, Anssi Kääriäinen
wrote:
> The main point is that having WITHIN PRIMARY KEY syntax would make usage
> of this feature a lot easier for us.
I was thinking about doing that anyway.
--
Peter Geoghegan
--
You received this message because you are subscri
think that there is an
incredible amount of misinformation about this topic floating around.
The various vendors that have a MERGE feature should have clearly
indicated that MERGE isn't useful for implementing an UPSERT, but they
didn't, and so the problem persists.
--
Peter Geoghegan
-
-insert-into-a-table/2249#2249
Would you be happier with that?
--
Peter Geoghegan
--
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 e
antees, and they're both non-standard.
[1]
http://www.postgresql.org/message-id/flat/CAM3SWZRP0c3g6+aJ=yydgyactzg0xa8-1_fcvo5xm7hrel3...@mail.gmail.com#CAM3SWZRP0c3g6+aJ=yydgyactzg0xa8-1_fcvo5xm7hrel3...@mail.gmail.com
--
Peter Geoghegan
--
You received this message because you are su
On Sat, Sep 27, 2014 at 6:33 PM, Peter Geoghegan wrote:
> The statement-level trigger stuff (i.e. the idea that ON CONFLICT
> UPDATE never fires an UPDATE statement level trigger) is for
> consistency with user-defined rules, where we're really compelled to
> have INSERT...ON CON
that that isn't a very satisfactory state of affairs for people
who are using per-statement triggers for auditing and things like
that, and I wouldn't be surprised if that was revised.
--
Peter Geoghegan
--
You received this message because you are subscribed to the Google Groups
"Dja
ut
which unique index I mean"? It turns out that that's quite ticklish in
certain edge cases (e.g. partial unique indexes with BEFORE triggers).
We might come up with a better way that's fully general, but I'm not
holding my breath.
> I think even under MySQL it doesn't use
id/CAM3SWZRvkCKc=1Y6_Wn8mk97_Vi8+j-aX-RY-=msrjvu-ec...@mail.gmail.com
You'll need to build PostgreSQL from the git master branch (which
includes dependencies on things like Flex and Bison), with the patch
set applied. There are guides to doing this on the internet, including
this one: http://
This is in reference to this ticket:
https://code.djangoproject.com/ticket/17092
There is a patch there to fix the specific use case of needing to disable
django's fix_location_header for certain responses in a CGI compliant
environment. Because of the way that response_fixes work you can't jus
ngs much easier to sell
in shops that value stability and support, if this alternative solution is
better known.
Regards,
---Peter
On Jun 29, 2013, at 5:08 AM, Florian Apolloner wrote:
> Hi,
>
> On Friday, June 28, 2013 4:17:22 PM UTC+2, Aymeric Augustin wrote:
> As far as I can t
+1 on pre_syncdb
On Tuesday, May 21, 2013 8:29:49 AM UTC-7, Shai Berger wrote:
>
> On Tuesday 21 May 2013, Donald Stufft wrote:
> > I run migrations in test. How else will you know your db reflects
> reality
> > :/
> >
>
> When you have a few hundred migrations, that's something you're willin
I have a thought on an action we could take out of this that might be
constructive.
Would it be possible to customise trak at all to make the workflow clearer?
I'm thinking if someone tries to open a ticket that was closed by a committer
then they should get an intermediate page pointing them
Hi everyone,
This is about ticket (https://code.djangoproject.com/ticket/13794) where
inline formsets don't respect a foreign key's to_field. I've written about
this issue before, even tried a 5 for 1 but I'm having a hard time getting
feedback on it. This bug doesn't just affect django admin b
Thank you aaugustin for taking a look at
https://code.djangoproject.com/ticket/13794. I've made some further updates
but haven't heard anything back in a few weeks. Even though the original
ticket title and description makes it sound like a fairly minor bug I do
want to point out that as with m
Not sure if this is still a thing, but i'd like to ask for a review of this
ticket:
https://code.djangoproject.com/ticket/13794
I triaged/reviewed the following tickets: #18201, #19668, #19663, #19617,
#19624
--
You received this message because you are subscribed to the Google Groups
"Djang
data loss is a possibility.
Monday, August 27, 2012 5:33:03 PM UTC-7, Russell Keith-Magee wrote:
> On Tue, Aug 28, 2012 at 3:11 AM, peter >
> wrote:
> > I opened this ticket (https://code.djangoproject.com/ticket/18823) on
> the
> > Trac but thought i'd bring it
I opened this ticket (https://code.djangoproject.com/ticket/18823) on the
Trac but thought i'd bring it up here to increase the likelihood of it
getting noticed. In short things don't quite work right when you have a m2m
field that uses a through model that uses a to_field for it's foreign
key.
whole form ( {{ form.as_p }} ) you'll see your
new sensitive field appear in the page. If you manually render the form,
you'll get a warning.
One problem would be excessive warnings if you went further and hand craft
the HTML - does anyone do that?
Cheers,
Peter
--
You received this
I'd just like to chime in to say this should definitely be part of
core - it's a common requirement, and whilst it could be a third party
app, it certainly feels much more at home in core.
On Sep 27, 1:13 pm, Luke Plant wrote:
> For me, QuerySet is at a level of abstraction where I don't think it
Essentially, you want a compare-and--swap instruction for a database?
Have you considered using memcached atomicity (add and cas) to handle this
kind of thing? It might get pretty elaborate, but with just a cursory
thought seems doable.
-peter
On Sat, Aug 6, 2011 at 9:59 PM, Steven Cummings
On Tue, Jun 21, 2011 at 8:43 PM, Ramiro Morales wrote:
> That's what [1]ticket 11665 reports.
So it does! I'd just hit the problem when I wrote my mail, and hadn't
checked Trac yet.
I guess I'll apply the patch and see if it solves my problem tomorrow.
Thanks
Peter
o have
Django mess with unmanaged tables.
I'll have a play and see how hard it would be.
Thanks
Peter Russell
--
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
FWIW: we are successfully using Ned's fix on top of 1.2.5 today. -peter
--
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
ort. If I fix the ImportError
then I won't have this problem. I suppose this will probably
break someone's code though :-(
3. Make the cache of model definitions behave transactionally.
When importing an app raises ImportError, remove all of the
models which have been inserted sin
See ticket 15840.
On Thu, Apr 14, 2011 at 9:25 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
> On Thu, Apr 14, 2011 at 8:16 PM, Peter Portante
> wrote:
> > Looking at line 153 of django/views/decorators/http.py (rev [15927]),
> > I just see "return
+1 from the Tabblo group remnants.
On Thu, Apr 14, 2011 at 8:41 AM, Ned Batchelder wrote:
> Does anyone else have any opinions on a direction forward to fix this
> problem? At the very least I'd like to make a doc patch for 1.3.1 that
> explains the fragility.
>
>
--
You received this message
Looking at line 153 of django/views/decorators/http.py (rev [15927]),
I just see "return inner". Is there a particular reason why it should
not be: "return wraps(func, assigned=available_attrs(func))(inner)"?
--
You received this message because you are subscribed to the Google Groups
"Django de
n you still get the old message.
That way, you can only gain more information than with the current
system when you have
both a username and correct password. If an attacker has that
information, then frankly,
it's too late to be thinking about how to make things more secure.
Regards,
Peter
-
On Feb 6, 8:45 pm, Simon Meers wrote:
> 2011/2/5 Carl Meyer
> > Hi Mike,
>
> > On Feb 3, 4:36 pm, Mike Lindsey wrote:
> > > I'm doing something with bidirectional ManyToManyFields, in a project
> > > I'm working on, that is resulting in duplicate attempts to create the
> > > intermediate table
I'm not an expert, but that's correct. A too-fast or broken hash function
will still be "vulnerable" to a brute force attack [1]. Salting doesn't
prevent this.
Peter
[1]
http://stacksmashing.net/2010/11/15/cracking-in-the-cloud-amazons-new-ec2-gp
u-instances/
On
On Thu, Nov 4, 2010 at 5:37 AM, silent1mezzo wrote:
> +1 for {% include "foo.html" x=1 y=2 %}
>
> This just seems more natural. My designer agreed based on the {% url
> %} tags.
>
+1 for using the = syntax here. My reasons have been mentioned above,
but to recap:
* and/as gets too verbose and d
On Nov 8, 2010, at 9:14 AM, Carl Meyer wrote:
> Hi Peter,
>
> On Nov 7, 9:41 pm, Peter Herndon wrote:
>> I just ran into a minor issue and thought I'd bring it to light. In adding
>> django.contrib.comments to a site I'm building, I found that when u
imal.
I'm happy to open a ticket, but should the solution be to include a default
template, to add relevant documentation pointing out the customization
possibility, or both?
Regards (and many thanks for an incredible framework!),
---Peter Herndon
--
You received this message because you ar
est and if James was
> willing.
>
> Jacob
I think South is the best candidate here, because it could improve the third
party app ecosystem to have a stable and consistent migration framework
battery included. DDT and django-registration both stand alone pretty well,
so I see less benefit (thoug
It just moved. See:
http://code.djangoproject.com/browser/django/trunk/django/forms/fields.py#L924
http://code.djangoproject.com/browser/django/trunk/django/core/validators.py#L122
-- Pete
On Tue, Oct 12, 2010 at 8:44 AM, Sebastian wrote:
> Hello,
> I investigated a bit further, it was commited
On 16 June 2010 13:53, George Sakkis wrote:
> On Jun 16, 4:22 pm, Peter Bengtsson wrote:
>
>> I have a modelform where I change the cleaned_data dict after I have
>> run is_valid() and I'm not sure if this is the totally wrong way of
>> doing things or if it
I have a modelform where I change the cleaned_data dict after I have
run is_valid() and I'm not sure if this is the totally wrong way of
doing things or if it's a bug.
My code broke when I upgraded to 1.2 so it did work back in the 1.1
days.
# models.py
class Person(models.Model):
name = model
Submitted here: http://code.djangoproject.com/ticket/13776
On Jun 14, 2:05 pm, Karen Tracey wrote:
> On Mon, Jun 14, 2010 at 12:39 PM, Peter Bengtsson wrote:
> > I'm happy to submit a ticket but wanted to check first that I'm doing
> > the right thing. I think this u
rms import FooBarForm
post = {'name':'Peter'}
f2 = FooBarForm(data=post)
self.assertTrue(not f2.is_valid())
Instead of returning False on the is_valid() function, it raises a
ValueError which looks like this:
Traceback (most recent call last):
File "/
On Fri, Jun 11, 2010 at 9:16 AM, Andrew Godwin wrote:
>
>
> On 11/06/2010 03:28, Peter Baumgartner wrote:
>>
>> In my experience, almost every project has domain-specific
>> applications that don't get reused. If you have a reusable app, you
>> bundle it sepa
On Thu, Jun 10, 2010 at 11:21 AM, Andrew Godwin wrote:
> Hi all,
>
> I noticed today that the tutorial still does imports like "from
> mysite.polls.models import Poll", and URLs like "(r'^polls/$',
> 'mysite.polls.views.index')".
>
> At least in the places and projects I've worked with, the standa
delete with a query set.
>
> I opened a new ticket:
>
> http://code.djangoproject.com/ticket/13731
>
> Thomas
>
> Russell Keith-Magee wrote:
>> On Wed, Jun 9, 2010 at 3:53 AM, Peter Bengtsson wrote:
>>> On 8 June 2010 13:09, Jeremy Dunck wrote:
>>>
On 8 June 2010 13:09, Jeremy Dunck wrote:
> On Tue, Jun 8, 2010 at 7:30 AM, Peter Bengtsson wrote:
>> I've now had to learn this the hard way by having real live data
>> deleted from my database on two production projects and it pisses me
>> off big time every time.
&
I've now had to learn this the hard way by having real live data
deleted from my database on two production projects and it pisses me
off big time every time.
I can accept that NOT nullable foreign relations cascade the delete
but not if they have null=True on them. Example:
class Survey(Models):
On May 12, 8:54 am, Russell Keith-Magee
wrote:
>
> FYI - I got itchy fingers, so I opened a bug report:
>
> http://code.djangoproject.com/ticket/13528
>
> Yours
> Russ Magee %-)
No problem. Thanks
Peter Long
--
You received this message because you are subscribed
on and in
addition it appears the correct way to get a connection is to "ask" a
router what connection to use for a given Model instance. Since
Options is part of a Model instance's _meta instance I am not sure how
I would call router.db_for_read() from a Options getter method.
Pet
Hi Django developers,
I have been using the development copy of django from the svn trunk. I
think I may have found an area that needs updating now that django
supports multiple databases. I am not very familiar with the django
backend architecture so I am not sure if its a real bug or not and if
On Mon, Apr 19, 2010 at 8:19 AM, Jacob Kaplan-Moss wrote:
> Hi folks --
>
> I'd like to try to reboot the discussion that's been going on about
> Django's development process.
>
> I'm finding the current thread incredibly demoralizing: there's a
> bunch of frustration being expressed, and I hear t
On 4/19/10 11:41 AM, "Jacob Kaplan-Moss" wrote:
> On Mon, Apr 19, 2010 at 9:54 AM, Peter Landry wrote:
>> One suggestion that jumped out at me (which I admittedly know very little
>> history about with regards to Django or other projects) was the "trunk
>&g
ggesting any concrete plans for how that might
happen though. A single almost-trunk branch? A branch per
lieutenant/component? I'm wary of adding too much bureaucracy and overhead.
I think it's pretty clear that the core Django process is successful, and
this seems like a low impact (though
On Mar 5, 2010, at 11:35 AM, stherrien wrote:
> What I'm suggesting is that we setup something to allow everyone to
> improve the docs with help from the core django group. I think this
> would be very helpful to everyone. if one of the core group would like
> to help us get setup to do this it w
Thanks, Joseph.
I agree it works well as an external project. It's been on pypi for a little
while[1] and I added the link again to the bottom of the (now closed) ticket.
Incidentally, #2507[2] is a rather old and dusty ticket on the same subject.
Thanks,
Peter
[1] http://pypi.python.org
ise on the correct procedure here?
Thanks,
Peter
[1] http://code.djangoproject.com/ticket/11526
--
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 f
I don't think this is a bug; it's just telling you that you can't count the
photos until the gallery is in the database. Try:
x = Gallery.objects.create()
x.photo_count()
On Jan 24, 2010, at 3:14 PM, x13 wrote:
> (sorry for my English mistakes)
> Hello all, I have a problem with the count() fu
complexity (multi-db, email backends), due to
requirements from the current community.
My two cents, appropriately adjusted for the current economic situation.
---Peter Herndon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To po
ay to
express support for a feature/ticket then? If the original argument is "not
enough people want it", I think it's fair that people voice their support,
and most have included specific use cases. What is the alternative?
Peter
--
You received this message because you are subscribe
that these other solutions don't?
>
> [1] http://mattsnider.com/css/css-string-truncation-with-ellipsis/
>
> Ian
>
Hello,
To address specifically this point, I would suggest that there might be use
cases where CSS isn't available to accomplish truncation (non-HTML text
I just noticed and can only agree... nice work.
//Peter
On Tue, Dec 22, 2009 at 18:27, Simon Willison wrote:
> And a big congratulations to all involved. Here's the changeset log
> (on GitHub since Trac seems not to like being linked to at the
> moment):
>
>
> http://g
here could
> be a valid need for a google-style search of the column and this is
> where DB2 and Oracle support 'Text' indexing of LOB columns.
>
> Peter, maybe you can elaborate why you choose 'Text' and why you need
> an a unique index on it.
>
I chose Tex
On Dec 18, 2009, at 12:02 PM, Ian Kelly wrote:
> On Fri, Dec 18, 2009 at 9:00 AM, Peter Herndon wrote:
>> Hi all,
>>
>> I've run into a situation where syncdb produces an error on one of my models
>> against Oracle, but not against Postgres. Using Postgres,
ould
be specially handled by the Oracle backend somewhere? If the latter, I'm happy
to file a bug report.
Thanks very much for all your hard work in creating and improving Django, I
really appreciate all your work, it's made my life much easier.
Regards,
---Peter Herndon
--
Yo
Thanks for the help. Patch uploaded
http://code.djangoproject.com/ticket/11421
On Oct 21, 6:49 pm, Peter Bengtsson wrote:
> On 21 Oct, 16:34, Jacob Kaplan-Moss wrote:> On Wed, Oct
> 21, 2009 at 9:29 AM, Peter Bengtsson wrote:
> > > But how do I run these? It takes many m
1 - 100 of 167 matches
Mail list logo
