🌐 Mailman 3 February 2023 - Python-list - python.org

>>> %matplotlib inline results in SyntaxError: invalid syntax
by Mike S Dec. 25, 2023

Dec. 25, 2023

I have installed Python 3.4.4 on XPSP3 and am trying to work my way through this tutorial. A Complete Tutorial on Ridge and Lasso Regression in Python http://www.analyticsvidhya.com/blog/2016/01/complete-tutorial-ridge-lasso-r… In Step 2 "Why Penalize the Magnitude of Coefficients?" we are shown this code: #Importing libraries. The same will be used throughout the article. import numpy as np import pandas as pd import random import matplotlib.pyplot as plt %matplotlib inline I get an error on the last line. I am running this code in Idle Python 3.4.4 Shell... Python 3.4.4 (v3.4.4:737efcadf5a6, Dec 20 2015, 19:28:18) [MSC v.1600 32 bit (Intel)] on win32 Type "copyright", "credits" or "license()" for more information. >>> import numpy as np >>> import pandas as pd >>> import random >>> import matplotlib.pyplot as plt >>> %matplotlib inline SyntaxError: invalid syntax What am I doing wrong? Suggested reading? TIA, Mike

7 8

Re: How to add CC and BCC while sending mails using python
by akegb3＠gmail.com June 20, 2023

June 20, 2023

On Tuesday, September 30, 2008 8:00:16 AM UTC-8, Bernhard Walle wrote: > Hi, > > * cindy jones [2008-09-30 19:57]: > > > > Can someone tel me how to add cc's and bcc's while sending mails using > > python > > Following (tested) snippet should help: > > ------------------ 8< ------------------------------ > from smtplib import SMTP > from email.mime.image import MIMEImage > from email.mime.text import MIMEText > from email.mime.multipart import MIMEMultipart > > to = 'to_address(a)example.invalid' > cc = 'cc_address(a)example.invalid' > bcc = 'bcc_address(a)example.invalid' > > msg = MIMEMultipart() > msg['To'] = to > msg['Cc'] = cc > msg['From'] = 'bernhard(a)bwalle.de' > msg['Subject'] = 'Test' > text = MIMEText('Das ist ein Test') > text.add_header("Content-Disposition", "inline") > msg.attach(text) > > s = SMTP('test.smtp.relay') > s.sendmail(msg['From'], [to, cc, bcc], msg.as_string()) > s.quit() > ------------------ >8 ------------------------------ > > > Regards, > Bernhard Hello Bernhard, I've tried the above code and the bcc address does not receive the message, on the To & CC addresses receive it. Here are snippets from my code, perhaps something will stand out to you? to = 'ed(a)domain.gov' cc = 'ed(a)gmailmail.com' bcc = 'ed(a)home.net' msg = MIMEMultipart() msg['To'] = to msg['Cc'] = cc msg['Subject'] = 'My Subject text here' msg['From'] = 'edsboss(a)domain.gov' smtp = SMTP("smtpserver") smtp.ehlo() smtp.sendmail(msg['From'], [to, cc, bcc], msg.as_string()) Thanks in advance..hope you're still out there!! ~Ed

3 2

ANN: DIPY 1.6.0
by Eleftherios Garyfallidis March 5, 2023

March 5, 2023

Hello all, We are excited to announce a new release of DIPY: DIPY 1.6.0 is out from the oven! In addition, registration for the oceanic DIPY workshop 2023 (April 24-28) is now open! Our comprehensive program is designed to equip you with the skills and knowledge needed to master the latest techniques and tools in structural and diffusion imaging. An intense hands-on experience in Santa Monica, Los Angeles! See the exquisite program here <https://dipy.org/workshops/dipy-workshop-2023#Schedule> for this highly anticipated event <https://dipy.org/workshops/dipy-workshop-2023>. DIPY 1.6.0 (Monday, 16 January 2023) The release 1.6.0 received contributions from 22 developers (the full release notes are at: https://dipy.org/documentation/1.6.0./release_notes/release1.6/). Thank you all for your contributions and feedback! Please click here <https://dipy.org/documentation/1.6.0./api_changes/#dipy-1-6-0-changes> to check 1.6.0 API changes. Highlights of 1.6.0 release include: - NF: Unbiased groupwise linear bundle registration added. - NF: MAP+ constraints added. - Generalized PCA to less than 3 spatial dims. - Added positivity constraints to QTI. - New functionality to apply Symmetric Diffeomorphic Registration to points/streamlines. - New Human Connectome Project (HCP) data fetcher added. - New Healthy Brain Network (HBN) data fetcher added. - Multiple Workflows updated (DTIFlow, LPCAFlow, MPPCA) and added (RUMBAFlow). - Ability to handle VTP files. - Large codebase cleaning. - Large documentation update. - Closed 75 issues and merged 41 pull requests. To upgrade or install <http://dipy.org/release0.10.html> DIPY Run the following command in your terminal: <http://dipy.org/release0.10.html> pip install --upgrade dipy or conda install -c conda-forge dipy This version of DIPY depends on nibabel (3.0.0+). For visualization you need FURY (0.8.0+). Please support us by citing DIPY in your papers using the following DOI: 10.3389/fninf.2014.00008 <https://www.ncbi.nlm.nih.gov/pubmed/24600385> Questions or suggestions? For any questions go to https://dipy.org, or send an e-mail to dipy(a)python.org <neuroimaging(a)python.org> We also have an instant messaging service and chat room available at https://gitter.im/dipy/dipy Finally, a new forum is available at https://github.com/dipy/dipy/discussions Have a wonderful time using the new version. On behalf of the DIPY developers, Eleftherios Garyfallidis, Ariel Rokem, Serge Koudoro https://dipy.org/contributors

