how can I reference a field from one model to another model

[carlos]

Hello,
I do not know if I'm asking the question correctly, but I need to call a
field of one model in another model
example:
class ModelDad(models.Model):
name = blablabla

class ModelChild1():
   fk(ModelDad)
   number = models.IntegerField()

class ModelChild2():
  fk(ModelDad)
  another_number = models.IntegerField()

   def make_proces(self):
  return self.another_number * ModelChild1.number #this is my question

how can I send a call number within the function (make_proces ) of
ModelChild2

is posible



-- 
att.
Carlos Rocha

-- 
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/CAM-7rO125r3pox%3D137GOfmjnmFaf3cekaNj-j%2B9A0Cwc%3DEM0Fg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Charfield variable length

[Anirudh Jain]

If you are sure that values entered will only be 0s and 1s then why not use
IntegerField(). But if really want to use CharField() and you know that
size won't be larger than 180bits then use CharField(max_lenght=25)

On Thu, 24 Jan 2019, 06:23 Mike Dewhirst  On 24/01/2019 9:14 am, 'Odile Lambert' via Django users wrote:
> >
> > Hello
> >
> > I have problems with the Charfield max_length. In the source code, the
> > possibility exists to have max_length = None but it does not pass
> > Django check when  models.py. contains a charfield = None
> >
> > I can understand that there is a need for such a max_length form the
> > database point of view .
> >
>
> When you run migrate it establishes the size of the Char field *in the
> database*. Therefore it can only be set once per migration.
>
> > My need is the following:
> >
> > I have a set of  fields whose content in the database is a binary code
> > of maximum 180 bits. Most of the time it will be much shorter and
> > there is  in the form a field (max size) giving this maximum size.
> >
> > The user needs to input this field in the database as a Character
> > string of 0 and 1. using hexadecimal fields would be very unpractical.
> > Last but not least, I am using the admin to enter these data in the
> > database.
> >
> > In a first shot, I used a Charfield and*I overwrote the field in the
> > init to set the maximum length to the value chosen by the user. I also
> > modifed the attributes of the widget. But at the end the HTML contains
> > a texinput with the max length set in the model.
> > *
> >
> > Is this an admin feature or did I miss something?
> >
>
> A TextField is a varying length character field. Might be of interest.
>
> A binary field requires bytes not text. I think if I needed binary data
> entered by a user I would use a CharField with a reasonable max_length
> and in the model.save() method I would convert/interpret the data
> entered into precisely the binary format I needed and then
> programmatically store it into a "parallel" binary field. I would
> probably make it readonly in the Admin or just not display it.
>
> I'm not sure about using binary fields with a choice attribute but that
> might be another thing to research.
>
> You can certainly use choices in a CharField to totally restrict the
> data entered.
>
> > . Any other suggestion on how to handle these fields would be welcomed.
> >
>
> It might be easier to offer advice if your use-case was more clear.
>
> > --
> > 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/23ff10f1-41d5-8da1-18a4-07d457be8756%40laposte.net
> > <
> https://groups.google.com/d/msgid/django-users/23ff10f1-41d5-8da1-18a4-07d457be8756%40laposte.net?utm_medium=email_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/e55ea10b-7fc6-efd9-ec87-02b5b75368f2%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/CAC3mK7dpwk%3DrAUDT4VbUZ94rz30JHKHKVe0kDMmrjN_xAcz0zg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Charfield variable length

[Mike Dewhirst]

On 24/01/2019 9:14 am, 'Odile Lambert' via Django users wrote:


Hello

I have problems with the Charfield max_length. In the source code, the 
possibility exists to have max_length = None but it does not pass 
Django check when  models.py. contains a charfield = None


I can understand that there is a need for such a max_length form the 
database point of view .




When you run migrate it establishes the size of the Char field *in the 
database*. Therefore it can only be set once per migration.



My need is the following:

I have a set of  fields whose content in the database is a binary code 
of maximum 180 bits. Most of the time it will be much shorter and 
there is  in the form a field (max size) giving this maximum size.


The user needs to input this field in the database as a Character 
string of 0 and 1. using hexadecimal fields would be very unpractical. 
Last but not least, I am using the admin to enter these data in the 
database.


In a first shot, I used a Charfield and*I overwrote the field in the 
init to set the maximum length to the value chosen by the user. I also 
modifed the attributes of the widget. But at the end the HTML contains 
a texinput with the max length set in the model.

*

Is this an admin feature or did I miss something?



A TextField is a varying length character field. Might be of interest.

A binary field requires bytes not text. I think if I needed binary data 
entered by a user I would use a CharField with a reasonable max_length 
and in the model.save() method I would convert/interpret the data 
entered into precisely the binary format I needed and then 
programmatically store it into a "parallel" binary field. I would 
probably make it readonly in the Admin or just not display it.


I'm not sure about using binary fields with a choice attribute but that 
might be another thing to research.


You can certainly use choices in a CharField to totally restrict the 
data entered.



. Any other suggestion on how to handle these fields would be welcomed.



It might be easier to offer advice if your use-case was more clear.


--
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/23ff10f1-41d5-8da1-18a4-07d457be8756%40laposte.net 
.

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/e55ea10b-7fc6-efd9-ec87-02b5b75368f2%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Re: Admin form_url breakout problem

[Mike Dewhirst]

On 24/01/2019 9:35 am, Matthew Pava wrote:

Have you tried setting APPEND_SLASH = False in your settings?


Yes. The result is ...


 Page not found(404)

Request Method: POST
Request URL: 
http://localhost:8000/admin/substance/substance/1442/change/payment


Using the URLconf defined in|ssds.urls|, Django tried these URL 
patterns, in this order:



... followed by all the urls the most pertinent one of which is ...

^admin/ ^substance/substance/ ^(.+)/change/$ 
[name='substance_substance_change']







-Original Message-
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of Mike Dewhirst
Sent: Wednesday, January 23, 2019 3:48 PM
To: django-users@googlegroups.com
Subject: Re: Admin form_url breakout problem

On 24/01/2019 1:08 am, Matthew Pava wrote:

It looks like your second URL is different than the first.

*/admin/substance/substance/1442/change/payment*

