On Sep 1, 2017 3:00 PM, "Derek" wrote:
Thanks Melvyn
I already have tests for the processing of data when it has been uploaded -
which is actually the critical issue for the application. The "view" is
just really a thin wrapper around the two steps : form display & upload and
then the file proc
I have been looking for a decent guide that covers testing in a solid,
thorough way - there are lots of fragmented pieces that cover
bits-and-pieces of what is needed for tests but not all the cases with a
start-to-end comprehensive approach for everything ("Obey the Testing Goat"
comes closest). I
It certainly isn't trivial.
First and foremost, write fat models and Managers, but lean views.
Rather then putting complex queries in views, I have a strong bias
to writing manager methods (or QuerySet methods, if I feel it's
reusable in more then one Manager - see Manager.from_queryset [1]).
Fu
It is a project I developed in ubuntu and currently running on a ubuntu
server. I just bought a new mac mini, so I would like to develop on mac.
I have isolated the problem to the django version.
When I use django==1.10.7, this does not happen.
When I use django==1.11a1 this happens.
This is
I use Python3.5.2 Django1.9
I use `python -m venv venv/weather_station` to create virtual evnironment
(/home/user/venv)
This is my project tree in Ubuntu /home/user/myproject:
(`export project=/home/user/myproject`)
myproject
|
├── gunicorn.conf.py
├── static
│ ├── admin
└─
Try:
gunicorn --bind ip:port wsgi:application
Make sure you run it from the directory where manage.py is located.
Regards,
M
On Sun, Sep 3, 2017 at 9:04 AM, Jonathan Cheng
wrote:
> I use Python3.5.2 Django1.9
>
> I use `python -m venv venv/weather_station` to create virtual evnironment
> (/hom
File
"/Users/coderek/Documents/projects/py3.5/lib/python3.5/site-packages/django/contrib/staticfiles/storage.py",
line 21, in
from django.utils.six.moves import range
ImportError: cannot import name 'range'
Are you sure you're using 3.6.2? Do you have another virtualenv with 3.5
and no Dj
it's the same in either versions of python. the output was captured when i
was just debugging it in 3.5.
On Sun, Sep 3, 2017 at 2:55 PM, James Schneider
wrote:
>
>
> File
> "/Users/coderek/Documents/projects/py3.5/lib/python3.5/site-packages/django/contrib/staticfiles/storage.py",
> line 21,
On 1 September 2017 at 16:13, Melvyn Sopacua wrote:
> A few tips on your code:
>
> def get_latest_chemo(self):
> chemo = ChemoRegime.objects.filter(pat
> ient=self).latest('stop_date')
>
> class ChemoRegime(models.Model):
> patient = models.ForeignKey(Patient, on_delete=mo
Hi,
I have current django application with django 1.11 and python 2.7.
Python 2.7 has support till 2020-01-01 and 3.5 has support till 2020-09-13.
I've been asked to upgrade to Python 3.5. My question is why is there a
need to upgrade from 2.7 to 3.5 as EOL support for both of them is nearly
th
Could you turn off DEBUG and check what the problem is then?
The reason is that I want to make sure we're not judging the side
effect of *rendering* the exception.
On Sun, Sep 3, 2017 at 11:52 PM, Derek Zeng wrote:
> it's the same in either versions of python. the output was captured when i
> was
Hi,
the reason is that Python 3.6 is backwards-compatible with 3.5. Same thing with
3.7 and 3.8 and generally 3.x for x>=6. In contrast, Python 3.0 is
backwards-incompatible with 2.7. So if you upgrade to 3.5 now, your program will
also run in any Python 3 version later than 3.5. The big thing is
Bijal,
Django 2.x - the next release cycle - will be Python 3.x
Most major OSes will be moving to Python 3.x in their next release (eg in
RedHat/CentOS 7.4 (I think))...
If it's no big deal - and it really shouldn't be - you should move to
Python 3.x
Cheers
L.
--
"The antidote to apocaly
On Sun, Sep 3, 2017 at 4:26 PM, Derek Zeng wrote:
>
> When I use django==1.10.7, this does not happen.
> When I use django==1.11a1 this happens.
>
Why 1.11a1? Current is 1.11.4
--
| Raffaele Salmaso
| https://salmaso.org
| https://bitbucket.org/rsalmaso
| https://github.com/rsalmaso
--
You rec
At this point it makes more sense to upgrade to 3.6, but that
aside, next Django release (2.0) will drop support for Python
2.
Dealing with 2 major version upgrades is not the best platform
for a smooth ride.
On Mon, Sep 4, 2017 at 8:04 AM, BIJAL MANIAR wrote:
>
> Hi,
>
> I have current django
Your Django project really is "weather_station", but you treat
"myproject" as the
project.
Revisit:
https://docs.djangoproject.com/en/1.11/intro/tutorial01/#creating-a-project
And follow instructions to the tee and look at the directory structure.
On Sun, Sep 3, 2017 at 6:04 PM, Jonathan Cheng
16 matches
Mail list logo
