Re: Internet Explorer question

[Andréas Kühne]

Hi,

If you target corporate users, you will have to test IE. I would say that
that is a requirement. The draggable corner of a TextField is a browser
implementation for example and doesn't exist in IE (as you now have
experienced). However the javascript problems you are seeing should "just
work", because django admin uses jquery and that works with all major
browsers (as long as you are not using a very old version of IE).


Regardsr,

Andréas

2017-06-16 6:06 GMT+02:00 Mike Dewhirst :

> I have just spent the most frustrating 90 minutes in living memory walking
> a potential user through our application via IE.
>
> Does anyone know if we need to make special provision for IE in Django
> Admin (1.10) ?
>
> The UI seems very slow and quirky. I suspected Javascript was disabled but
> the Show/Hide links worked sometimes. The user is familiar with IE
> (corporate desktop) and had to click (SHOW) three times to expand the
> collapsed fields. The draggable corner of a TextField was non-existent.
> Drop-down lists were sometimes mysteriously blank but could be traversed
> with the up/down arrow keys.
>
> I haven't had IE on any of my machines for decades. Am I going to have to
> test on IE?
>
> Ideas?
>
> Thanks
>
> Mike
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/django-users/3401c396-596b-a021-fc29-eb1250980d7c%40dewhirst.com.au.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCfwSDW9jRLptDhnNBTt82oUc%2BiAJwpiBdYcfH0%3DPXg4TA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed building wheels for twisted

[yingi keme]

I really dont know how to post it.

> Okk,
> 
> So what i had to do is, download the Twisted .whl file from this link:
> 
> http://www.lfd.uci.edu/~gohlke/pythonlibs/#twisted
> 
> You have to choose which is compatible with your python version. Mine is 
> python 3.5 and win32. So make sure you choose the correct .whl file
> Then you can install the .whl file you just downloaded in your virtual 
> environment. 
> 
> ..\MyVenv> pip install 
> C:\Users\Documents\Twisted-17.5.0-cp35-cp35-cp35m-win32.whl
> 
> After installing Twisted, then you can now go on ahead and install channels 
> in your virtual environment
> 
> ..\MyVenv> pip install channels.
> 
> Thats all.



> On 15 Jun 2017, at 11:07 AM, Oladipupo Elegbede 
>  wrote:
> 
> Do you want to share what you did to resolve it?
> 
> That may help someone else.
> 
> Thanks.
> 
> On Jun 14, 2017 5:07 PM, "yingi keme"  wrote:
> I have solved the problem. Thanks anyways..!
> 
> Yingi Kem
> 
> > On 14 Jun 2017, at 6:43 PM, yingi keme  wrote:
> >
> > Hello
> >
> > I tried installing django channels on my virtual environment. But it has 
> > failed. And it gives the following error 'failed building wheel for 
> > twisted'.
> >
> > What is this about.? And how can i handle this issue?
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Django users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to django-users+unsubscr...@googlegroups.com.
> > To post to this group, send email to django-users@googlegroups.com.
> > Visit this group at https://groups.google.com/group/django-users.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/django-users/95e49887-8f39-4a53-8e8c-73b216a4c43a%40googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/1C2C6D76-E535-461B-853E-36623A7942CB%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CAHjgLX4dki5woio85Fh5GTiicMFZEcoKxFDAByVAAPm7wtcYrw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/A01E5BB2-EEB7-4598-8223-384561AAE567%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Images are not displaying

[Santosh Yelamarthi]

Hi,

am using django 1.10 version. am unable to display images in web.

my app name -- polls

I created templates directory and i put my *home.html* over there 
**
**
**
**
**
**

I created static folder and i put my image *logo.jpg* over there

In my views file I imported home.html :

*from django.shortcuts import render_to_response*
*from django.http import HttpResponse*

*# Create your views here.*
*def index(request):*
*return render_to_response('home.html')*

settings.py :

*STATIC_URL = '/static/'*

I am able to display text but not images.


Can any one please help me in this.

Thanks in advance

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e3703e83-01d4-4412-9227-c82147262571%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I did the tutorial successfully but couldn't find similar examples for small project (for better understanding of Django programming)

[softie . coder]

Hi!