*/admin/substance/substance/1442/change/payment/change/*

If you just want to add a slash, then add it.

*/admin/substance/substance/1442/change/payment/*

I’m guessing that Django is interpreting the second URL like so:

*/admin/substance/substance/(pk=1442/change/payment)/change/*


You are right. It looks like Django expects the last element of the url
to be the id and automatically appends 'change' to a modelAdmin url.
That apparently invokes the 'change' form.

My mission (I think) is to find a way to launch a non-Admin url from
inside the Admin. Or perhaps from a model method.

That is what I meant with the word 'breakout' in the subject line.

Derek suggested a modelAdmin wrapper a few days ago ... "Basically you
can create your own view and use that to display data in a template that
inherits from, for example, the Django admin form template. A bit tricky
first time but then it seems straightforward."

I'm finding it a bit tricky for sure!

If you can see a way ...

Thanks

Mike


*From:*django-users@googlegroups.com
[mailto:django-users@googlegroups.com] *On Behalf Of *Mike Dewhirst
*Sent:* Wednesday, January 23, 2019 12:57 AM
*To:* Django users
*Subject:* Admin form_url breakout problem

How can I break out of the Admin to a payment gateway? I've tried
form_url='billing:payment_view'  in SubstanceAdmin.change_view()
unsuccessfully.

I can semi-break out of the admin and get the beginning of a payment
happening with the following ...

SubstanceAdmin.change_form_template = payment.html (which has Stripe
js and necessary hidden fields)
or
./templates/admin/substance/substance/change_form.html (identical to
payment.html except it calls block.super at the end to render the rest
of the admin page)

SubstanceAdmin.change_view() which collects the contextual data
required for either template

IngredientsInline.form (inherits  admin.StackedInline.form) for all
the hidden fields for each ingredient.

With all that, if an ingredient hasn't been paid for, the
billing.Subscription record won't have a Stripe token so the Admin
will launch the payment page. On entering credit card detail and
pressing the button, Stripe happily takes the money and issues a
token. BUT the Admin then barfs with ...



   RuntimeError at /admin/substance/substance/1442/change/payment

You called this URL via POST, but the URL doesn't end in a slash and
you have APPEND_SLASH set. Django can't redirect to the slash URL
while maintaining POST data. Change your form to point to
localhost:8000/admin/substance/substance/1442/change/payment/ (note
the trailing slash), or set APPEND_SLASH=False in your Django settings.


... If I add a slash in the browser address bar and press Enter the
next problem emerges ...



   ValueError at /admin/substance/substance/1442/change/payment/change/

invalid literal for int() with base 10: '1442/change/payment'


... which tells me the Admin is hoping for
/admin/substance/substance/1442/

I don't know where to go now.

My preference would be to leave the Admin somehow and handle the
payment externally with my billing.payment_view() and
billing.success_view() then at the end find a way to give that
hoped-for url to the server and expect the substance to come up
normally in the admin.

Any advice will be greatly appreciated. Happy to show any code you
might want to see.

Many 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/f8061a7d-27b5-c929-c364-d8870829ad3e%40dewhirst.com.au

RE: Admin form_url breakout problem

[Matthew Pava]

Have you tried setting APPEND_SLASH = False in your settings?

-Original Message-
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of Mike Dewhirst
Sent: Wednesday, January 23, 2019 3:48 PM
To: django-users@googlegroups.com
Subject: Re: Admin form_url breakout problem

On 24/01/2019 1:08 am, Matthew Pava wrote:
>
> It looks like your second URL is different than the first.
>
> */admin/substance/substance/1442/change/payment*
>
> */admin/substance/substance/1442/change/payment/change/*
>
> If you just want to add a slash, then add it.
>
> */admin/substance/substance/1442/change/payment/*
>
> I’m guessing that Django is interpreting the second URL like so:
>
> */admin/substance/substance/(pk=1442/change/payment)/change/*
>

You are right. It looks like Django expects the last element of the url 
to be the id and automatically appends 'change' to a modelAdmin url. 
That apparently invokes the 'change' form.

My mission (I think) is to find a way to launch a non-Admin url from 
inside the Admin. Or perhaps from a model method.

That is what I meant with the word 'breakout' in the subject line.

Derek suggested a modelAdmin wrapper a few days ago ... "Basically you 
can create your own view and use that to display data in a template that 
inherits from, for example, the Django admin form template. A bit tricky 
first time but then it seems straightforward."

I'm finding it a bit tricky for sure!

If you can see a way ...

Thanks

Mike

> *From:*django-users@googlegroups.com 
> [mailto:django-users@googlegroups.com] *On Behalf Of *Mike Dewhirst
> *Sent:* Wednesday, January 23, 2019 12:57 AM
> *To:* Django users
> *Subject:* Admin form_url breakout problem
>
> How can I break out of the Admin to a payment gateway? I've tried 
> form_url='billing:payment_view'  in SubstanceAdmin.change_view() 
> unsuccessfully.
>
> I can semi-break out of the admin and get the beginning of a payment 
> happening with the following ...
>
> SubstanceAdmin.change_form_template = payment.html (which has Stripe 
> js and necessary hidden fields)
> or
> ./templates/admin/substance/substance/change_form.html (identical to 
> payment.html except it calls block.super at the end to render the rest 
> of the admin page)
>
> SubstanceAdmin.change_view() which collects the contextual data 
> required for either template
>
> IngredientsInline.form (inherits  admin.StackedInline.form) for all 
> the hidden fields for each ingredient.
>
> With all that, if an ingredient hasn't been paid for, the 
> billing.Subscription record won't have a Stripe token so the Admin 
> will launch the payment page. On entering credit card detail and 
> pressing the button, Stripe happily takes the money and issues a 
> token. BUT the Admin then barfs with ...
>
>
>
>   RuntimeError at /admin/substance/substance/1442/change/payment
>
> You called this URL via POST, but the URL doesn't end in a slash and 
> you have APPEND_SLASH set. Django can't redirect to the slash URL 
> while maintaining POST data. Change your form to point to 
> localhost:8000/admin/substance/substance/1442/change/payment/ (note 
> the trailing slash), or set APPEND_SLASH=False in your Django settings.
>
>
> ... If I add a slash in the browser address bar and press Enter the 
> next problem emerges ...
>
>
>
>   ValueError at /admin/substance/substance/1442/change/payment/change/
>
> invalid literal for int() with base 10: '1442/change/payment'
>
>
> ... which tells me the Admin is hoping for 
> /admin/substance/substance/1442/
>
> I don't know where to go now.
>
> My preference would be to leave the Admin somehow and handle the 
> payment externally with my billing.payment_view() and 
> billing.success_view() then at the end find a way to give that 
> hoped-for url to the server and expect the substance to come up 
> normally in the admin.
>
> Any advice will be greatly appreciated. Happy to show any code you 
> might want to see.
>
> Many 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/f8061a7d-27b5-c929-c364-d8870829ad3e%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, 

Charfield variable length

['Odile Lambert' via Django users]

  
  
Hello
I have problems with the Charfield max_length. In the source
  code, the possibility exists to have max_length = None but it does
  not pass Django check when  models.py. contains a charfield = None

I can understand that there is a need for such a max_length form
  the database point of view .
  My need is the following: 

I have a set of  fields whose content in the database is a binary
  code of maximum 180 bits. Most of the time it will be much shorter
  and there is  in the form a field (max size) giving this maximum
  size. 

The user needs to input this field in the database as a Character
  string of 0 and 1. using hexadecimal fields would be very
  unpractical. Last but not least, I am using the admin to enter
  these data in the database.
In a first shot, I used a Charfield and I overwrote the field
in the init to set the maximum length to the value chosen by the
user. I also modifed the attributes of the widget. But at the
end the HTML contains a texinput with the max length set in the
model.  
  
Is this an admin feature or did I miss something?
. Any other suggestion on how to handle these fields would be
  welcomed.

  




-- 
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/23ff10f1-41d5-8da1-18a4-07d457be8756%40laposte.net.
For more options, visit https://groups.google.com/d/optout.

Re: Questions about MySQL notes in Django docs

[Carsten Fuchs]

Hi Tim,

thanks for your reply!

I'm sorry if I left the impression that I had not spent any time with research 
before posting my question!

Unfortunately and mistakenly, I was referring to the 2.1 docs when I am in fact 
still using Django 1.11:
My problem is that I still (have to) use an Oracle 11 database, which in turn 
gets me stuck with Django 1.11 LTS – this is one of the reasons for our planned 
switch to MySQL (unfortunately I was not able to persuade the team to use 
PostgreSQL instead).

Therefore, I have to switch from Oracle 11 to MySQL at Django 1.11.

Thus my question: With #29451 referring to Django 2.0, does the MySQL support 
in Django 1.11 cover MySQL 8, so that I can from there upgrade to newer Django 
versions?

Sorry again for having not made that clear in my initial message!

Best regards,
Carsten



Am 23.01.19 um 16:37 schrieb Tim Graham:
> Yes, Django supports MySQL 8. If you google "django mysql 8" the second 
> result is https://code.djangoproject.com/ticket/29451. Based on the commits 
> there, it looks like Django 2.0.7 and above received the fixes.
> 
> On Wednesday, January 23, 2019 at 5:10:18 AM UTC-5, Carsten Fuchs wrote:
> 
> Dear Django group,
> 
> can you please help me with some questions about
> https://docs.djangoproject.com/en/2.1/ref/databases/#mysql-notes 
>  ?
> (I've been using Django with an Oracle database for years, but I'm new
> to MySQL.)
> 
> a) Does "Django supports MySQL 5.6 and higher." cover MySQL 8? (I'm not
> sure about the status of some tickets and PRs.)
> 
> b) Why is the "mysqlclient" client the recommended choice?
> 
> c) Using MySQL 8 and considering
> https://code.djangoproject.com/ticket/18392 
> , should we set utf8 or
> utf8mb4 as the character set?
> https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html 
> 
> indicates that utf8 is an alias to the deprecated utf8mb3 even with MySQL 
> 8.
> 
> d) Why is isolation level "read committed" preferred over "repeatable
> read"? The text says "Data loss is possible with repeatable read.", but
> how can "repeatable read" have data loss that "read committed" has not?
> 
> Thank you!
> 
> Best regards,
> Carsten


-- 
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/db2f7a92-9d28-97da-7d26-8a8de71a7213%40cafu.de.
For more options, visit https://groups.google.com/d/optout.

Re: Admin form_url breakout problem

[Mike Dewhirst]

On 24/01/2019 1:08 am, Matthew Pava wrote:


It looks like your second URL is different than the first.

*/admin/substance/substance/1442/change/payment*

