Sorry to have missed meeting you at DjangoCon, Meet, but I'll add my
findings here to the record.
By way of background, I work at The Wharton School, where we're a
Python/Django (on RHEL) and SQL Server shop. I was responsible for
implementing a working configuration for Django, starting with
Thanks for all of your efforts, Aymeric, I've been following your project
since its inception - I'm FlipperPA on GitHub.
On Sunday, September 13, 2015 at 4:59:34 AM UTC-4, Aymeric Augustin wrote:
> Did you mean “pyodbc outperforms pymssql”? Or did you go with pyodbc
> despite lower
, 2015 at 11:27:59 AM UTC-4, Tim Allen wrote:
> Thanks for all of your efforts, Aymeric, I've been following your project
> since its inception - I'm FlipperPA on GitHub.
> On Sunday, September 13, 2015 at 4:59:34 AM UTC-4, Aymeric Augustin wrote:
>> Did you mean
Thanks Tim, this is a promising update. While my department is slowly
migrating to PostgreSQL, most of the other departments are still very much
reliant on SQL Server. Since we're a Python/Django shop for our web stack,
better support would be very welcome. Most of our developers are on Macs,
Since Django 1.9 will support Python 3.5, I was wondering if there are any
plans to support Python 3.5 in Django 1.8, since it is an LTR.
I did a cursory search and didn't find anything stating yay or nay. I'm
going to assume 1.8 only support 3.4 for now, as I've had issues with
Since we're on the topic, it'd be great if `inspectdb` also accepted a
`--tables` option, to only move certain tables in the database. For example:
./manage.py inspectdb --tables=form_*,user_*
...to import any tables starting with 'form_' or 'user_'. Allow with the
`--database` option, this
HI Doug, I can relate to what you are saying, I had a similar experience
when trying to find a reference for the generic FormView. Issuing a P.R. to
improve it is on my BLOTTD (big list of things to do). I was interviewing a
candidate last week who knows I'm a big fan of Django, and wanted to
Tim: that's definitely a big help, but still a click away. I'm just
brainstorming here, please bear with me!
I think part of my confusion as a newbie is from the front page itself,
Now that I understand the concepts behind the documentation better (thanks
Scot, you've summarized what I've run into as well beautifully. My problem
has never been with the documentation once I find it - it has been the path
to finding it. Another frustration is trying to find a part of the
documentation I know I've seen before a second time. I seem to go round and
>>>>- *We are finalizing the detailed schedule this week and will post
>>>>it on this thread by next Friday. *
>>>> 3. If myself or the other attendees should do anything to prepare for
On Thursday, January 28, 2016 at 1:09:41 PM UTC-5, Cristiano Coelho wrote:
> Tim Allen,
> What you said about compiling the C dependencies on a similar machine and
> then upload it all together indeed works (it was one of the options) but
> caused some ot
[slightly off-topic] I'm wondering if this will extend to SQL Server
Management Studio. While I'm mainly a command line basher, many of
coworkers are married to the GUI. I've found SSMS blows the competition out
of the water when it comes to DB management GUIs. I'm wondering if this
>>>>- Improve getting started experience [decrease difficulty]: Getting
>>>>MSSQL for development (free and easy/fast set up) is hard today;this is
>>>>MSFT to improve this experience.
Just a reminder the today is the last day to register for DjangoCon at
Early Bird rates. Tomorrow, prices will increase by $50 per ticket. To
register, click here:
Prices are affordable for the 5 days, starting at $195 for our diversity
rate. The speakers
How would you prefer suggested tweaks to your proposal? Since it is on
GitHub, would you prefer pull requests? Thank you for taking the initiative!
On Sunday, June 5, 2016 at 10:52:57 PM UTC-4, Connor Boyle wrote:
> I'd like to make a proposal for the addition of a
+0 to extending the length, but the 255-character maximum in MySQL
shouldn't be a concern since MySQL 5.0.3 (IIRC). I'm all for the ease of a
length increase to the concern raised in the original post. While it would
be nice to do more in the long term, that's a bigger discussion, as Aymeric
Our main database in my division contains about 150,000 users total - from
across the world. Although the distribution is heavily weighted towards
North America and Europe, we do have a fair amount of Asian schools, and
one from Brazil. Many of these schools also have international students. I
Hi Etienne, like Tim G. said, you'll probably have better luck with the
django-users mailing list. This group is for development discussion of core
You may also want to reconsider using Schevo; I remember hearing about it
long ago, but it doesn't appear that is has been actively
I'd be happy to contribute configuration for connecting Django to SQL
Server. I've had to deploy this for some projects at work that don't (yet)
use PostgreSQL. This sounds like a fantastic tool for testing, as well as
examples for people just getting started; wiring up a database for the
This makes sense, and the DEP looks great. Just a few thoughts:
- Django has always had dependencies, just external to PyPI. Python itself
is the obvious one. While not absolutely required for Django, a database
driver stack is another (psycopg2, mysql-connector, pyodbc, etc). Perhaps
Switching to another font is certainly an option. Is the issue with Google
Fonts the Apache license versus the Django BSD license?
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this
I've had the privilege of introducing Django to many people over the past
several years. A recurring theme I have noticed is that once a new Django
developer reaches the "It Worked!" page, the inevitable next question is,
It struck me that this page is valuable real estate for the
y don't need to be
> hand-updated with every version.
> I think the unused css should be removed. We're not
> using button,input,optgroup,select,textarea, etc.
> On Tue, Apr 18, 2017 at 12:03 PM, Tim Allen <fli...@peregrinesalon.com
> > wrote:
>> Switching t
, I noticed a couple layout glitches in the current
> proposal, but nothing major:
> - can overlap and at small heights e.g. with
> developer tools open at the bottom
> - links look bad at 320px wide — try the "iPhone 5" setting in Chrome's
> responsive view
I've recently been introduced to `django-environ`, a similar library that
has additional features to DB connect URLs that we may want to consider:
It has the same issue with third party DB engines; for example, I recently
issued a PR to include `pyodbc`
I would love to see partial indexes supported. Great work! As far as
databases with Django support:
- PostgreSQL supports partial indexes
- SQLite supports partial indexes
- SQL Server supports them, called "filtered indexes"
- Oracle: Sort of supports
If we need some dogfooding with real-world candidates, I'd be happy to
provide some. We have a project which currently takes ~20 minutes to start
up (automated data models created by introspecting a database) that might
be a good edge-case candidate.
You received this message because you
AFAIK, the *supports_microsecond_precision* feature is still needed by
*django-pyodbc-azure*, because of SQL Server's, ahem, creative datetime
> feature around if it's helpful for that backend, but we'll need
> contributions from django-pyodbc-azure maintainers to keep it updated
> (mainly with respect to using the feature to skip or change behavior in
> On Sunday, August 2
>From there, you're one click away from the tickets. Here's a link to the
"Easy Pickings" currently open:
You received this message because you are subscribed to the Google Groups
This would certainly make a good package, but I'm not sure it belongs in
core Django, as it would likely introduce dependencies for everyone.
I've done something similar for the Wagtail CMS on Django using the PrismJS
library: https://github.com/FlipperPA/wagtailcodeblock A similar package
Hi Kunal, welcome to the Django community! django-pyodbc-azure is the best
maintained SQL Server engine I've found, and it typically gets updated a
little more quickly than this. However, Michaya who maintains the package
has been extremely busy lately, and said it will take him a few more
Since `django-admin startproject my_project` is created on the fly from
templates, couldn't we dynamically create the `manage.py` executable based
on some system introspection and an agreed upon priority?
On Tuesday, April 10, 2018 at 4:28:12 AM UTC-4, Adam Johnson wrote:
Over the past few releases, several CharFields in django.contrib.auth have
been increased to a max_length of 191: username, first_name, and last_name
come to mind.
I've issued a PR
I've amended the PR to be 150 characters rather than 191.
Thanks for doing the digging which explains why I had 191 characters stuck
in my head. I'm in the "as long as possible to cover the most possible
cases" camp, but 150 would seem to hit the 99.9%, so let's call it a
On Friday, December 21, 2018 at 10:18:04 AM UTC-5, Cristiano Coelho wrote:
> Let's not forget how the various *count *calls starts to kill your
> database when you get over 1 million rows (postgres at least).
> So far the only options I have found with postgres are:
> - Estimate count for non
I'm in the camp of having a flexible policy that allows us to have
discussions that examine the current state of the Django and Python
ecosystems. This allows us to make informed decisions.
As several folks have mentioned before, 3.6 was a more momentous release
than most versions of Python.
Another plus one for Black, without getting too into the weeds. I think the
time is will save likely outweigh the valid concerns posted here. I've used
Black extensively on several projects, and much like f-strings, the last
Pink Floyd album, and broccoli, have found I really like something I
Mail list logo