I'm doing OOP now for some years (C++/C#, no Python) but never had much 
contact with database stuff. I did the tutorial in a virtualenv ((nearly?) 
current Python 3.6 for Windows and Django 1.11). Now, for better 
understanding of Django, I'd like to program a small website (just for 
internal use). I assume Django is suited for it :-)
The bad thing is that I couldn't find any similar examples (and also when I 
tryed to edit the tutorial program in that way, I didn't came far). 
Probably I just don't know the right keywords.

I'd like to do something like this:
An internal tool, let me call it "Internal car configurator". So every 
user(!) is allowed to do everything mentioned below.
- There're car model A, B and C (which needs to be extendable and deletable 
like by a "+"/"-" buttons on the website - renaming would be a plus). 
- There's a table where every model has it's own row. Every model is shown 
there once.
- In that table, there're columns like "exterior package" and "interior 
package" (dropdown box to select the corresponding package). The columns 
need to be extendable and deletable like by a "+"/"-" buttons on the 
website - renaming would be a plus.
- For each like exterior and interior package, there's a number of elements 
which may only exist once per like "exterior" and "interior". Like for 
exterior "more_chrome", "bigger_wheels", ... and for interior "more_chrome" 
(that's completely independent of exterior "more_chrome"!), 
"leather_seats", "6th_and_7th_seat", ... (which needs to be extendable and 
deletable like by a "+"/"-" buttons on the website - renaming would be a 
plus). 
- Packages have to be defined for each like "exterior" and "interior" (the 
number of and the contents in the packages need to be extendable and 
deletable like by a "+"/"-" buttons on the website - renaming would be a 
plus). 
- Only the packages are selectable in the table (with rows for each model) 
metioned above. For each column, exactly one package must be selected 
(which can contain no elements and can be called like "nothing").
- Exterior packages can only contain exterior elements. E.g.: The exterior 
package "nothing" doesn't contain any of the (of courser only exterior) 
elements. The exterior package "chrome" only contains "more_chrome". The 
exterior package "extend" only contains "more_chrome" and "bigger wheels". 
The packages "everything" contains everything (of the exterior elements). 
Same for interior etc.
- If the contents of package is changed (element added, deleted, 
renamed...), this change applies immediately to all models where that 
package is selected.
- "everything" mustn't automatically contain new elements. New elements 
have to be manually added to "everything".
- Deleting a package mustn't delete elements. It's ok if there're elements 
which currently aren't part of any package.

Later this will be extended like by (but for that I think I'll find 
something on my own):
- All elements, all packages with their elements and all car models with 
the elements selected via selecting packages will be exported to text files 
in a certains format to be stored in a Git repository (so that database 
contents (but not the basic database structure)) can be restored from that 
text files, see below and that text files can be processed by other 
software).
- Delete current database contents and import that text files from the Git 
repository (=vice versa to the line above - only works if the basic 
database structure wasn't change since when creating that text files).
- LDAP login (also because of Git)

So if you have links or keywords to similar examples (which work with 
Django 1.11 very well) or could even write some example code here -> thank 
you! :-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/85e9b8a9-526d-4b34-9127-a65fb3b6a617%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: User has no dcf_profile : RelatedObjectDoesNotExist

['Abraham Varricatt' via Django users]

On Friday, June 16, 2017 at 7:06:33 AM UTC-4, Nabil BOUDERBALA wrote:
>
> After extending an existing user model, I get RelatedObjectDoesNotExist 
> exception with a value User has no dcf_profile. I seems that dcf_profile 
> isn't created automatically for each user.
>

It took me awhile to figure out that dcf_profile is the text you use as 
related_name for the User model. 


 

> Please take a look at my model, view and form below and tell me how can I 
> correct my views file?
>
My views.py :
>
> @method_decorator(login_required)def dispatch(self, *args, **kwargs):
> if not self.request.user.dcf_profile.allow_add_item():
>
>
It looks like this is where you are having trouble. The code is trying to 
call the dcf_profile attribute/method from the user object - which doesn't 
exist. 

Your end goal appears to be to call the all_add_item() function. Why not 
grab an instance of your CustomUser first and invoke it on that? Something 
like,

def dispatch(self, *args, **kwargs):
user = self.request.user
my_user = CustomUser.objects.get(auth_user_ptr=user)  # Assuming you 
have entry in your database
if not my_user.allow_add_item():


Yours,
Abraham V.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/022133ae-25f4-4bc4-82ce-aee7726932b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Images are not displaying

['Abraham Varricatt' via Django users]

If this is a production deployment, you probably need to run collectstatic 
and test if static files are being served correctly - more a deployment 
issue than a django matter. 

But, if you are testing with 'runserver' on a development system ... 
without exact knowledge of your folder structure, it's going to be 
difficult to help you - since this appears to be a pathing issue. 

However,

On Friday, June 16, 2017 at 7:06:17 AM UTC-4, Santosh Yelamarthi wrote:
>
>
> I created templates directory and i put my *home.html* over there 
> **
> **
> **
> **
> **
> **
>
> I created static folder and i put my image *logo.jpg* over there
>

If this is all you did, then shouldn't the src path be "static/logo.jpg" ?

Yours,
Abraham V.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/db89c6a7-9a68-4a5e-afb2-072316102bc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

DSasS(Data Science as Service)

[Arshpreet Singh]

There is a project I am working on which is Platform. Data Science as 
Service. A Platform where almost anyone can do Data Science with Few Clicks.
 


SearchBusinessAnalytics spoke with DataScience CEO and founder Ian Swanson 
about the burgeoning data science as a service space. He discussed what his 
team of data scientists provides that data analysis tools alone cannot, the 
ways in which data science drives revenue, and how his venture-backed 
company has been able to acquire and develop a strong stable of data 
scientists and data engineers in less than two years while massive tech 
companies often struggle to do the same. 



http://searchbusinessanalytics.techtarget.com/feature/Data-science-as-a-service-provides-instant-access-to-analysts

So basically there will be few ML models and I will feed those some 
variables and will get some output. Before writing any kind of code I am 
interested in the architecture of the whole system. Django is the option to 
use and do things.

I am bit confused and not sure where I should start to do things? 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b3fad60b-fe5e-4a7f-9e43-a4aa599e47cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Images are not displaying

[Carl]

Hi!

Because static is a folder on the root of your website, try putting
a slash in front of static; for example,



Hope this helps. :-)

