roles
for exactly the reason Andrew mentioned here: there's no one ready to
replace us.
I think the discussions here are moving in the right direction. We are
looking at the community we have, and figuring out how to build and
maintain an active leadership group based on the current capaci
Hi, Contact me. I am an experienced Django developer, if you still need a
developer.
Thank you
*Kind Regards*
*Eric Bawakuno | Computer Engineer **| 247ERICPOINTCOM |
247ericpointcom.site** | +27795639700 | +27 815152254 | eric...@gmail.com
| **29 Rochester Road, Observatory | Cape Town, South
-utils) where there is some work
>> to update it, but after this, and if nobody else had enough time to have a
>> look, I can try to contribute on django-formtools.
>>
>> Romain.
>>
>> Le mercredi 4 janvier 2017 23:20:40 UTC, eric@datalyticsolutions.com
>
; more up-to-date than django-formtools. (4) Is this a sign that people
>>> simply aren't using Django for this task, and are maybe instead using some
>>> kind of Javascript library instead? If you have any information these
>>> questions, please let me know.
>&g
people
simply aren't using Django for this task, and are maybe instead using some
kind of Javascript library instead? If you have any information these
questions, please let me know.
Thanks,
Eric
On Tuesday, January 3, 2017 at 6:04:59 PM UTC-7, Tim Graham wrote:
>
> Is the situation
This is really bad. django-formtools used to be part of the core of Django.
Is this getting the attention it deserves from the Django Foundation?
On Monday, November 28, 2016 at 9:55:48 PM UTC-7, Asif Saifuddin wrote:
>
> Hi Tim,
>
> In case there is lack of active maintainers for the project the
Happy to help with this. We can move the RTD builds to using Sphinx
HTMLDir, and then redirects won't be necessary for the page titles, at
least.
On Thursday, February 18, 2016 at 12:58:03 PM UTC-4, Florian Apolloner
wrote:
>
>
>
> On Thursday, February 18, 2016 at 4:24:09 PM UTC+1, Tim Graham
1. it's not necessarily about SSL, it can be for any protocol but SITE
dependent.
2. and for the dev/prod , your data will be different anyway so you put
the preferred protocol accordingly to your setup.
3. it's only for generating full URLs, not for internal links (ex:
si
since no feedback has been given yet, I will add that the change is just
an addition (new feature) meaning there is no breaking of code , it just
provides a way to define a default protocol for a given SITE, and will
ultimately default to http when none is specified
--
You received this mes
Hi
I've created a ticket to propose adding a preferred/default protocol in the
"sites" framework at https://code.djangoproject.com/ticket/26079
tim suggested I bring this to the mailing list and said the following:
I'm not immediately convinced that a database field is the way to go for a
> co
t;>
>> On Tuesday, December 29, 2015 at 11:25:40 AM UTC-5, Tim Graham wrote:
>>>
>>> I've refined Daniele's explanation here:
>>> https://github.com/django/django/pull/5888
>>>
>>> Let me know if it helps and what could be better.
>
of sense to write down the logic and structure behind these decisions
in a DEP, and explain the layout to doc users in a few places in the
documentation explicitly.
Cheers,
Eric
--
You received this message because you are subscribed to the Google Groups
"Django developers (Con
arguments!
Thanks!
Eric
m: 312-399-1586
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to th
+1 for me too
On Thursday, March 6, 2014 3:28:59 PM UTC-5, Andre Terra wrote:
>
> +1, for one simple reason: practicality beats purity.
>
>
> On Wed, Mar 5, 2014 at 10:23 AM, Daniel Ellis
> > wrote:
>
>> +1 - I've had the same issue with sorl thumbnail.
>>
>>
>> On Wed, Mar 5, 2014 at 7:07 AM, Ad
Hi all,
I'm working on a project where I want to ignore certain files when running
collectstatic.
I am having success only when i use 'basename' patterns, such as *.exe or
vendor, but not when trying to match file paths, such as vendor/*.exe.
It seems the reason i'm not seeing the behavior i e
It's only able to access a field value in validator but it would be lacked
if checking request object data.
Should better to have another parameter for passing data to validators?
Maybe like this:
form = MyForm(request.POST, validator_data={'user': request.user})
def my_validator(value, valida
One question: does this proposal include some way of specifying a maxiumum
number of outstanding connections to the database from a single process?
Looked but didn't see it in the pull request. In my experience, most
PostgreSQL instances don't have a whole lot of breathing room in terms of
th
d be added to the docs before
release.
It'd be super nice if it worked with other field types, but I don't see it
being a big deal if it's documented as being that way.
On Tuesday, November 6, 2012 6:07:14 PM UTC-5, Russell Keith-Magee wrote:
>
> Hi Eric,
>
> Althou
I've been playing with custom user models. Something i've found is that
trying to use the django-extensions uuidfield as a primary key doesn't seem
very usable at the moment.
Many of the built in auth views, specifically password reset, assume an
integer field here.
/lib/python2.7/site-packag
.
0: http://mmstats.readthedocs.org/en/latest/
Cheers,
Eric
On Wednesday, October 31, 2012 3:41:05 PM UTC-7, jdunck wrote:
>
> If you use/monitor/graph metrics (the idea, not Coda's library, but that
> would be good, too), I'd like to hear from you.
>
> What sort of metrics,
t are specific to the underlying db (or not create if the db
doesn't support). This would be functionality not common in ORMs today,
and Django would be a trail-blazer in this area.
Are there any I'm missing? What seems like the most viable direction to
take?
Thanks!
Eric
--
You
performance/storage hit that isn't justified.
I am working around the problem now with a custom Field class, but it seems
to me that this is a feature that others may benefit from and wanted to
solicit feedback and ideas for if it should be an option, and if so, what
form it should take.
(e.g. 'user') and any other user-domain-specific customizations needed.
Thanks,
Eric Florenzano
>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google
d the tag
> names. It may not be important for jQuery, but if we implement
> verbatim, the output should be an exact copy of the verbatim contents.
This is true. I couldn't find an easy way to implement a verbatim tag
that was truly "verbatim" at the time without making
seemingly unrelated changes in there
having to do with password resetting, base64 url encoding, and file
uploading--none of which have to do with NoSQL.
Thanks,
Eric Florenzano
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
I would just like to point out that a lot of my users all are behind
various nats, so my webapp typically sees only a few ips that have
valid users on them, and i have users whom i have to remind of their
password on a daily basis. it could lead to a couple of dozen people
being throttled for one p
On Dec 23, 2:55 pm, Christophe Pettus wrote:
> On Dec 23, 2010, at 11:35 AM, Eric wrote:
>
> > a) To fix this, one must identify the sequences that are not correct.
> > I scoured pg_catalog and friends and cannot identify where PostgreSQL
> > exposes the link between the &
x27;%s','%s'))"
% (table_name, pk_name))
last_id = cursor.fetchone()[0]
if last_id is None:
raise IntegrityError("Valid sequence not found for %s.%s." %
(table_name, pk_name))
return last_id
would at least make this (and future sequence issues) at
at should be checked in
soon.
If you find something without a patch, I'd go ahead and confirm that the
issue is real, and then go ahead and try to fix it! Looking through Django's
source and fixing things is usually good fun.
In the spirit of Wikipedia, "Be Bold".
Che
Cody Soyland has also done some work on this in a reusable app, which might
be useful as a starting point:
http://github.com/codysoyland/django-smart-load-tag
Cheers,
Eric
--
Eric Holscher
Web Developer at The World Company in Lawrence, Ks
http://ericholscher.com
--
You received this message
f the DSF or anyone actually wants to pay
to have good CI.
Just as a data point, I took it down about a month ago, and people only just
noticed during the sprints. I don't know how to fix that particular problem.
Cheers,
Eric
--
You received this message because you are subscribed to
e it takes those inputs and assigns them to your provided
values.
[1]
http://github.com/django/django/blob/master/django/core/management/base.py#L216
Cheers,
Eric
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to th
em like a place that could use some expose either in the
docs or in the general community though.
Cheers,
Eric
On Thu, Jul 22, 2010 at 9:26 AM, Alex Robbins wrote:
> I am a huge fan of simple_tag and inclusion_tag. They take a common
> template tag use case and make it very easy to write
it's really great, now we just need to
figure out how to scale this up without using lots of human hours in the
process.
Cheers,
Eric
On Fri, Feb 26, 2010 at 1:08 PM, Mikhail Korobov wrote:
> That's great news, thanks!
>
> A very minor issue: web server returns 'Content
the pycon etherpad:
http://pyconpads.net/django-testing
Let me know if you have any thoughts, questions, or concerns.
Cheers,
Eric
--
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
Use Django Piston. It will make your life a ton easier.
Cheers,
Eric
On Wed, Feb 17, 2010 at 11:48 AM, orokusaki wrote:
> Addendum: I might be simply abusing `serialize`. I'm using it as a
> Django compatible `json.dumps` in order to provide a JSON API from my
> models to my J
ts on the
team to make those calls, so we need to bring in people who are
knowledge in that area. If there was someone in the community who has
contributed a lot, and knew a ton about security, it would seem like a
no brainer to make them a committer, with a Czar-like power over
security issues. I am mere
r the project. I agree he was never appointed, but that is
how things worked. If we are trying to establish process, or ideas about how
to perform a similar role, then the only thing that we have to look at is
how it was previously done.
Luckily we have an excellent model of how things worked previ
I went ahead and replied to this on my blog[0]. I'll copy it here for
completeness.
[0]:
http://ericholscher.com/blog/2010/feb/6/role-designers-django-community/
There has been a recent discussion on the Django Development mailing list
about the role of designers in the Django community. I think
Hi,
Django Developers is for development on Django. For usage questions you want
django-users: http://groups.google.com/group/django-users
Cheers,
Eric
On Thu, Jan 28, 2010 at 8:48 AM, rokson wrote:
> This is kiran .
> i am new to django fw.i installed django fw and trying to connect
&
in more abilities in the future, we don't blow up people's old test
runners that they have that don't support new options.
Otherwise this patch looks good, thanks for the work Russ.
Cheers,
Eric
--
You received this message because you are subscribed to the Google Groups
&qu
I'm alone.
I don't understand the argument for not including it. It's pretty
obviously wanted and it's not going to turn journalism on it's ear.
It would appear there is also very little cost to including it.
Eric
--
You received this message because you are subscribed
ttp://github.com/ericholscher/django/commit/b48b261d2533b45fd7bb955e50869aa1f41bab7b#L0R330
[3]
http://code.djangoproject.com/browser/django/trunk/django/core/management/__init__.py?rev=11526#L313
--
Eric Holscher
Web Developer at The World Company in Lawrence, Ks
http://ericholscher.com
--
You
I would be up for getting one together in Lawrence. Our offices at LJ World
have always been a good place in the past, and I'm sure we can use them
again.
--
Eric Holscher
Web Developer at The World Company in Lawrence, Ks
http://ericholsche
k that I had was that people liked being
able to download the whole source tree.
Hrm, I feel like I have more battle scars, but right now I can't think
of anything else. I'll be around so feel free to ask me any questions
or whatever.
Thanks,
Eric Florenzano
--~--~-~--~--
utside of Django than inside of it.
That being said, this proposal is actually something that I think fits
well within Django core itself, as it really is a logical extension of
the core functionality of the ORM.
Thanks,
Eric Florenzano
--~--~-~--~~~---~--~~
You
A big +1 on signed cookies, and I like the direction the discussion is
going.
Also, I hope this doesn't derail this discussion, but I hope after
signed cookies are added, auth can be made to optionally use signed
cookies instead of sessions.
Thanks,
Eric Flore
ww.sqlalchemy.org/docs/05/dbengine.html#configuring-logging
2:
http://www.sqlalchemy.org/trac/browser/sqlalchemy/trunk/lib/sqlalchemy/log.py
--
Eric Holscher
Web Developer at The World Company in Lawrence, Ks
http://ericholscher.com
--~--~-~--~~~---~--~~
You received
On Sep 17, 1:25 am, Simon Willison wrote:
> 1. We'll be able to de-emphasise the current default "e-mail all
> errors to someone" behaviour, which doesn't scale at all well.
I'm a big fan of this proposal, for exactly this reaso
At first glance, tests and documentation. Everything needs both of these
things before they go into trunk. Having a complete patch like that will
make it a lot easier for someone to see what you're doing, and verify that
you have fixed it.
Cheers,
.
>
> > 4. ManyToManyFields don't show up.
> >
>
> I don't see this problem, for example User/Group show the relationship
> in both directions correctly, since you clearly don't see it there's
> probably some more debugging work
put me down for the
1.2 time frame on this one.
Cheers,
Eric
--~--~-~--~~~---~--~~
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
et/11019andhttp://code.djangoproject.com/ticket/10761.
Aha, interesting... Thanks for the links.
E
>
> On May 22, 10:24 am, Eric Abrahamsen wrote:
>
>
>
> > I've got a Model A with a foreignkey to Model B, which is limited to
> > certain instances of Model B using limit_choices_to i
min functionality"
2. it's otherwise hard or messy or undesirable.
Does this seem like an acceptable idea?
Eric
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
s
> just leaving the door open for more additions in the future.
I don't really understand this argument. Maybe I'm not parsing it
correctly, but I read this as "Your implementation is good, but let's
not add it now so that we can add it later", whic
It took me a bit to realize that
it had to do with the CSRF middleware, and if it tripped me up, it's
going to trip up other users as well. If we're going to ship CSRF
middleware on by default, I propose that we take a second look at the
wontf
He's got a +1 from
me (not that it means much now that I'm on Malcolm's special list).
Speaking of Malcolm's special list...
> One suggestion Eric Florenzano had was that we go above and beyond
> just storing the methods and parameters, we don't even excecute them
&
If anyone else read this and was as confused as I was at first, make
sure to note that this is different than WTForms[1], which is an
alternate form library that took several of its cues from Django's
newforms.
[1] http://wtforms.simplecodes.com/
Thanks,
Eric Flore
]
http://code.google.com/p/django-atompub/source/browse/trunk/atompub/atom.py#475
[1] http://code.google.com/p/django-atompub/source/browse/trunk/atompub/atom.py
[2]
http://code.google.com/p/django-atompub/source/browse/trunk/atompub/test_validation.py
Cheers,
Eric
--~--~-~--~~
Looking back through the history of django-dev will probably get you some of
the design discussion that went on around this project. An example is:
http://groups.google.com/group/django-developers/browse_thread/thread/a121b2ed850c93ab/d370133daeeb4b34?lnk=gst&q=rest+api#d370133daeeb4b34
Hope this
eclared unique in the Meta unique_together.
>
>
> This is still a legitimate issue during serialization, it's great to
> see someone has made steps in the right direction.
Glad it's been helpful. I want to get this into a more generic solution, and
hopefully get part of it into dj
re a special case for content type things (or some other
approach which I haven't thought of). Having references to contrib apps is
frowned upon, so I think having a third party serializer that does this is
the answer for now.
Hope this helps
1.
http://
On Thu, Jan 15, 2009 at 12:06 PM, Karen Tracey wrote:
> On Wed, Jan 14, 2009 at 5:35 PM, Russell Keith-Magee <
> freakboy3...@gmail.com> wrote:
>
>>
>> On Thu, Jan 15, 2009 at 5:40 AM, Eric Holscher
>> wrote:
>> > I think that if there is a plan to ev
ating the objects yourself.
This means that we will internally write out doctests that require fixtures
back into unit tests, but this isn't a huge deal.
I think we should just decide now, and stick with it. I really don't have a
preference, because I don't thin
"s for 1.1 having been committed..)
Cheers,
Eric
1: http://code.djangoproject.com/wiki/Version1.1Roadmap
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this gr
Name it whatever you want. It's your bikeshed.
Eric
On Sun, Dec 21, 2008 at 11:55 PM, Maluku wrote:
>
> DTL seems to be too short...
>
> What about "Dotiac" (DjangO Template Interpreter And Compiler), which
> works as a name and an abbreviation.
>
> Malu
Check out http://twitter.com/DjangoTracker
Eric
On Fri, Dec 5, 2008 at 1:02 PM, David Reynolds
<[EMAIL PROTECTED]>wrote:
>
> Hi,
>
> Since a lot of Djangonauts and Django Developers are using twitter,
> would anyone find it useful to get svn commit messages on twitter?
&
thread.
>
> True, but that's because python-memcached for some reason still uses its
> own hashing algorithm (pure CRC32) while other libraries are more or
> less
> unified in their hashing algorithm. (Wouldn't know about libmemcached.)
>
> *ugh* Why can you never eat th
> ``response.context`` to avoid this sort of problem? Unless I'm
> thinking about this the wrong way, it shouldn't be too hard to
> differentiate dictionary-style access from list-style access, since
> the former -- in the case of a Context -- will always be using string
> keys
s could be modified to set this attribute,
however this is probably unlikely now that 1.0 has hit.
Perhaps you could post your code somewhere so that 3rd-party app
developers can standardize their authorization (git-hub?).
Eric
On Oct 13, 7:11 am, Thomas Guettler <[EMAIL PROTECTED]> wrote:
&g
; wrote:
> >>
> >> How about
> >>
> >> {% for item in items %}
> >> {% otherwise %}
> >> {% endfor %}
> >>
>
> +1 to the otherwise tag :)
>
>
> --
> Antoni Aloy López
> Blog: http://trespams.com
>
> I would be surprised if it works with Oracle, unless you replace
> IntegerField with CharField(max_length=18).
I made tests only on sqlite (a trac db).
I mean it ''should'' works with Oracle because Oracle support oid's;
but I have made no test. If someone want to ...
--~--~-~--~~-
provides 2
methods:
- use of oid field (works on sqlite, oracle, postgres <= 8)
- composite pk (for mysql that provides no oid field)
cheers,
Eric
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&
On Oct 2, 4:51 pm, Ludvig Ericson <[EMAIL PROTECTED]> wrote:
> On Oct 2, 2008, at 10:31, Eric wrote:
>
>
>
>
>
> > Hi,
> > I saw few questions from people who wonder how to manage tables
> > without primary key (when using inspectdb on a legacy db);
&
) in the
model:
rowid = models.IntegerField(primary_key=True, editable=False)
It works ! it's so simple ! I love django !
Maybe this tip could be added in the doc; for others sgbd, there must
be something similar.
And why not put this in the inspectdb command ...
cheers,
Eric
PS:
You can just put a models.py there that is empty. A slight hack, but it
should work just fine. (Think of it as __init__.py's big brother :))
Eric
On Tue, Sep 23, 2008 at 2:27 PM, Adam J. Forster <[EMAIL PROTECTED]>wrote:
>
> Firstly I'm sorry if I have posted this in
Haha, yea, sorry.
On Wed, Sep 10, 2008 at 11:17 AM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 10, 2008 at 12:12 PM, Eric Holscher <[EMAIL PROTECTED]>wrote:
>
>> Yea, I totally agree with this.
>>
>> I wrote a blog post about how to use setuptools
Pypi.
Eric
On Wed, Sep 10, 2008 at 10:57 AM, James Bennett <[EMAIL PROTECTED]>wrote:
>
> On Wed, Sep 10, 2008 at 9:31 AM, mrts <[EMAIL PROTECTED]> wrote:
> > * create a central app index à la Cheeseshop
>
> Doesn't the Cheese Shop already exist?
>
> > * c
em with my code as with the sql.
On Aug 21, 10:35 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Thu, 2008-08-21 at 07:23 -0700, Eric Montgomery wrote:
> > I'm not exactly sure what's going on here, and I managed to "fix" it
> > by switching my sto
out
exactly what was going on with the foreign key constraint error, so to
play that safe, I switched to myisam, although I would like to use
innodb if I can make it work.
If anything in my explanation was unclear (it all happened around 3am
last night), let me know and I can try to clear things up
I think the TWID guys are doing something as well. Might want to combine
groups.
Eric
On Wed, Aug 20, 2008 at 11:21 PM, Jonathan Nelson <[EMAIL PROTECTED]>wrote:
>
> I'm planning a get together the night before DjangoCon for people
> going to the conference. I figured it
Well, you can teach someone to fish without telling them to "get an
f'n fishing pole".
On Jul 1, 5:25 am, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 26-Jun-08, at 7:51 PM, Jeremy Dunck wrote:
>
> >> Then, I tried helping people the way he does for a mere fraction of
> >> the time he does.
The guy is rude. I never go in the IRC channel to help because he's
there being an ass.
The reason why I fell in love with Django way back in 2005 was because
of the community in #django and I'm worried that he's stunting
adoption because he's turned the channel into #linux.
E.
On Jul 2, 7:41
of the stability of using 0.96
without the need of a massive port when 1.0 comes out.
Eric.
On Jun 8, 11:11 am, Phil M <[EMAIL PROTECTED]> wrote:
> On Jun 8, 9:27 am, Wim Feijen <[EMAIL PROTECTED]> wrote:
>
> > My vote is +1, because I think Django needs another stable
your
progress, trying your code and reporting issues if you are open to
it. If you start a mailing list or wiki or somesuch on your project,
please announce it on django-dev so I can follow along.
Best regards,
Eric.
--~--~-~--~~~---~--~~
You received this messag
n -- and is encouraged to -- help out keeping tickets
> organized, these folks have volunteered to take ownership of the ticket
> tracker in the long term.
>
> Let's have a big virtual standing ovation for them!
Cheers Chris, Simon, Michael, Gary
Hawkeye wrote:
> ===
> (100 chars ~ 25% reduction)
...
> My second question is... if we can, is there any real value
> (specifically for very large sites)?
Our site isn't huge, but it's not small, either (~8M records). Network
bandwidth between the web and data servers is very near
On Monday 27 March 2006 15:22, binaryfeed wrote:
> gabor wrote:
> > is there a plan or a rough estimate about when the magic-removal
> > branch is going to be merged back to the trunk?
> >
> > this month?
> > next year?
>
> What's most frustrating about this thread is that no one has
> responded,
I wrote a custom tag that allows you to cache an expression in a
template.
I noticed, that my template was sending many duplicate queries to the
database because I was using a method in my model that used a foreign
key in a loop with many repeats.
I could have recoded the view to generate all th
One of the most respected and award-winning newspaper Web teams in the
world has moved to Florida and is looking for an experienced
server-side Web developer.
NDN Productions -- the online and new media publishing division of the
Naples Daily News -- is looking for a full-time Python programmer t
On Tuesday 08 November 2005 08:35, Jacob Kaplan-Moss wrote:
> I think we need to bite our lips, suck it up, and release a 1.0
> version.
+1
A "stable" release would make those who are trusting my judgement in
choosing Django for a medium-large-ish project a little less nervous
(me, too).
91 matches
Mail list logo
