I am already posted it on Django Snippets
http://www.djangosnippets.org/snippets/1218/
I want to introduce my idea about url resolving in Django.
It can be useful for using object-oriented includes in common patter.
It can be useful for created function which will be running only
before
angoproject.com/en/dev/internals/contributing/
>
> 2016-08-12 11:23 GMT+02:00 Alexander Lyabah <a.ly...@checkio.org
> >:
> > Hi Django developers.
> >
> > My name is Alex I’m CEO and founder of CheckiO. I hope I found a right
> place
> > to post this ki
Hi Django developers.
My name is Alex I’m CEO and founder of CheckiO. I hope I found a right
place to post this kind of message.
CheckiO is a game for python developers where players solving puzzles and
improving their coding skills by sharing their solution and checking
solutions of other
Django Doc has several pages about testing
https://docs.djangoproject.com/en/1.11/intro/tutorial05/
https://docs.djangoproject.com/en/1.11/topics/testing/tools/
https://docs.djangoproject.com/en/1.11/topics/testing/advanced/
On Thursday, September 21, 2017 at 8:55:59 PM UTC+3, Heba Khan wrote:
>
ind one?
On Tuesday, September 5, 2017 at 5:06:20 PM UTC+3, Daniele Procida wrote:
>
> On Tue, Sep 5, 2017, Alexander Lyabah <a.ly...@checkio.org >
> wrote:
>
> >A lot of articles that I've read say that I should start with ticket from
> >
t; On Tue, Sep 5, 2017, Alexander Lyabah <a.ly...@checkio.org >
> wrote:
>
> >A lot of articles that I've read say that I should start with ticket from
> >Easy pickings.
>
> >The problem is that there are not that many tickets I can choose from.
> All
> &
> If there were a way to autofocus on first page load only that would be
the best, it might be possible with JS.
Yes, It should be possible by parsing document.referrer in JS.
On Monday, January 9, 2017 at 10:21:15 AM UTC+2, Adam Johnson wrote:
>
> I just found out that's it not new behavior in
Hi guys,
A lot of articles that I've read say that I should start with ticket from
Easy
pickings
https://code.djangoproject.com/query?status=assigned=new=1=Accepted=id=summary=status=owner=type=component=version=changetime=1=id
The problem is that there are not that many tickets I can choose
I'm doing it already through middleware
On Wednesday, November 8, 2017 at 2:28:01 AM UTC+2, Jamesie Pic wrote:
>
> Hello
>
> Have we considered extracting LogEntry from django.contrib.admin in its
> own contrib module ?
>
> It would open doors for new features such as automatic request/response
If it requires any source code changing
On Friday, April 27, 2018 at 9:24:29 AM UTC+3, Kenneth wrote:
>
> Thank you for the reply, Josh.
>
> Should I post it as an issue in the djangoproject.com repository (
> https://github.com/django/djangoproject.com/issues) and not as a ticket
> in the
I can make a version for production use (in a week or two), for your
critics.
For example, based on Appache wsgi.
PS: maybe it is also worth to make a docker image for testing changes in
Django source?
On Wednesday, February 27, 2019 at 4:31:17 PM UTC+2, Jamesie Pic wrote:
>
> > most people
se as an image at all.
>
> On Tuesday, 26 February 2019 07:39:34 UTC, Alexander Lyabah wrote:
>>
>> Hi guys,
>>
>> I found out that official django container is deprecated. Why you don't
>> want to support it?
>>
>> When you search "django" in Pyt
gmail.com
wrote:
> On Thursday, September 10, 2020 at 11:16:56 AM UTC+2 Alexander Lyabah
> wrote:
>
>> The problem with the function is that it is actually working, but not
>> always, and because of that, other people are suggesting it on
>> StackOverflow, using
What the purpose of having function that is not working correctly, when you
may not have this function at all and thing is changed.
I'm talking here about function Query.__str__
Bellow I show you an example:
In [19]: str(TimelineEvent.objects.filter(id__gt=100).query)
Out[19]: 'SELECT
t the other libarries don't - it may
> require calling some internal/undocumented methods. Solving this ticket
> needs some research and work. Your contributions would be welcome.
>
> On Thu, 10 Sep 2020 at 09:15, Alexander Lyabah
> wrote:
>
>>
>> What the purpose of hav
Django in international framework, not US-framework. You should not change
variable names just because meaning of some words have been changed in US
recently. Those words have been used in source-code for years, and nobody
put racism in those word when this framework was founded and nobody
Btw, PR-author has now a privilege to create an article
https://en.wikipedia.org/wiki/Allowlistening
On Sunday, June 21, 2020 at 11:11:02 AM UTC+3, Alexander Lyabah wrote:
>
> I'm not debating, since nobody has something to say. I'm explaining, why
> things that you are doing are emb
xander, it's not really up for debate any more. We've already merged
> the PR's to Django.
>
> On Sat, 20 Jun 2020 at 13:51, Alexander Lyabah > wrote:
>
>> let's not change the subject
>>
>> we are not talking about black and white, we are talking about whitelist
&
Robert, thank you for your response.
For me, as an experience developer, blacklist is more descriptive, since I
saw this word in so many other places, languages, frameworks. But it is
just me, I'm here not to say that my opinion is more important than anyone
else's.
What is more important
Daryl, that is very strange, that you bring it here now.
> One of Django's strengths is that decision making is *not* polluted by
one strong opinion, a whim by a marketing department, or trend-following.
renaming whitelist and blacklist is exactly what is in trend right now. I
understand
rder to argue against changing these names (which has been
> pointed out has already been merged) you would have to come up with an
> argument to show reputational or technical harm would be done by changing.
> Of all the users who have posted on the list who *disagree* with the
> changes
fuse to hear the opinions of
> those who are hurt. That is exclusionary and lacks empathy.
>
> On Monday, June 22, 2020 at 6:20:28 AM UTC-4, Alexander Lyabah wrote:
>>
>> Daryl,
>>
>> I've never called anyone egocentric here, maybe thinking in a very
>> short
e. ‘Allow’ and ‘Deny’ are simply
> semantically clearer than ‘white’ and ‘black’. That alone is a convincing
> argument for me.
>
> On 19 Jun 2020, at 13:55, Alexander Lyabah > wrote:
>
>
>
> Django in international framework, not US-framework. You should not c
> then we should definitely change it.
>
> On Fri, Jun 19, 2020 at 2:54 PM Alexander Lyabah > wrote:
>
>>
>> Django in international framework, not US-framework. You should not
>> change variable names just because meaning of some words have been changed
>
In some of the previous version on Django I had a very useful context
manager.
from contextlib import ContextDecorator
from django.db import connections
class overwrite_default_connection(ContextDecorator):
prev_default = None
write_connection = None
def __init__(self,
a context manager that affects the router's
> state?
> https://docs.djangoproject.com/en/4.0/topics/db/multi-db/#topics-db-multi-db-routing
>
> . That is the API Django supports for moving queries to different databases.
>
> On Wed, Jun 1, 2022 at 2:21 PM Alexander Lya
26 matches
Mail list logo
