Javier Buzzi <mailto:buzzi.jav...@gmail.com>> wrote:
> Hi Bobby, yes, thank you, this looks around the line of what i would like us
> to implement in Django.
>
> Side note: i saw this config('DEBUG', default=False, cast=bool) and thought
> "there is NO WAY t
There’s also python-decouple that I use that I haven’t seen mentioned in this
thread. It lets you set specific environment variables in a separate .env file
or INI file: https://github.com/henriquebastos/python-decouple
-bobby
> On Jun 25, 2020, at 4:47 AM, Javier Buzzi wrote:
>
> Hey Tom, co
I also have my own version of “startproject" that creates several additional
files, including my web server config file (I use H20 web server, not Nginx) as
well as a uWSGI vassals config file. I create the following preconfigured files
and directories using a command-line Python script:
.gitig
In particular, they include settings that shouldn’t be stored in a git repo
such as SECRET_KEY and database passwords. You’ll find these kinds of settings
in git repos all the time.
Really the default django-admin startproject shouldn’t have a single
settings.py that people include in their git
I’ve been testing out some custom Python classes for Django templating, due to
Python 3.6’s addition of F-strings. In addition, templates now have the full
capability to be programmed in Python itself, with the possibility of creating
smart templates and components based on Python classes.
Inst
In any case you’re going to see a lot of Django 2.0 developers on Mac OS hit
this problem when they install to default Python or use standard Python install
convention where Python 3.5 is installed as “python3".
-bobby
> On Apr 10, 2018, at 3:46 PM, Aymeric Augustin
> wrote:
>
>> On 10 Apr 2
#x27;t seem like there is much to fix IMO.
>
>
> On Sun, 8 Apr 2018, 08:19 Bobby Mozumder, <mailto:bmozum...@gmail.com>> wrote:
> Is it OK to reopen that ticket?
>
> The problem is that python2 and python3 need to coexist in most systems, and
> you can’t just rena
<https://www.python.org/dev/peps/pep-0394/>
>
> TL;DR
>
> For now, python should refer to python2 and python3 should be used to refer
> to python 3.
>
> On Saturday, 7 April 2018 07:07:35 UTC+10, Bobby Mozumder wrote:
> The header of manage.py has: #!/usr/bin/env python
The header of manage.py has: #!/usr/bin/env python
Shoudn’t it be: #!/usr/bin/env python3
Since 2.0 is now only Python3. Both my Mac OS & FreeBSD environments have
Python 3.5+ as “python3". (I’m not sure about Linux or other environments).
Is that a bug I need to file?
-bobby
--
You received
h faster version of this flow?
>
> On 4 January 2017 at 22:31, Bobby Mozumder <mailto:bmozum...@gmail.com>> wrote:
>
> > On Jan 4, 2017, at 4:47 PM, Aymeric Augustin
> > > <mailto:aymeric.augus...@polytechnique.org>> wrote:
> >
> > Hello Bob
> On Jan 4, 2017, at 4:47 PM, Aymeric Augustin
> wrote:
>
> Hello Bobby,
>
>> On 4 Jan 2017, at 22:25, Bobby Mozumder wrote:
>>
>> It’s actually called once on app startup during DB connection via a Signal.
>
> Unless I missed something, sin
PM, Adam Johnson wrote:
>
> For that use case I'd suggest just re-executing prepare_db_queries on every
> page view when DEBUG=True. This is similar to how Django's template loaders
> work without the cached loader wrapping them.
>
> On 4 January 2017 at 21:12,
, Tim Graham wrote:
>
> When is prepare_db_queries() called? During a request/response cycle? I
> doesn't look like any caching is happening so I still doesn't see why the
> server needs to restart to pickup changes to the SQL files.
>
> On Wednesday, January 4, 2017
cursor.execute(sql_prepare)
except (OSError, IOError) as e:
pass
except e:
logger.info('Error reading SQL file: %s' % file_name)
raise e
It’s a custom view class that basically
Hi,
Right now, Django only tracks Python module files for autoreload during
development. As a project starts to include more custom include files, such as
Javascript, SQL, Makefiles, etc.., the autoreload function doesn't apply to
these.
For my use case, I have custom view functions that call
> On Aug 16, 2016, at 2:16 AM, Curtis Maloney wrote:
>
> On 16/08/16 09:10, Bobby Mozumder wrote:
>> Hi,
>>
>> I also use generators for my views, and I use Django’s streaming views
>> with my generators to stream responses, so that the web browser rece
t look that it requires any changes to Django core
> itself. So for the community it doesn't need to be within Django core, you
> can already do it for all existing and future versions - which would provide
> nice ground to prove that your solution is good and useful for others as
Hi,
I’ve been using zlib compression on my custom view responses on my site
(https://www.futureclaw.com). I do this before I even cache, and I store the
compressed responses in my Redis cache. This effectively increases my Redis
cache size by about 10x. It also reduces response times from my
Hi,
Here’s an example of minimal Django, where one can output run an full site from
a single file:
https://github.com/rnevius/minimal-django
The author made the comparison to Flask.
I believe the tutorial should start out with this, as the initial Part 0, to
introduce the audience to the fram
> approach.
>
> On Wednesday, November 25, 2015 at 10:20:37 AM UTC-5, Bobby Mozumder wrote:
> I could also use a couple of enhancement to this:
>
> 1) Allow renaming of keys, instead of using the database column names.
> 2) Allow callbacks functions (or lambdas) to conver
I could also use a couple of enhancement to this:
1) Allow renaming of keys, instead of using the database column names.
2) Allow callbacks functions (or lambdas) to convert output values to another
format if needed.
With this, I could send the queries results right to JSON outputs.
-bobby
>
. It also requires the knowledge of which internal
class that the field uses. So, I have a common get/set interface for each
custom field, so I don’t need to know which class that a field uses, as long as
I interface with it properly.
-bobby
>
> ~wolph
>
> On Monday, June 15, 201
Hi all,
Here’s an issue of usability that if fixed could make usage of custom fields
simpler.
Right now fields don’t allow a built-in defaults, and you need to explicitly
set the default parameter for model fields. The problem is that this adds a
ton of boilerplate code.
Using the Polls tuto
> On Jun 2, 2015, at 2:43 AM, Emil Stenström wrote:
>
> On Tuesday, 2 June 2015 05:19:43 UTC+2, Bobby Mozumder wrote:
> At this point it’s probably easiest for Django to provide templates only for
> Javascript front-end, and for Django to only serve API endpoints.
>
>
At this point it’s probably easiest for Django to provide templates only for
Javascript front-end, and for Django to only serve API endpoints.
We really don’t need Django to serve HTML pages anymore, except for the initial
page-load.
I believe this is where the web is headed for the long-term.
For the Documentation, one suggestion I have is that the body font that’s more
different from the source code font.
It looks like you’re using Roboto (a Helvetica clone) for the body text and
Incosolota for the source code. They’re a little too similar. Also, Roboto
isn’t a good font for descr
Looks great. Thanks.
Will this same look apply to the admin backend?
-bobby
> On Dec 16, 2014, at 11:09 AM, Jannis Leidel wrote:
>
> Hi everyone,
>
> We're incredibly proud to share with you the new design of the Django
> website, the documentation and the issue tracker.
>
> This is a lon
In the file subclassing.py, should the following:
def make_contrib(superclass, func=None):
"""
Returns a suitable contribute_to_class() method for the Field subclass.
If 'func' is passed in, it is the existing contribute_to_class() method on
the subclass and it is called before a
It seems that the MVC Javascript systems like Angular and Ember are winning the
front-end. They're very responsive compared to being served files from the
back-end - no need to wait for server responses, since there's a local cache
subset of the database in the browser.
It would probably be us
29 matches
Mail list logo