*/admin/substance/substance/1442/change/payment/change/*

If you just want to add a slash, then add it.

*/admin/substance/substance/1442/change/payment/*

I’m guessing that Django is interpreting the second URL like so:

*/admin/substance/substance/(pk=1442/change/payment)/change/*



You are right. It looks like Django expects the last element of the url 
to be the id and automatically appends 'change' to a modelAdmin url. 
That apparently invokes the 'change' form.


My mission (I think) is to find a way to launch a non-Admin url from 
inside the Admin. Or perhaps from a model method.


That is what I meant with the word 'breakout' in the subject line.

Derek suggested a modelAdmin wrapper a few days ago ... "Basically you 
can create your own view and use that to display data in a template that 
inherits from, for example, the Django admin form template. A bit tricky 
first time but then it seems straightforward."


I'm finding it a bit tricky for sure!

If you can see a way ...

Thanks

Mike

*From:*django-users@googlegroups.com 
[mailto:django-users@googlegroups.com] *On Behalf Of *Mike Dewhirst

*Sent:* Wednesday, January 23, 2019 12:57 AM
*To:* Django users
*Subject:* Admin form_url breakout problem

How can I break out of the Admin to a payment gateway? I've tried 
form_url='billing:payment_view'  in SubstanceAdmin.change_view() 
unsuccessfully.


I can semi-break out of the admin and get the beginning of a payment 
happening with the following ...


SubstanceAdmin.change_form_template = payment.html (which has Stripe 
js and necessary hidden fields)

or
./templates/admin/substance/substance/change_form.html (identical to 
payment.html except it calls block.super at the end to render the rest 
of the admin page)


SubstanceAdmin.change_view() which collects the contextual data 
required for either template


IngredientsInline.form (inherits  admin.StackedInline.form) for all 
the hidden fields for each ingredient.


With all that, if an ingredient hasn't been paid for, the 
billing.Subscription record won't have a Stripe token so the Admin 
will launch the payment page. On entering credit card detail and 
pressing the button, Stripe happily takes the money and issues a 
token. BUT the Admin then barfs with ...




  RuntimeError at /admin/substance/substance/1442/change/payment

You called this URL via POST, but the URL doesn't end in a slash and 
you have APPEND_SLASH set. Django can't redirect to the slash URL 
while maintaining POST data. Change your form to point to 
localhost:8000/admin/substance/substance/1442/change/payment/ (note 
the trailing slash), or set APPEND_SLASH=False in your Django settings.



... If I add a slash in the browser address bar and press Enter the 
next problem emerges ...




  ValueError at /admin/substance/substance/1442/change/payment/change/

invalid literal for int() with base 10: '1442/change/payment'


... which tells me the Admin is hoping for 
/admin/substance/substance/1442/


I don't know where to go now.

My preference would be to leave the Admin somehow and handle the 
payment externally with my billing.payment_view() and 
billing.success_view() then at the end find a way to give that 
hoped-for url to the server and expect the substance to come up 
normally in the admin.


Any advice will be greatly appreciated. Happy to show any code you 
might want to see.


Many 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/f8061a7d-27b5-c929-c364-d8870829ad3e%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/d0ae4053cd254b2bbc982cff3637d0a6%40iss2.ISS.LOCAL 

Re: Channels 2.0 close code and http response status

[RETAIL CYBER]

I can't get it to load mysql on my centos system ?

On Wed, Jan 23, 2019, 9:46 AM  Hey I read the spec of websocket handshake and I believe that in abrupt
> close connection, the server can send either a 403 or 404. I wish there
> were a way to send a 404. :(
>
> On Sunday, June 24, 2018 at 7:21:10 PM UTC+2, Andrew Godwin wrote:
>>
>> I'm not quite sure - WebSockets do have browser differences. You could
>> also try adding a delay between the accept and the close to see if that
>> changes how they handle it.
>>
>> Andrew
>>
>> On Sun, 24 Jun 2018, 06:02 Kirill Tyushchakov, 
>> wrote:
>>
>>> Hi, Andrew! Thanks a lot for your response.
>>> I've changed my consumer's connect method like this:
>>>
>>> def connect(self):
>>> user = self.scope.get('user')
>>> super(NotificationsConsumer, self).connect()
>>> if user.is_anonymous:
>>> self.close(code=4003)
>>>
>>>
>>>
>>> I've tested it in Chrome, Firefox, Safari and IE 11 and here is the
>>> result that I've got:
>>> Chrome - 1006
>>> IE 11 - 1005
>>> Firefox - 4003
>>> Safari - 1006
>>>
>>> It doesn't return 403 HTTP status code. Seems it works fine, but I think
>>> I need to test it more.
>>> So the expected close code appears only in Firefox. Should I consider it
>>> as the browser issue?
>>>
>>>
>>> Hi!

 Close code 1006 means that the connection was closed abruptly by the
 other end (basically, the socket just got chopped off without an actual
 close frame being sent).

 This is what happens when you close during the handshake, which is what
 closing during connect() does - at that point, the connection is still HTTP
 before the upgrade has finished, and so Channels sends a HTTP 403 response
 code down instead. Looks like your browser interprets this as code 1006 for
 a websocket.

 There's no way to change the HTTP response code sent when a handshake
 is terminated at the moment - it's hardcoded (as you can see in Daphne's
 serverReject method, here:
 https://github.com/django/daphne/blob/master/daphne/ws_protocol.py#L200
 ).

 Given that no browser I know of will actually tell you the HTTP
 response code in this case, I don't think there's much value in letting it
 be changed - you're always going to see an aborted WebSocket connection
 code instead. If you want to provide more detail to the user, you can
 instead accept the socket, letting the handshake finish, and then close it
 immediately with a custom WebSocket close code (you can do all of that
 inside connect, I think).

 Andrew

 On Thu, Jun 21, 2018 at 2:52 PM Kirill Tyushchakov 
 wrote:

> Hello everyone!
> I'm new in Django Channels. I'm using Channels 2.0 and I have few
> questions about it.
> I'm using JsonWebsocketConsumer class for my consumer and I wrote my
> definition of connect method like this:
>
> def connect(self):
> user = self.scope.get('user')
> if user.is_anonymous:
> super(NotificationsConsumer, self).connect()
> else:
> self.close(code=4003)
>
>
> On client side I'm using native JS Websocket.
> But when I try to connect to this socket as unauthorzied user I get
> code 1006 and HTTP response status code 403.
>
> My questions is:
> 1) How can I send custom close code to client?
> 2) Can I send another HTTP response status code? In my case 401
>
> --
> 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/446d3be6-438b-4e59-ad4f-7841895f4fcb%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...@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/b758b6f7-91f0-43b8-8ea8-087c137598c4%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> 

Re: Poll Tutorial: I'm stuck I have mysql on my vps I created the database

[Motaz Hejaze]

really your question is not clear ,
what is the error message you got from debugger ??


On Wed, Jan 23, 2019 at 9:29 AM Anirudh Jain 
wrote:

> First of all you can remove 'PORT'. Then the most important thing to do is
> to grant your user privileges to perform operations on mysql database that
> you must have created by the name 'urbanpyt_polls'. The easiest way to do
> is to run this query on mysql : GRANT ALL PRIVILEGES ON *.* TO 
> 'username'@'localhost'
> IDENTIFIED BY 'password';
> You only need to replace 'username' by your user and similarly the
> password.
> After this - python manage.py makemigrations and then migrate
>
> On Wed, Jan 23, 2019 at 12:28 PM RETAIL CYBER 
> wrote:
>
>> has anyone ever install the django on a live web hosting service? if so
>> when it comes to using db is the db virtual just like djangoEnv or do i use
>> the mysql thats on my host? i have a vsp??
>>
>> --
>> 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/fb36ebb9-ad3c-448a-a290-2fac0f7cd345%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> *Anirudh Jain* | *Appreciate you taking time to read the mail.*
>
> --
> 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/CAC3mK7d3nUo%3DUy_%2B0yd8q_nvXHZbcRZmPoZAhuX-Rgg8wb%2BeTQ%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/CAHV4E-cjtC6bYsmS1mRHw-ObmLc4_YXfQP%3DuvDTt%2BJYV%3D8q_rA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Looking for a Django Co-Founder.

[Motaz Hejaze]

If you need a Programming experience only without money funding , i can
help you ..
feel free to contact me at skype:m3tz-hjze

or by mail
trappper...@gmail.com

On Wed, Jan 23, 2019 at 6:41 AM Aditya Singh 
wrote:

> No thanks
>
> On Jan 23, 2019 10:10 AM, "Zack Amaral"  wrote:
>
> @Amitesh
>
> What's your email, I don't want to call internationally at the moment. I
> can call you on zoom, skype or whatsapp. Let me know what works for you.
>
> Cheers,
>
> Zack
>
> On Tue, Jan 22, 2019 at 5:45 AM 'Amitesh Sahay' via Django users <
> django-users@googlegroups.com> wrote:
>
>> Hello Zack,
>>
>> I am based in Indian Standard Time zone. Please let me know about
>> your time zone so that we could try to sync.
>>
>> Regards,
>> Amitesh Sahay
>> *91-750 797 8619*
>>
>>
>> On Tuesday, 22 January, 2019, 5:56:27 PM IST, Zack Amaral <
>> zack.j.ama...@gmail.com> wrote:
>>
>>
>> Abhinav,
>>
>> What’s your availability this week? I’d love to setup a call with you!
>>
>> Thanks for the reply, I look forward to hearing back from you!
>>
>> Cheers,
>>
>> Zack
>>
>> On Tue, Jan 22, 2019 at 3:03 AM Abhinav tuteja <
>> abhinavtuteja1...@gmail.com> wrote:
>>
>> Hey i am a django developer and i we are a team of  2 people with 3 years
>> of experience plz feel free to contact
>> Whats app - 9540824924
>>
>> On Tue, 22 Jan 2019 at 9:23 AM, Zack Amaral 
>> wrote:
>>
>> [image: Boxbe]  This message is eligible
>> for Automatic Cleanup! (zack.j.ama...@gmail.com) Add cleanup rule
>> 
>> | More info
>> 
>> Django Community,
>>
>> Hey you guys, I'm trying to build a platform as a service similar to
>> twitch.tv, are their any django developers out there that would be
>> interested in co-founding my company and helping me develop a MVP to get a
>> seed round of funding? If you're interested I can send you a link to my
>> business plan and UI/UX Design.
>>
>> Respectfully,
>>
>> Zack Amaral
>> We Love Music, LLC
>>
>> --
>> 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/894392e9-e171-47fd-9f2b-17335c7b9189%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Django users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/django-users/dzCLmS7-7Dg/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAEN0qXXUwTomg-jNRXqxOPJbx10XT_8X%3DVDe_v-TJMYf1hmXKA%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/CANG%3DrDmUV5dw8XcjnEUMWT4AUNTxQOEG9%3DrZUd9UGaTo%2BE8h7g%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to a topic in 

Re: Channels 2.0 close code and http response status

[guillaume]

Hey I read the spec of websocket handshake and I believe that in abrupt 
close connection, the server can send either a 403 or 404. I wish there 
were a way to send a 404. :(

On Sunday, June 24, 2018 at 7:21:10 PM UTC+2, Andrew Godwin wrote:
>
> I'm not quite sure - WebSockets do have browser differences. You could 
> also try adding a delay between the accept and the close to see if that 
> changes how they handle it.
>
> Andrew
>
> On Sun, 24 Jun 2018, 06:02 Kirill Tyushchakov,  > wrote:
>
>> Hi, Andrew! Thanks a lot for your response.
>> I've changed my consumer's connect method like this:
>>
>> def connect(self):
>> user = self.scope.get('user')
>> super(NotificationsConsumer, self).connect()
>> if user.is_anonymous:
>> self.close(code=4003)
>>
>>
>>
>> I've tested it in Chrome, Firefox, Safari and IE 11 and here is the 
>> result that I've got:
>> Chrome - 1006
>> IE 11 - 1005
>> Firefox - 4003
>> Safari - 1006
>>
>> It doesn't return 403 HTTP status code. Seems it works fine, but I think 
>> I need to test it more.
>> So the expected close code appears only in Firefox. Should I consider it 
>> as the browser issue?
>>
>>
>> Hi!
>>>
>>> Close code 1006 means that the connection was closed abruptly by the 
>>> other end (basically, the socket just got chopped off without an actual 
>>> close frame being sent).
>>>
>>> This is what happens when you close during the handshake, which is what 
>>> closing during connect() does - at that point, the connection is still HTTP 
>>> before the upgrade has finished, and so Channels sends a HTTP 403 response 
>>> code down instead. Looks like your browser interprets this as code 1006 for 
>>> a websocket.
>>>
>>> There's no way to change the HTTP response code sent when a handshake is 
>>> terminated at the moment - it's hardcoded (as you can see in Daphne's 
>>> serverReject method, here: 
>>> https://github.com/django/daphne/blob/master/daphne/ws_protocol.py#L200
>>> ).
>>>
>>> Given that no browser I know of will actually tell you the HTTP response 
>>> code in this case, I don't think there's much value in letting it be 
>>> changed - you're always going to see an aborted WebSocket connection code 
>>> instead. If you want to provide more detail to the user, you can instead 
>>> accept the socket, letting the handshake finish, and then close it 
>>> immediately with a custom WebSocket close code (you can do all of that 
>>> inside connect, I think).
>>>
>>> Andrew
>>>
>>> On Thu, Jun 21, 2018 at 2:52 PM Kirill Tyushchakov  
>>> wrote:
>>>
 Hello everyone!
 I'm new in Django Channels. I'm using Channels 2.0 and I have few 
 questions about it.
 I'm using JsonWebsocketConsumer class for my consumer and I wrote my 
 definition of connect method like this: 

 def connect(self):
 user = self.scope.get('user')
 if user.is_anonymous:
 super(NotificationsConsumer, self).connect()
 else:
 self.close(code=4003)


 On client side I'm using native JS Websocket. 
 But when I try to connect to this socket as unauthorzied user I get 
 code 1006 and HTTP response status code 403.

 My questions is:
 1) How can I send custom close code to client?
 2) Can I send another HTTP response status code? In my case 401 

 -- 
 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/446d3be6-438b-4e59-ad4f-7841895f4fcb%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...@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/b758b6f7-91f0-43b8-8ea8-087c137598c4%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 

Re: Questions about MySQL notes in Django docs

[Tim Graham]

Yes, Django supports MySQL 8. If you google "django mysql 8" the second 
result is https://code.djangoproject.com/ticket/29451. Based on the commits 
there, it looks like Django 2.0.7 and above received the fixes.

On Wednesday, January 23, 2019 at 5:10:18 AM UTC-5, Carsten Fuchs wrote:
>
> Dear Django group, 
>
> can you please help me with some questions about 
> https://docs.djangoproject.com/en/2.1/ref/databases/#mysql-notes ? 
> (I've been using Django with an Oracle database for years, but I'm new 
> to MySQL.) 
>
> a) Does "Django supports MySQL 5.6 and higher." cover MySQL 8? (I'm not 
> sure about the status of some tickets and PRs.) 
>
> b) Why is the "mysqlclient" client the recommended choice? 
>
> c) Using MySQL 8 and considering 
> https://code.djangoproject.com/ticket/18392, should we set utf8 or 
> utf8mb4 as the character set? 
> https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html 
> indicates that utf8 is an alias to the deprecated utf8mb3 even with MySQL 
> 8. 
>
> d) Why is isolation level "read committed" preferred over "repeatable 
> read"? The text says "Data loss is possible with repeatable read.", but 
> how can "repeatable read" have data loss that "read committed" has not? 
>
> Thank you! 
>
> Best regards, 
> Carsten 
>
>

-- 
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/8881bcd7-2d9e-4e2d-abf8-8dd840dfdbaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading Django views inside template with JQuery

[Nelson Varela]

Use iframes which loads the three different views

-- 
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/b041c366-cafc-49b9-905f-8b681a9e15c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: I need help guys please

[Nelson Varela]

Say what 

> Say what?
>

-- 
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/49402962-6631-446e-8c71-24526b4bf9db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Django Databade

[Matthew Pava]

The database is just a separate application on your computer.

It is _not_ a Python package, so you can’t use pip  to install it.  If your 
host has MySQL and you can’t install PostgreSQL on it, then you might just want 
to make your life easier and install MySQL on your development computer.

Now, you will need a Python package that acts as an interface between Django 
and the database application.  For PostgreSQL, it is psycopg2.  More details 
are in the Django documentation.


From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of RETAIL CYBER
Sent: Wednesday, January 23, 2019 1:01 AM
To: Django users
Subject: Re: Django Databade

when installing on home system will this be like some time of virtual db system 
or should i use like pip to install into the django server? just like 
everything else? im looking to move to my main server I know my host has mysql?
please help me id be very appreciative.

On Tuesday, January 22, 2019 at 12:02:58 PM UTC-6, Matthew Pava wrote:
You can install PostgreSQL on your home system, if I understand your concern 
correctly.

From: django...@googlegroups.com 
[mailto:django...@googlegroups.com] On Behalf Of RETAIL CYBER
Sent: Tuesday, January 22, 2019 10:43 AM
To: django...@googlegroups.com
Subject: Re: Django Databade

My thing is I'm trying to get it to my server I have vps most tutorials I see 
are in the view of someone running it on thier home system.


On Tue, Jan 22, 2019, 9:08 AM Matthew Pava  
wrote:
PostgreSQL is my preference.  Stick with the built-in backends:
https://docs.djangoproject.com/en/2.1/ref/settings/#engine



-Original Message-
From: django...@googlegroups.com 
[mailto:django...@googlegroups.com] On Behalf Of 
official...@gmail.com
Sent: Tuesday, January 22, 2019 8:06 AM
To: Django users
Subject: Django Databade

Guys please kindly advise me, what db is pleasant for django projects, been 
trying to use firebase with pyrebase but it is slow and not efficient.
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 djang...@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/8041ecf4-ab38-4ce3-adf1-7341dc309195%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...@googlegroups.com.
To post to this group, send email to djang...@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/1a4f0e9415bb480f90c6558e5da7b44e%40iss2.ISS.LOCAL.
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...@googlegroups.com.
To post to this group, send email to djang...@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/CAGNKn_BSeEsKOnN0NyzKebU%2BzbOZcc1T8E1Q_FRJDTyT9FX%2BEA%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/c79ff119-4f6e-4f13-8474-77a039a1a4a5%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 

RE: Admin form_url breakout problem

[Matthew Pava]

It looks like your second URL is different than the first.
/admin/substance/substance/1442/change/payment
/admin/substance/substance/1442/change/payment/change/

If you just want to add a slash, then add it.
/admin/substance/substance/1442/change/payment/

I’m guessing that Django is interpreting the second URL like so:
/admin/substance/substance/(pk=1442/change/payment)/change/


From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of Mike Dewhirst
Sent: Wednesday, January 23, 2019 12:57 AM
To: Django users
Subject: Admin form_url breakout problem

How can I break out of the Admin to a payment gateway? I've tried 
form_url='billing:payment_view'  in SubstanceAdmin.change_view() unsuccessfully.

I can semi-break out of the admin and get the beginning of a payment happening 
with the following ...

SubstanceAdmin.change_form_template = payment.html (which has Stripe js and 
necessary hidden fields)
or
./templates/admin/substance/substance/change_form.html (identical to 
payment.html except it calls block.super at the end to render the rest of the 
admin page)

SubstanceAdmin.change_view() which collects the contextual data required for 
either template

IngredientsInline.form (inherits  admin.StackedInline.form) for all the hidden 
fields for each ingredient.

With all that, if an ingredient hasn't been paid for, the billing.Subscription 
record won't have a Stripe token so the Admin will launch the payment page. On 
entering credit card detail and pressing the button, Stripe happily takes the 
money and issues a token. BUT the Admin then barfs with ...



RuntimeError at /admin/substance/substance/1442/change/payment

You called this URL via POST, but the URL doesn't end in a slash and you have 
APPEND_SLASH set. Django can't redirect to the slash URL while maintaining POST 
data. Change your form to point to 
localhost:8000/admin/substance/substance/1442/change/payment/ (note the 
trailing slash), or set APPEND_SLASH=False in your Django settings.

... If I add a slash in the browser address bar and press Enter the next 
problem emerges ...



ValueError at /admin/substance/substance/1442/change/payment/change/

invalid literal for int() with base 10: '1442/change/payment'

... which tells me the Admin is hoping for /admin/substance/substance/1442/

I don't know where to go now.

My preference would be to leave the Admin somehow and handle the payment 
externally with my billing.payment_view() and billing.success_view() then at 
the end find a way to give that hoped-for url to the server and expect the 
substance to come up normally in the admin.

Any advice will be greatly appreciated. Happy to show any code you might want 
to see.

Many 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/f8061a7d-27b5-c929-c364-d8870829ad3e%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/d0ae4053cd254b2bbc982cff3637d0a6%40iss2.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.

Re: Overriding settings in Django when used by the models

[Vinicius Assef]

I hope you already got this solved. If not, there's a way to achieve what
you are looking for.

Get settings.MIN_SLUG_LENGTH from an environment variable. Use it in your
settings.py:

MIN_SLUG_LENGTH = os.getenv('ENV_MIN_SLUG_LENGTH')

You'll need to set ENV_MIN_SLUG_LENGTH before running your tests in the
shell will run them.

Note: ENV_MIN_SLUG_LENGTH could be any name. This is only for demonstration
purposes, OK?

Shalom!


‪On Mon, 31 Dec 2018 at 02:07, ‫אורי‬‎  wrote:‬

>
> https://stackoverflow.com/questions/53953444/overriding-settings-in-django-when-used-by-the-models
>
> We are using Django for Speedy Net and Speedy Match
>  (currently Django 1.11.17, we
> can't upgrade to a newer version of Django because of one of our
> requirements, django-modeltranslation). Some of our settings are used by
> the models. For example:
>
> class USER_SETTINGS(object):
> MIN_USERNAME_LENGTH = 6
> MAX_USERNAME_LENGTH = 40
>
> MIN_SLUG_LENGTH = 6
> MAX_SLUG_LENGTH = 200
>
> # Users can register from age 0 to 180, but can't be kept on the site 
> after age 250.
> MIN_AGE_ALLOWED_IN_MODEL = 0  # In years.
> MAX_AGE_ALLOWED_IN_MODEL = 250  # In years.
>
> MIN_AGE_ALLOWED_IN_FORMS = 0  # In years.
> MAX_AGE_ALLOWED_IN_FORMS = 180  # In years.
>
> MIN_PASSWORD_LENGTH = 8
> MAX_PASSWORD_LENGTH = 120
>
> MAX_NUMBER_OF_FRIENDS_ALLOWED = 800
>
> PASSWORD_VALIDATORS = [
> {
> 'NAME': 
> 'speedy.core.accounts.validators.PasswordMinLengthValidator',
> },
> {
> 'NAME': 
> 'speedy.core.accounts.validators.PasswordMaxLengthValidator',
> },
> ]
>
> (which is defined in
> https://github.com/speedy-net/speedy-net/blob/uri_merge_with_master_2018-12-26_a/speedy/net/settings/global_settings.py).
> And then in the models I use:
>
> from django.conf import settings as django_settings
> class User(ValidateUserPasswordMixin, PermissionsMixin, Entity, 
> AbstractBaseUser):
> settings = django_settings.USER_SETTINGS
>
> (and then use attributes of settings, such as settings.MIN_SLUG_LENGTH,
> in the class).
>
> The problem is, when I try to override such settings in tests (you can see
> my question & answer on Can I define classes in Django settings, and how
> can I override such settings in tests?
> 
> ), User.settings remains the same and is not overridden by the settings I
> tried to override. This is a problem since in the model I passed
> settings.MIN_SLUG_LENGTH for example to validators, which are also passed
> other values by other models. Is it possible to define the models and
> settings in such a way which the correct settings will be used both in
> production and in tests, including when I want to override them?
>
> I'm aware of this quote from
> https://docs.djangoproject.com/en/dev/topics/testing/tools/#overriding-settings
> :
>
> *Warning*
>
> The settings file contains some settings that are only consulted during
> initialization of Django internals. If you change them with
> override_settings, the setting is changed if you access it via the
> django.conf.settings module, however, Django’s internals access it
> differently. Effectively, using override_settings() or modify_settings()
> with these settings is probably not going to do what you expect it to do.
>
> We do not recommend altering the DATABASES setting. Altering the CACHES
> setting is possible, but a bit tricky if you are using internals that make
> using of caching, like django.contrib.sessions. For example, you will have
> to reinitialize the session backend in a test that uses cached sessions and
> overrides CACHES.
>
> Finally, avoid aliasing your settings as module-level constants as
> override_settings() won’t work on such values since they are only evaluated
> the first time the module is imported.
>
> Which I understand are relevant in this case, but how do I define the
> settings in such a way that I can override them?
> Thanks,
> אורי (Uri)
> u...@speedy.net
>
>
> אורי
> u...@speedy.net
>
> --
> 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/CABD5YeEpMnMAHiNOerSCni3hvntWWzBM7-QFkuZMDfDjsA%3Dx-Q%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are 

Re: Questions about MySQL notes in Django docs

[RETAIL CYBER]

i cant even get it to load


On Wed, Jan 23, 2019 at 4:09 AM Carsten Fuchs  wrote:

> Dear Django group,
>
> can you please help me with some questions about
> https://docs.djangoproject.com/en/2.1/ref/databases/#mysql-notes ?
> (I've been using Django with an Oracle database for years, but I'm new
> to MySQL.)
>
> a) Does "Django supports MySQL 5.6 and higher." cover MySQL 8? (I'm not
> sure about the status of some tickets and PRs.)
>
> b) Why is the "mysqlclient" client the recommended choice?
>
> c) Using MySQL 8 and considering
> https://code.djangoproject.com/ticket/18392, should we set utf8 or
> utf8mb4 as the character set?
> https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html
> indicates that utf8 is an alias to the deprecated utf8mb3 even with MySQL
> 8.
>
> d) Why is isolation level "read committed" preferred over "repeatable
> read"? The text says "Data loss is possible with repeatable read.", but
> how can "repeatable read" have data loss that "read committed" has not?
>
> Thank you!
>
> Best regards,
> Carsten
>
> --
> 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/7d5c0f45-95eb-461b-ace5-3a823aacd2c7%40cafu.de
> .
> 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/CAGNKn_At-91DMscbZzqL7Njt_q6Px7K_ferTF1cZCNcgcgFtsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Questions about MySQL notes in Django docs

[Michal Petrucha]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Wed, Jan 23, 2019 at 11:09:32AM +0100, Carsten Fuchs wrote:
> Dear Django group,
> 
> can you please help me with some questions about
> https://docs.djangoproject.com/en/2.1/ref/databases/#mysql-notes ?
> (I've been using Django with an Oracle database for years, but I'm new to
> MySQL.)
> 
> a) Does "Django supports MySQL 5.6 and higher." cover MySQL 8? (I'm not sure
> about the status of some tickets and PRs.)
> 
> b) Why is the "mysqlclient" client the recommended choice?
> 
> c) Using MySQL 8 and considering
> https://code.djangoproject.com/ticket/18392, should we set utf8 or utf8mb4
> as the character set?
> https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html indicates
> that utf8 is an alias to the deprecated utf8mb3 even with MySQL 8.
> 
> d) Why is isolation level "read committed" preferred over "repeatable read"?
> The text says "Data loss is possible with repeatable read.", but how can
> "repeatable read" have data loss that "read committed" has not?

I can't answer the rest of your questions, but here's a discussion
that might shed some light on this for you (along with the tickets
linked from that thread):
https://groups.google.com/d/msgid/django-developers/1c8af1c8-23dd-4c79-85ce-9486290ae73f%40googlegroups.com

Michal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJcSGR9AAoJEHA7T/IPM/klu9QP/A2hCcibyiFvKBVD2mGOl8Wm
373BMpdq07p5UW3LJHY/sxBy343UuhKqc8/tl7MYGk0l1VsdnIBDEO73AMQPDKE2
LSWdQa5vNWwQR6RR2HdyAmJRDCCCp79eJmLZ8NTBWFCrYYB+u8Oi8dw3dm7zWeRu
PiYaub0+f5WonwREt9x/Ezt5ztI30t65MCqOSTaZOnA2pKmdDYEshRorIdPLtrjA
9k2Uh8XJe/LnKStQy7Vj/L5OJDKGXP3L/GSj1r04ZDrIF9rjOcJMZrcoFBYKHewM
ofC0SVtYvsKx2wcngePAPIthkL0czi05tOeZD1qMRuaLuxQ3zHpr3LFIgfsFn80C
tDjpS6/P8iwi+XWbIFtu2U90mzr1e5feIfgkd2bXxpZEUjdG+GaypJ+T0DEsozu+
ydrupUO4uOOhtQk0DawVkcz4ElM1fibfXFI4XS88c/Ykf9Ptoeib1fXqHxnMjXEf
bpkrqhZEHlnMUx1ftDy2FYE6Jqx9QT7diEaUbQPpggb+7MeJfMDHCiZlgwGijboy
8SUY31/0+lzgQ4v1NlaBU90lEVp8vehLI7qHpJhtPgBzfRxtANEX+O3ghoXlqv5d
Tqyuh0caL6sOOyZPiEhRhGWLvKTA9LmDhbAgJH2gABYnG+8BJZ6yYBHE89LXN4rd
NOYJAcID+ZrMC/wgudjc
=l01c
-END PGP SIGNATURE-

-- 
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/20190123125629.GG8269%40konk.org.
For more options, visit https://groups.google.com/d/optout.

Columna solo lectura en base de datos

[systemsatinel]

Buenas,

Tengo en la base de datos una columna solo lectura, y al guardar un 
formulario de esa tabla en django, me da error de columna solo lectura, 
aunque no se nombre esa columna de solo lectura.
Habría alguna manera de tener ese campo en el modelo, solo para ver datos?


Un saludo

-- 
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/62d39065-fa03-48e2-92ac-70563bc10261%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Recommendations for available apps (elements of marketplace and task management)

[Nikola Penchev]

Cheers!

I am a lawyer with some IT background. My team and I have created a 
prototype product where clients post there legal inquiries, which are 
outsourced by members of our team to various lawyers who we partner with. 
Lawyers are presented with online working area where they can log different 
activities on their work with the clients. All inquiries which we call 
cases are managed centrally and lawyers are only given access to their 
respective cases. We have integrated some automatic emails and 
notifications for members of our team. However, it is all a prototype - I 
have created a bunch of connected google spreadsheets and some scripts to 
automate various processes. It works fine but I want to grow it.

I have recently reviewed the case management solutions of of some friends 
who also work in the legal tech industry. It's based on the Django CMS. I 
liked it but it doesn't really do the job for me so I decided to look for 
some recommendations on available solutions which I can base the product 
on. The necessary features are:


   1. Database for cases, accessible through web app by admins (I call them 
   case managers). They work with the database on a daily basis - assign cases 
   to lawyers, follow case logs, communicate with clients and lawyers;
   2. Service provider (lawyer) interface - a simplified version of the 
   database with more friendly ux. Lawyers are also our clients as service 
   providers and they need an are to manage their cases.
   3. Reporting based on statuses - i.e. how many cases are pending 
   response for client currently;
   4. Email automation - option to send emails to clients and lawyers 
   directly from one app. This should be an options for admins.

These are the initial options with which I want to start. After that I want 
to add an invoicing tool, a payment processor and a voip option. I will 
appreciate and review all recommendations.

-- 
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/a9017e08-9322-4961-9f6b-ec6268358b40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Looking for a Django Co-Founder.

[Vedarth Sharma]

@Zack

Yes, I'm free this week. You can ping me on Hangouts if you want to do a
video call.

On Wed, Jan 23, 2019, 8:12 AM Zack Amaral  @Vedarth
>
> Do you have time for a video call sometime this week?
>
> Cheers,
>
> Zack
>
> On Tue, Jan 22, 2019 at 8:47 AM Vedarth Sharma 
> wrote:
>
>> Looks interesting. I'm interested in working with you on this. I think
>> it's a very good idea.
>>
>> On Tue, Jan 22, 2019, 3:33 PM Zack Amaral >
>>> Sorry about the delay. Can I get an update on everybody that is still
 interested in being a co founder? Let me send you guys a link to my plan, I
 removed access for a couple of you guys. Let me just post a link real
 quick.

>>>
>>>
>>> Here's a link to my plan: https://pitch.liveplan.com/FQNcr/qJbwS
>>> You shouldn't need access to this @tim vogt.
>>>
>>> If you are interested in learning more I'd love to set up a call with
>>> you guys.
>>>
>>> Thanks
>>>
>>> Zack Amaral
>>> We Love Music, LLC
>>>
>>>
>>> --
>>> 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/163989e5-29e6-4701-b140-48ad5d6e85be%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Django users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/django-users/dhBAN-QTfSc/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAK1F8%2Bde1KPhVfn4xXwNtgm8XG-_tB-rXE-4A5QQ47kpfz2LuQ%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/CANG%3DrDmFqy2V16xubKLrH%3DAr%2BOrFv8aZypHgc2gFd1KPAFgP-g%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/CAK1F8%2Bce9unCPk52Z4QLXZbxzH6HuWADKO7mZDHssSHunQ48mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Installing pdftotext library on heroku

[Joel Mathew]

pdftotext library is a requirement in requirements.txt. While trying to
push to heroku, I get the following error:

remote:  Running setup.py install for pdftotext: started
remote:Running setup.py install for pdftotext: finished
with status 'error'
remote:Complete output from command
/app/.heroku/python/bin/python -u -c "import setuptools,
tokenize;__file__='/tmp/pip-build-rnbekz45/pdftotext/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" install
--record /tmp/pip-o0if2tl3-record/install-record.txt
--single-version-externally-managed --compile:
remote:
/app/.heroku/python/lib/python3.6/distutils/dist.py:261: UserWarning:
Unknown distribution option: 'long_description_content_type'
remote:  warnings.warn(msg)
remote:running install
remote:running build
remote:running build_ext
remote:building 'pdftotext' extension
remote:creating build
remote:creating build/temp.linux-x86_64-3.6
remote:gcc -pthread -Wno-unused-result -Wsign-compare
-DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPOPPLER_CPP_AT_LEAST_0_30_0=0
-I/app/.heroku/python/include/python3.6m -c pdftotext.cpp -o
build/temp.linux-x86_64-3.6/pdftotext.o -Wall
remote:pdftotext.cpp:3:10: fatal error:
poppler/cpp/poppler-document.h: No such file or directory
remote: #include 
remote:  ^~~~
remote:compilation terminated.
remote:error: command 'gcc' failed with exit status 1
remote:
remote:
remote:Command "/app/.heroku/python/bin/python -u -c "import
setuptools, 
tokenize;__file__='/tmp/pip-build-rnbekz45/pdftotext/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" install
--record /tmp/pip-o0if2tl3-record/install-record.txt
--single-version-externally-managed --compile" failed with error code
1 in /tmp/pip-build-rnbekz45/pdftotext/
remote:  ! Push rejected, failed to compile Python app.
remote:
remote:  ! Push failed

Normally I'd solve this by installing libpoppler-cpp-dev with apt. But on
heroku, I don't have root access to do that. Is there a solution for this?
Sincerely yours,

 Joel G Mathew

-- 
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/CAA%3Diw__jf69Dcd4QZAGQrSjbL51biA3kZq_LuV%3D6Vu6kHkYj1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Questions about MySQL notes in Django docs

[Carsten Fuchs]

Dear Django group,

can you please help me with some questions about 
https://docs.djangoproject.com/en/2.1/ref/databases/#mysql-notes ?
(I've been using Django with an Oracle database for years, but I'm new 
to MySQL.)


a) Does "Django supports MySQL 5.6 and higher." cover MySQL 8? (I'm not 
sure about the status of some tickets and PRs.)


b) Why is the "mysqlclient" client the recommended choice?

c) Using MySQL 8 and considering 
https://code.djangoproject.com/ticket/18392, should we set utf8 or 
utf8mb4 as the character set? 
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html 
indicates that utf8 is an alias to the deprecated utf8mb3 even with MySQL 8.


d) Why is isolation level "read committed" preferred over "repeatable 
read"? The text says "Data loss is possible with repeatable read.", but 
how can "repeatable read" have data loss that "read committed" has not?


Thank you!

Best regards,
Carsten

--
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/7d5c0f45-95eb-461b-ace5-3a823aacd2c7%40cafu.de.
For more options, visit https://groups.google.com/d/optout.