4 3

How to escape strings for re.finditer?
by Jen Kris March 2, 2023

March 2, 2023

When matching a string against a longer string, where both strings have spaces in them, we need to escape the spaces. This works (no spaces): import re example = 'abcdefabcdefabcdefg' find_string = "abc" for match in re.finditer(find_string, example): print(match.start(), match.end()) That gives me the start and end character positions, which is what I want. However, this does not work: import re example = re.escape('X - cty_degrees + 1 + qq') find_string = re.escape('cty_degrees + 1') for match in re.finditer(find_string, example): print(match.start(), match.end()) I’ve tried several other attempts based on my reseearch, but still no match. I don’t have much experience with regex, so I hoped a reg-expert might help. Thanks, Jen

10 38

Re: Is there a more efficient threading lock?
by Jon Ribbens March 2, 2023

March 2, 2023

On 2023-02-26, Barry Scott <barry(a)barrys-emacs.org> wrote: > On 25/02/2023 23:45, Jon Ribbens via Python-list wrote: >> I think it is the case that x += 1 is atomic but foo.x += 1 is not. > > No that is not true, and has never been true. > >:>>> def x(a): >:... a += 1 >:... >:>>> >:>>> dis.dis(x) > 1 0 RESUME 0 > > 2 2 LOAD_FAST 0 (a) > 4 LOAD_CONST 1 (1) > 6 BINARY_OP 13 (+=) > 10 STORE_FAST 0 (a) > 12 LOAD_CONST 0 (None) > 14 RETURN_VALUE >:>>> > > As you can see there are 4 byte code ops executed. > > Python's eval loop can switch to another thread between any of them. > > Its is not true that the GIL provides atomic operations in python. That's oversimplifying to the point of falsehood (just as the opposite would be too). And: see my other reply in this thread just now - if the GIL isn't making "x += 1" atomic, something else is.

8 12

How to fix this issue
by Arslan Mehmood March 2, 2023

March 2, 2023

How I can remove python terminl, its again and again open during working in python. Please help me to resolve this issue. Python 3.11.1 (tags/v3.11.1:a7a450f, Dec 6 2022, 19:58:39) [MSC v.1934 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>>

4 4

Re: Python 3.10 Fizzbuzz
by Hen Hanna March 1, 2023

March 1, 2023

On Monday, August 29, 2022 at 7:18:22 PM UTC-7, Paul Rubin wrote: > Just because. > > from math import gcd > def fizz(n: int) -> str: > match gcd(n, 15): > case 3: return "Fizz" > case 5: return "Buzz" > case 15: return "FizzBuzz" > case _: return str(n) > > for i in range(1,101): > print(fizz(i)) is there any reason to prefer " over ' ?

6 6

Re: Python 3.10 Fizzbuzz
by Greg Ewing March 1, 2023

March 1, 2023

On 28/02/23 5:08 am, Thomas Passin wrote: > On 2/27/2023 11:01 AM, Mats Wichmann wrote: >> If you intend to run Black on your code to ensure consistent >> formatting, you may as well learn to prefer double quotes, because >> it's going to convert single to double > > I prefer single quotes because they are easier to type. I tend to use the convention of double quotes for strings seen by the outside world, and single quotes for internal constants (such as enumerated types that happen to be represented by strings). I guess this means I can't use Black. :-( -- Greg

2 1

Re: Python 3.10 Fizzbuzz
by rbowman March 1, 2023

March 1, 2023

On Mon, 27 Feb 2023 09:01:26 -0700, Mats Wichmann wrote: > If you intend to run Black on your code to ensure consistent formatting, > you may as well learn to prefer double quotes, because it's going to > convert single to double (or: don't learn, and set your IDE to "convert > on save" and don't think about it...) I'd never heard of Black. "By using Black, you agree to cede control over minutiae of hand- formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters." Somehow I don't think we would get along very well. I'm a little on the opinionated side myself.

10 11

Re: How to escape strings for re.finditer?
by Jon Ribbens Feb. 28, 2023

Feb. 28, 2023

On 2023-02-28, Thomas Passin <list1(a)tompassin.net> wrote: > On 2/28/2023 10:05 AM, Roel Schroeven wrote: >> Op 28/02/2023 om 14:35 schreef Thomas Passin: >>> On 2/28/2023 4:33 AM, Roel Schroeven wrote: >>>> [...] >>>> (2) Searching for a string in another string, in a performant way, is >>>> not as simple as it first appears. Your version works correctly, but >>>> slowly. In some situations it doesn't matter, but in other cases it >>>> will. For better performance, string searching algorithms jump ahead >>>> either when they found a match or when they know for sure there isn't >>>> a match for some time (see e.g. the Boyer–Moore string-search >>>> algorithm). You could write such a more efficient algorithm, but then >>>> it becomes more complex and more error-prone. Using a well-tested >>>> existing function becomes quite attractive. >>> >>> Sure, it all depends on what the real task will be. That's why I >>> wrote "Without knowing how general your expressions will be". For the >>> example string, it's unlikely that speed will be a factor, but who >>> knows what target strings and keys will turn up in the future? >> On hindsight I think it was overthinking things a bit. "It all depends >> on what the real task will be" you say, and indeed I think that should >> be the main conclusion here. > > It is interesting, though, how pre-processing the search pattern can > improve search times if you can afford the pre-processing. Here's a > paper on rapidly finding matches when there may be up to one misspelled > character. It's easy enough to implement, though in Python you can't > take the additional step of tuning it to stay in cache. > > https://Robert.Muth.Org/Papers/1996-Approx-Multi.Pdf You've somehow title-cased that URL. The correct URL is: https://robert.muth.org/Papers/1996-approx-multi.pdf

2 1