Thanks so much, Tim. I really appreciate it.
On Saturday, January 7, 2017 at 2:05:53 PM UTC-7, Tim Graham wrote:
>
> django-formtools 2.0 is now available on PyPI.
>
> On Thursday, January 5, 2017 at 5:29:43 AM UTC-5, Romain Garrigues wrote:
>>
>> Hi guys,
>>
>> I'm currently investing some
+1 on type hinting. PyCharm always gives me 20+ options when I want to jump
to the definition of modelInstance.save() method (or any other method with
a common name like save), which makes me really miss static type
languages... As the framework for perfectionists with deadlines, I think
type
I just found out that's it not new behavior in Django 1.9. The javascript
autofocus that existed previously has the same effect. This doesn't change
my request though, I'd still like the autofocus to be either removed or
optional.
Op vrijdag 6 januari 2017 18:54:54 UTC+1 schreef Adam Johnson:
Hi Josh,
On Sunday, January 8, 2017 at 11:38:52 AM UTC+1, Josh Smeaton wrote:
>
> I guess I don't really see how we'd be helping users in any meaningful way
> by supporting python 3.4 with Django 2.0. Django 2.0's defining change is
> dropping Python 2. We have no idea what else will land in
Hi,
On Sunday, January 8, 2017 at 8:43:46 AM UTC+1, roboslone wrote:
>
> As Django user, I have to say type hinting would help a lot to understand
> how things work in Django without looking at docs. It could save a lot of
> time for beginners, too.
>
I've been working with "type hinting" in
Hi Josh,
How about keeping 3.5 support in 2.0.0? say the users of ubuntu 16.04 using
systems python3.5 and update to 2.0 or started a new project with dj2.0.0
in ubuntu 16.04.
About pyenv, it take care of installing and using different versions of
python in a system without hampering the
Apparently I'm dumb and didn't read enough. pyenv *does* take care of
installation too. I'm not familiar enough with it (obviously..) to know
whether or not we should be encouraging its use.
On Sunday, 8 January 2017 22:33:44 UTC+11, Josh Smeaton wrote:
>
> I don't think pyenv is really
I don't think pyenv is really relevant to this discussion and not something
we really need to promote. pyenv deals with making a particular installed
python *available*, it doesn't handle the installation of that python.
On Sunday, 8 January 2017 22:30:44 UTC+11, Asif Saifuddin wrote:
>
> Hi
Hi Josh,
I do agree and support your idea's. How about pointing/recommend pyenv for
deployment in the doc?
Thanks,
Asif
On Sunday, January 8, 2017 at 4:38:52 PM UTC+6, Josh Smeaton wrote:
>
> I guess I don't really see how we'd be helping users in any meaningful way
> by supporting python 3.4
I guess I don't really see how we'd be helping users in any meaningful way
by supporting python 3.4 with Django 2.0. Django 2.0's defining change is
dropping Python 2. We have no idea what else will land in 2.0.
If we're trying to consider Enterprise users on "older" Distros:
- 1.11 will be
10 matches
Mail list logo