Sincerely,
Carl

 Original Message 
Subject: Images are not displaying
Local Time: June 16, 2017 1:44 AM
UTC Time: June 16, 2017 5:44 AM
From: santosh.yelamar...@gmail.com
To: Django users 

Hi,

am using django 1.10 version. am unable to display images in web.

my app name -- polls

I created templates directory and i put my home.html over there








I created static folder and i put my image logo.jpg over there

In my views file I imported home.html :

from django.shortcuts import render_to_response
from django.http import HttpResponse

# Create your views here.
def index(request):
return render_to_response('home.html')

settings.py :

STATIC_URL = '/static/'

I am able to display text but not images.

Can any one please help me in this.

Thanks in advance

--
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
[https://groups.google.com/d/msgid/django-users/e3703e83-01d4-4412-9227-c82147262571%40googlegroups.com](https://groups.google.com/d/msgid/django-users/e3703e83-01d4-4412-9227-c82147262571%40googlegroups.com?utm_medium=email&utm_source=footer).
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/169zHcqyX29FYNm7sLfBk3FbH72r5PDtmPM9uY0M_-cow9udRGutLTgzU9QZ0BgkCiJTkiI6l5oAGMCjH9N3pVpJl8bTvNyW6y5qvt5Wq8Y%3D%40nexuspro.ca.
For more options, visit https://groups.google.com/d/optout.

Re: Images are not displaying

[Antonis Christofides]

Hello,

> **
This is probably missing a slash before "static"; it should be like this:



But a better way is this:

{% load static %}

...



If you are on production rather than development, see also this:
https://djangodeployment.com/2016/11/21/how-django-static-files-work-in-production/

Regards,

Antonis

Antonis Christofides
http://djangodeployment.com


On 2017-06-16 08:44, Santosh Yelamarthi wrote:
> Hi,
>
> am using django 1.10 version. am unable to display images in web.
>
> my app name -- polls
>
> I created templates directory and i put my *home.html* over there 
> **
> **
> **
> **
> **
> **
>
> I created static folder and i put my image *logo.jpg* over there
>
> In my views file I imported home.html :
>
> *from django.shortcuts import render_to_response*
> *from django.http import HttpResponse*
> *
> *
> *# Create your views here.*
> *def index(request):*
> *return render_to_response('home.html')*
>
> settings.py :
>
> *STATIC_URL = '/static/'*
>
> I am able to display text but not images.
>
>
> Can any one please help me in this.
>
> Thanks in advance
> -- 
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com
> .
> To post to this group, send email to django-users@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/e3703e83-01d4-4412-9227-c82147262571%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4e8335af-c1fc-6883-dc28-96ec6181690c%40djangodeployment.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error even after following the django documentation

[danbmathew]

Thanks for the reply.Well i used the same model shown in the 
documentation.I even cross checked all my codes to verify that anything is 
out of place.Even then the error appears.


On Thursday, June 15, 2017 at 11:12:55 PM UTC+5:30, Hemhem wrote:
>
> TypeError: 'choice_text' is an invalid keyword argument for this function
> That above, is where the problem is where the problem is so I am going to 
> guess you need to check your model if you wrote everything correctly.
> If I can see what your model looks like, I can probe in.
>
> On Thu, Jun 15, 2017 at 10:34 AM, danbmathew  > wrote:
>
>> Well I'm new to django and my code is just as in the documentation.But 
>> got an error while trying to run the codeline q.choice_set.create(
>> choice_text='Not much', votes=0).
>> This part of the code is almost at the end of the segment named Playing 
>> With API.I will also post the error.
>>
>> Traceback (most recent call last):
>>   File "", line 1, in 
>>   File 
>> "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib\site-packages\django\db\models\fields\related_descriptors.py",
>>  
>> line 653, in create
>> return super(RelatedManager, self.db_manager(db)).create(**kwargs)
>>   File 
>> "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib\site-packages\django\db\models\manager.py",
>>  
>> line 85, in manager_method
>> return getattr(self.get_queryset(), name)(*args, **kwargs)
>>   File 
>> "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib\site-packages\django\db\models\query.py",
>>  
>> line 392, in create
>> obj = self.model(**kwargs)
>>   File 
>> "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib\site-packages\django\db\models\base.py",
>>  
>> line 571, in __init__
>> raise TypeError("'%s' is an invalid keyword argument for this 
>> function" % list(kwargs)[0])
>> TypeError: 'choice_text' is an invalid keyword argument for this function
>>
>>
>> Please help me.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/f53b5d7f-baa4-4fa6-91de-e75e4fb97af5%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Elegbede Muhammed Oladipupo
>
> web: www.dipoelegbede.com
> skype: dipo.elegbede
> mobile: (917) 860 1542
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5bd8118a-a3e6-4590-91d7-ae4daedc9fde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error even after following the django documentation

[Andréas Kühne]

Hi,

Could you please include your models.py file? So that we can see the model
declarations.

Regards,

Andréas

2017-06-16 14:07 GMT+02:00 danbmathew :

> Thanks for the reply.Well i used the same model shown in the
> documentation.I even cross checked all my codes to verify that anything is
> out of place.Even then the error appears.
>
>
> On Thursday, June 15, 2017 at 11:12:55 PM UTC+5:30, Hemhem wrote:
>>
>> TypeError: 'choice_text' is an invalid keyword argument for this function
>> That above, is where the problem is where the problem is so I am going to
>> guess you need to check your model if you wrote everything correctly.
>> If I can see what your model looks like, I can probe in.
>>
>> On Thu, Jun 15, 2017 at 10:34 AM, danbmathew  wrote:
>>
>>> Well I'm new to django and my code is just as in the documentation.But
>>> got an error while trying to run the codeline q.choice_set.create(c
>>> hoice_text='Not much', votes=0).
>>> This part of the code is almost at the end of the segment named Playing
>>> With API.I will also post the error.
>>>
>>> Traceback (most recent call last):
>>>   File "", line 1, in 
>>>   File "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib
>>> \site-packages\django\db\models\fields\related_descriptors.py", line
>>> 653, in create
>>> return super(RelatedManager, self.db_manager(db)).create(**kwargs)
>>>   File "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib
>>> \site-packages\django\db\models\manager.py", line 85, in manager_method
>>> return getattr(self.get_queryset(), name)(*args, **kwargs)
>>>   File "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib
>>> \site-packages\django\db\models\query.py", line 392, in create
>>> obj = self.model(**kwargs)
>>>   File "C:\Users\DELL\AppData\Local\Programs\Python\Python36-32\lib
>>> \site-packages\django\db\models\base.py", line 571, in __init__
>>> raise TypeError("'%s' is an invalid keyword argument for this
>>> function" % list(kwargs)[0])
>>> TypeError: 'choice_text' is an invalid keyword argument for this function
>>>
>>>
>>> Please help me.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-users...@googlegroups.com.
>>> To post to this group, send email to django...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/django-users.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/django-users/f53b5d7f-baa4-4fa6-91de-e75e4fb97af5%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Elegbede Muhammed Oladipupo
>>
>> web: www.dipoelegbede.com
>> skype: dipo.elegbede
>> mobile: (917) 860 1542 <(917)%20860-1542>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/5bd8118a-a3e6-4590-91d7-ae4daedc9fde%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCf1-Ls5TFU3B77L6%2BuOybnSaZuFBANS9DuaR%2BkN%3Dxv7Wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: how to combine views in one template

[Matthew Pava]

Hi Mark,
You would pass the form in the context of the template in the view.  You can 
pass pretty much anything to a template through the context.

def builddetails(request, id):
build = Build.objects.get(pk=id)
form = BuildForm(request.POST or None)
if form.is_valid():
   form.save()
return render(request, 'app/builddetails.html', { 'build': build, ‘form’: 
form })



From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of Mark Alan Jones
Sent: Thursday, June 15, 2017 6:04 PM
To: Django users
Subject: how to combine views in one template

Hello Django Community,

I am new to Django and tackling my first app outside of the tutorial. The app 
I'm working on is a simple ticket system for build requests at my IT Company. I 
only have one model 'Build', and I have checkboxes that denote how far the 
build has been done.

I have a page that shows all build requests, and then a separate page with the 
details of each build request. I want to add a form to this builddetails 
template, but I'm not sure what is the correct way to do this when the template 
is already pulling info from the model. Every tutorial I've followed has shown 
using a form under a separate URL, but that is not viable.

my current view for builddetails is this:

def builddetails(request, id):
build = Build.objects.get(pk=id);
return render(request, 'app/builddetails.html', { 'build': build });

How do I combine this with a ModelForm on the same page?

the ModelForm I was trying to use looks like this:

class BuildForm(forms.ModelForm):
class Meta:
model = Build,
fields = ['notes', 'build_engineer', 'latest_bios','bios_settings', 
'hot_keys_tested', 'office_activated']

If I need to provide any more information please let me know, and thank you so 
much in advance for any help you can offer.

--
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
django-users+unsubscr...@googlegroups.com.
To post to this group, send email to 
django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/733168e2-2559-4726-9067-dc2a23397bb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/977caa598f214043895a133c5de24f49%40ISS1.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.

RE: Internet Explorer question

[Matthew Pava]

The only Microsoft-supported version of IE is version 11.  And it seems to work 
just fine for me in Django Admin 1.10.  If you users aren’t using version 11, I 
would start there.  Then check the computer; maybe the user needs to delete 
some temporary files.

From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of Andréas Kühne
Sent: Friday, June 16, 2017 2:52 AM
To: django-users@googlegroups.com
Subject: Re: Internet Explorer question

Hi,

If you target corporate users, you will have to test IE. I would say that that 
is a requirement. The draggable corner of a TextField is a browser 
implementation for example and doesn't exist in IE (as you now have 
experienced). However the javascript problems you are seeing should "just 
work", because django admin uses jquery and that works with all major browsers 
(as long as you are not using a very old version of IE).


Regardsr,

Andréas

2017-06-16 6:06 GMT+02:00 Mike Dewhirst 
mailto:mi...@dewhirst.com.au>>:
I have just spent the most frustrating 90 minutes in living memory walking a 
potential user through our application via IE.

Does anyone know if we need to make special provision for IE in Django Admin 
(1.10) ?

The UI seems very slow and quirky. I suspected Javascript was disabled but the 
Show/Hide links worked sometimes. The user is familiar with IE (corporate 
desktop) and had to click (SHOW) three times to expand the collapsed fields. 
The draggable corner of a TextField was non-existent. Drop-down lists were 
sometimes mysteriously blank but could be traversed with the up/down arrow keys.

I haven't had IE on any of my machines for decades. Am I going to have to test 
on IE?

Ideas?

Thanks

Mike

--
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
django-users+unsubscr...@googlegroups.com.
To post to this group, send email to 
django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3401c396-596b-a021-fc29-eb1250980d7c%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
django-users+unsubscr...@googlegroups.com.
To post to this group, send email to 
django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCfwSDW9jRLptDhnNBTt82oUc%2BiAJwpiBdYcfH0%3DPXg4TA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3f013635d92343fcb4fb0d2d51d1bbff%40ISS1.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.

Re: how to combine views in one template

[yingi keme]

def builddetails(request, id):
build = Build.objects.get(pk=id)
Obj = BuildForm(request.POST)
Obj.save()
return render(request, .)




> On 16 Jun 2017, at 12:03 AM, Mark Alan Jones  wrote:
> 
> Hello Django Community,
> 
> I am new to Django and tackling my first app outside of the tutorial. The app 
> I'm working on is a simple ticket system for build requests at my IT Company. 
> I only have one model 'Build', and I have checkboxes that denote how far the 
> build has been done. 
> 
> I have a page that shows all build requests, and then a separate page with 
> the details of each build request. I want to add a form to this builddetails 
> template, but I'm not sure what is the correct way to do this when the 
> template is already pulling info from the model. Every tutorial I've followed 
> has shown using a form under a separate URL, but that is not viable.
> 
> my current view for builddetails is this:
> 
> def builddetails(request, id):
> build = Build.objects.get(pk=id);
> return render(request, 'app/builddetails.html', { 'build': build });
> 
> How do I combine this with a ModelForm on the same page? 
> 
> the ModelForm I was trying to use looks like this:
> 
> class BuildForm(forms.ModelForm):
> class Meta:
> model = Build,
> fields = ['notes', 'build_engineer', 'latest_bios','bios_settings', 
> 'hot_keys_tested', 'office_activated']
> 
> If I need to provide any more information please let me know, and thank you 
> so much in advance for any help you can offer. 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/733168e2-2559-4726-9067-dc2a23397bb7%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/A194F7C1-2840-4090-BF25-ECD003805839%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Custom field implementing Boolean Field is having response value as None instead of False

[Priyanka Thakur]

Hi,

I am doing migration from Django 1.7 to 1.10 version and has a custom 
django field.

Below is the custom class for the field:



from django.db import models



class HibernateBooleanField(models.BooleanField):

def from_db_value(self, value, expression, connection, context):

return self.to_python(value)


def get_internal_type(self):

return "HibernateBooleanField"


def db_type(self, connection):

return 'bit(1)'


def to_python(self, value):

if value in (True, False):

return value

if value in ('t', 'True', 'true', '1', '\x01'): return True

if value in ('f', 'False', 'false', '0', '\x00', None): return False


def get_db_prep_value(self, value, connection, prepared=False):

return 0x01 if value else 0x00


def get_db_prep_save(self, value, connection):

return 0x01 if value else 0x00


def get_prep_value(self, value):

return self.to_python(value)

---


I have defined a field in the model as:



class MetaMetadata(models.Model):

is_folder = HibernateBooleanField()



When I invoke a POST request on API in my test case , I get the value for 
this field as "None" in response. 


The API is :


response = self._client.post('/xyz/api/metametadatas/',
   {'edit_view': "TestEditView",
  'grid_view': "TestGridView",
  'name': "Test Metametadata",
  'sort_key': 9000,
  'parentid': 0,
  'version':0,
  'id': 100}, format='json')



Please explain , what is it that I'm doing wrong. Why isn't to_python method 
getting invoked ? Am I missing something?


Regards,

Priyanka


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3e95b214-8a06-4482-b092-c9dd6a32b6fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: User has no dcf_profile : RelatedObjectDoesNotExist

[Melvyn Sopacua]

On Friday 16 June 2017 03:17:00 Nabil BOUDERBALA wrote:
> After extending an existing user model, I get
> RelatedObjectDoesNotExist exception with a value User has no
> dcf_profile. I seems that dcf_profile isn't created automatically for
> each user.

That's correct. That's your job and the documentation gives you a hint on how 
to do it:

These profile models are not special in any way - they are just Django models 
that happen 
to have a one-to-one link with a user model. As such, they aren’t auto created 
when a user 
is created, but a django.db.models.signals.post_save[1] could be used to create 
or update 
related models as appropriate.

-- 
Melvyn Sopacua


[1] 
https://docs.djangoproject.com/en/1.11/ref/signals/#django.db.models.signals.post_save

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2503988.A6k4gYsYkB%40devstation.
For more options, visit https://groups.google.com/d/optout.

Re: DSasS(Data Science as Service)

[Melvyn Sopacua]

On Friday 16 June 2017 04:45:22 Arshpreet Singh wrote:


> So basically there will be few ML models and I will feed those some
> variables and will get some output. Before writing any kind of code I
> am interested in the architecture of the whole system. Django is the
> option to use and do things.
> 
> I am bit confused and not sure where I should start to do things?

You do things in models.
You gather things in views.
You render things in templates.
You make things available through urls.

Pretty much.
-- 
Melvyn Sopacua

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2844863.WQle7T2J5x%40devstation.
For more options, visit https://groups.google.com/d/optout.

Re: Custom field implementing Boolean Field is having response value as None instead of False

[Melvyn Sopacua]

On Friday 16 June 2017 07:33:22 Priyanka Thakur wrote:
> Hi,
> 
> I am doing migration from Django 1.7 to 1.10 version and has a custom
> django field.
> 
> Below is the custom class for the field:
> 
> 
> 
> from django.db import models
> 
> 
> 
> class HibernateBooleanField(models.BooleanField):
> 
> def from_db_value(self, value, expression, connection, context):
> 
> return self.to_python(value)
> 
> 
> def get_internal_type(self):
> 
> return "HibernateBooleanField"
> 
> 
> def db_type(self, connection):
> 
> return 'bit(1)'
> 
> 
> def to_python(self, value):
> 
> if value in (True, False):
> 
> return value
> 
> if value in ('t', 'True', 'true', '1', '\x01'): return True
> 
> if value in ('f', 'False', 'false', '0', '\x00', None): return
> False

and if value is something else, nothing (aka None) is returned. You have no 
else clause here.

-- 
Melvyn Sopacua

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7550235.97tRNztyJN%40devstation.
For more options, visit https://groups.google.com/d/optout.

Re: Raw SQL - How to approach paging and lazy fetching

[Kevin Yu]

Hi Jani,

Thanks for the link. I was aware of this link and actually followed the 
steps when I started the project. I tried using model but then found out 
when i need to query a join, it doesn't seem to work unless there's a 
foreign key between the two models, however, given it's a legacy database, 
i can't touch the schema at all. Is it possible to query join results with 
managed=False?

Thanks
On Thursday, June 15, 2017 at 11:31:42 PM UTC-7, Jani Tiainen wrote:
>
> Hi,
>
> Even you do have legacy database, you can use unmanaged models and then 
> leverage full power of ORM [1].
>
> Just create models and in their Meta set managed = False and there you go. 
>
> And what comes to paging - you need to somehow pass offset and limit to 
> your query.
>
> [1] https://docs.djangoproject.com/en/1.11/howto/legacy-databases/
>
> On 16.06.2017 02:05, Kevin Yu wrote:
>
> Hi All, 
>
> I am using raw sql to connect to database. The reason we used raw sql 
> instead of the Django model is because the database is legacy and is being 
> shared by multiple applications...
>
> I have one use case that I'm struggling right now. Basically I have a page 
> that fetch more than 1000 results. My query is like this:
>
> cursor = connection.cursor()
> cursor.execute('''
> SELECT br.id, br.name, br.created_at, br.updated_at,
> br.branchpoint_str, br.source
> FROM branches as br
> LEFT JOIN branches_projects as bp
> ON br.id = bp.branch_id 
> WHERE bp.project_id = "%s" AND source != "other"
> ORDER BY updated_at DESC
>''', [int(project_id)]
>)
>
> Then in my template, I have this:
> {% for br in special_branches %}
>
>link="/files/{{build.image_path}}/build{{build.build_number}}/">
> {{br.name}}
> {{br.branchpoint}}
> {{ br.source|upper }}
> {{br.updated_at}}
> {{br.built_at}}
>   
> {% endfor %}
>
> The current problem is this would create a very long page... I am 
> wondering how to approach this problem so that I can have different page on 
> the template, and say 100 result per page, when i click the second page, 
> then  django will fetch result 100-200.
>
> Thanks!
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users...@googlegroups.com .
> To post to this group, send email to django...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/f6a3df97-8218-4fb8-b200-f4535797e135%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Jani Tiainen
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7e4a44fc-e5ce-4562-8b75-09ba065e34f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: DSasS(Data Science as Service)

[Frank Gau]

+1 for this excellent summary!


On Fri, Jun 16, 2017 at 05:09:11PM +0200, Melvyn Sopacua wrote:
> On Friday 16 June 2017 04:45:22 Arshpreet Singh wrote:
> 
> 
> > So basically there will be few ML models and I will feed those some
> > variables and will get some output. Before writing any kind of code I
> > am interested in the architecture of the whole system. Django is the
> > option to use and do things.
> > 
> > I am bit confused and not sure where I should start to do things?
> 
> You do things in models.
> You gather things in views.
> You render things in templates.
> You make things available through urls.
> 
> Pretty much.
> -- 
> Melvyn Sopacua
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/2844863.WQle7T2J5x%40devstation.
> For more options, visit https://groups.google.com/d/optout.

-- 
sent with 100% wireless electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/20170616172307.GB12081%40fgau7270.localdomain.
For more options, visit https://groups.google.com/d/optout.

Re: Raw SQL - How to approach paging and lazy fetching

[Jani Tiainen]

Yes, even there isn't real foreign keys in  the database you can still join
models.

Have been doing that few times with legacy database. When defining fkey you
need to point it to corresponding field in fkey attributes in your model if
it isnt your target model pk.

And you can join nonmanged models with managed just fine.

16.6.2017 19.26 "Kevin Yu"  kirjoitti:

Hi Jani,

Thanks for the link. I was aware of this link and actually followed the
steps when I started the project. I tried using model but then found out
when i need to query a join, it doesn't seem to work unless there's a
foreign key between the two models, however, given it's a legacy database,
i can't touch the schema at all. Is it possible to query join results with
managed=False?

Thanks

On Thursday, June 15, 2017 at 11:31:42 PM UTC-7, Jani Tiainen wrote:

> Hi,
>
> Even you do have legacy database, you can use unmanaged models and then
> leverage full power of ORM [1].
>
> Just create models and in their Meta set managed = False and there you go.
>
> And what comes to paging - you need to somehow pass offset and limit to
> your query.
>
> [1] https://docs.djangoproject.com/en/1.11/howto/legacy-databases/
>
> On 16.06.2017 02:05, Kevin Yu wrote:
>
> Hi All,
>
> I am using raw sql to connect to database. The reason we used raw sql
> instead of the Django model is because the database is legacy and is being
> shared by multiple applications...
>
> I have one use case that I'm struggling right now. Basically I have a page
> that fetch more than 1000 results. My query is like this:
>
> cursor = connection.cursor()
> cursor.execute('''
> SELECT br.id, br.name, br.created_at, br.updated_at,
> br.branchpoint_str, br.source
> FROM branches as br
> LEFT JOIN branches_projects as bp
> ON br.id = bp.branch_id
> WHERE bp.project_id = "%s" AND source != "other"
> ORDER BY updated_at DESC
>''', [int(project_id)]
>)
>
> Then in my template, I have this:
> {% for br in special_branches %}
>
>   
> {{br.name}}
> {{br.branchpoint}}
> {{ br.source|upper }}
> {{br.updated_at}}
> {{br.built_at}}
>   
> {% endfor %}
>
> The current problem is this would create a very long page... I am
> wondering how to approach this problem so that I can have different page on
> the template, and say 100 result per page, when i click the second page,
> then  django will fetch result 100-200.
>
> Thanks!
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users...@googlegroups.com.
> To post to this group, send email to django...@googlegroups.com.
>
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/django-users/f6a3df97-8218-4fb8-b200-f4535797e135%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Jani Tiainen
>
> --
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/
msgid/django-users/7e4a44fc-e5ce-4562-8b75-09ba065e34f5%40googlegroups.com

.

For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAHn91odf6m0O7QSQ4aYfLJvxw8uWGweFGLAfAnwZOnntM-%3Duvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: DSasS(Data Science as Service)

[A.S. Khangura]

On Fri, Jun 16, 2017 at 8:39 PM, Melvyn Sopacua  wrote:

> Pretty much.

Yes that Explains almost everything we need to know for now. :)

Any way you could make me go through Architecture Design of system.
Or any kind of open-Source project where I would be able to study
things and look for how I can make my own?

-- 
Thanks
Arshpreet Singh
Python Developer
Web Development/Data Science/Systems Integration

Life is a journey, not a destination.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAAstK2GDnijf1PSxLUcWpipr2PjCU4KNTWJ0tZ48NzvXKC9UmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.