Regression in 1.3
See original GitHub issueHello,
I’m getting a TypeError NoneType object is not iterable
when saving an object in the admin.
I think it’s related to the line above where the check for None was removed.
https://github.com/gregmuellegger/django-sortedm2m/commit/428a8a85c0e7fad42e6d89db4d3a0ab10a508017#commitcomment-17613670
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
1.3 - The Simple Linear Regression Model | STAT 501
The line — which is called the "population regression line" — summarizes the trend in the population between the predictor x and the...
Read more >Page 1 Section 1.3: Linear Regression Regression is the ...
Section 1.3: Linear Regression. Regression is the method of finding the best fitting formula for a data set. ... Calculator commands for regression:....
Read more >1.3 Linear Regression - Bailey Math
1.3 Linear Regression. Regression is all about using data to find an equation which best shows the relationship between variables. We then use...
Read more >Module 1.3: Review of Regression Analysis - edX Edge
Center for Effective Global Action. University of California, Berkeley. Module 1.3: Review of Regression Analysis. Contents. 1. Introduction .
Read more >Regression
We shall be looking at regression solely as a descriptive statistic: what is the line which lies 'closest' to a given set of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just released 1.3.2, containing a fix for this issue. Thanks to @NinjaDero for the fix. https://pypi.python.org/pypi/django-sortedm2m
Hi, sorry for breaking it! This slipped through the review for the last release. This will get fixed soonish with #83