-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating spreg to 1.7 #158
Conversation
Changelog: - Add the function NSLX to allow for estimating non-linear SLX models. - Allow Kernel weights in SLX models - Add observation-specific multiplier effects - Other enhancements and bug fixes
wow, sweet! have been meaning to catch up because I've been using spreg lots lately. Been meaning to open another issue, but one thing I've noticed lately is the Didnt want to raise before investigating more, but while I have you here.... :P |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #158 +/- ##
=======================================
- Coverage 69.5% 69.3% -0.2%
=======================================
Files 42 43 +1
Lines 10059 10426 +367
=======================================
+ Hits 6988 7221 +233
- Misses 3071 3205 +134
|
@knaaptime , @jGaboardi , should we stop testing in python 3.9 since it can't solve the environment using the latest version of libpysal? |
Could you please check again using this code version to see if it is resolved? |
will do |
yes, we test on the last 3 released versions of python (so 3.10-3.12 right now) |
fwiw, i get a big warning on import now with this version
|
this seems to be something new in 3.12, a different way in which escape sequences are formatted, see below: from stack overflow In Python 3.12+ the error message is changed from a DeprecationWarning to a SyntaxWarning You can't just go putting backslashes in string literals whenever you want one. A backslash is only allowed when part of one of the valid escape sequences, and it will cause a DeprecationWarning (< 3.12) or a SyntaxWarning (3.12+) otherwise. For example \A isn't a valid escape sequence: So you should always use raw strings or \. I always turn warnings off :-) |
that should have been So you should always use raw strings or \. |
for some reason it takes out the second backslash, so it should be backslash backslash |
In markdown you can escape each backslash in regular text like --> "this is 4 backslashes but renders as two: \\" or you can put it in a code formatted block like --> |
I was copying and pasting from stackoverflow :-)
… On Sep 20, 2024, at 5:15 PM, James Gaboardi ***@***.***> wrote:
for some reason it takes out the second backslash, so it should be backslash backslash
In markdown you can escape each backslash in regular text like --> "this is 4 backslashes but renders as two: \\" or you can put it in a code formatted block like --> \\
—
Reply to this email directly, view it on GitHub <#158 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6STH7Y26O7JP6NB4MZDDLZXSGAVAVCNFSM6AAAAABOSPWFCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGYZDONBUGA>.
You are receiving this because you commented.
|
add gmm_lag, nslx, and dwh to docs
@knaaptime, I believe we are all set from our side! Many thanks. |
Changelog: