bad assignment error

Fixing "zsh: bad assignment" error in Linux

The other day I was trying to create an alias in Linux for repetitive commands. An alias is a name that is translated as another name or command (or a set of commands).

So, I tried to create the alias in the following manner:

And it threw me the following error:

If you are a regular user of the Linux command line, you must have identified the error on the previous command. But I was preoccupied with my program in C++ and I did not notice the obvious error here.

In fact, I thought it to be an error with the way I used the combination of error for the alias. So, I fiddled for a couple of minutes and just to make sure what I was doing wrong, tried this command:

Now, I was certain that there was no error with the commands this time but I git the same result as above:

And that’s when I realized my mistake. You see, I have been working a lot with C++ and was following the standard of using spaces before and after the assignment operator (=). And that is what I used here as well. And shell does not like the wastage of “space”.

I removed the extra white spaces before and after the = and voilà! There it worked like a charm.

In fact, the same error can be encountered with the export command as well or any other variable assignments in the shell. There should not be spaces before and after equals sign.

This taught me a lesson to not waste white space while dealing with shell scripts and Linux commands. It’s not the same as writing programs in other languages.

I would add this tiny learning lesson to my list of things to know about the Linux terminal.

I hope you would not have to waste your time with this problem if you mind those spaces before and after the equals sign.

Abhishek Prakash

Created It's FOSS 11 years ago to share my Linux adventures. Have a Master's degree in Engineering and years of IT industry experience. Huge fan of Agatha Christie detective mysteries 🕵️‍♂️

How To Fix Ubuntu Update Error: Problem With MergeList

How to fix "repository is not valid yet" error in ubuntu linux, how to use nightlight feature in linux mint to save your eyes at night, fixing 'shell script opening in text editor' in ubuntu and other linux, handling 'cannot refresh snap-store' error in ubuntu 24.04, it's foss.

Making You a Better Linux User

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to It's FOSS.

Your link has expired.

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.

• View all errors
• JSLint errors
• JSHint errors
• ESLint errors
• View all options
• JSLint options
• JSHint options
• ESLint options

Bad assignment

This warning has existed in two forms across the three main linters. It was introduced in the original version of JSLint and has remained in all three tools ever since.

In JSLint and JSHint the warning given has always been "Bad assignment"

In ESLint the warning has always been "Invalid left-hand side in assignment"

The situations that produce the warning have not changed despite changes to the text of the warning itself.

When do I get this error?

The "Bad assignment" error (and the alternative "Invalid left-hand side in assignment" error) are thrown when JSLint, JSHint or ESLint encounters an assignment expression in which the left-hand side is a call expression . In the following example we have an if statement with an assignment expression where you would normally expect a conditional:

JSLint also raises this warning when it encounters an assignment to a property of the arguments object . In this example we attempt to define an x property:

Why do I get this error?

In the case of assignment to a function call this error is raised to highlight a fatal reference error . Your code will throw an error in all environments if you do not resolve this issue. It makes no sense to assign a value to a call expression. The return value will be a literal value (such as a string or number) or an object reference, neither of which can be directly assigned to. Imagine it as if you're trying to do 123 = 234 .

If you're receiving the warning in this situation the chances are you were actually trying to perform a comparison rather than an assignment. If that's the case just ensure you're using a comparison operator such as === instead of the assignment operator = :

In the case of assignment to a property of an arguments object this error is raised to highlight a bad practice . The arguments object is notoriously difficult to work with and has behaviour that differs significantly between "normal" and "strict" mode. JSLint has numerous warnings related to abuse of the arguments object but if you're receiving the "Bad assignment" error the chances are you can use a normal variable instead:

In JSHint 1.0.0 and above you have the ability to ignore any warning with a special option syntax . Since this message relates to a fatal reference error you cannot disable it.

In ESLint this error is generated by the Esprima parser and can therefore not be disabled.

About the author

This article was written by James Allardice, Software engineer at Tesco and orangejellyfish in London. Passionate about React, Node and writing clean and maintainable JavaScript. Uses linters (currently ESLint) every day to help achieve this.

Follow me on Twitter  or  Google+

This project is supported by orangejellyfish , a London-based consultancy with a passion for JavaScript. All article content is available on GitHub under the Creative Commons Attribution-ShareAlike 3.0 Unported licence.

Have you found this site useful?

Please consider donating to help us continue writing and improving these articles.

[Fixed] Command Line zsh bad assignment error when setting an Alias – Alias

Quick Fix: When setting an alias, ensure there are no spaces around the = sign. For example, instead of alias foo = bar , use alias foo=bar .

The Problem:

When attempting to set an alias in the zsh terminal using the command alias pip = 'python3 -m pip' , the user encounters the error zsh: bad assignment . The same error occurs when the user tries to add the same line of code to their .zshrc file and refreshes their terminal.

The Solutions:

Solution 1: remove spaces around the equal sign.

The error is caused by spaces surrounding the = sign in the alias definition. To fix it, remove the spaces around the = , like this:

Solution 1: Add single quotes to the alias definition

In the command you’re using to define the alias, you’re missing single quotes around the value you’re assigning to the alias. The correct syntax is:

With the single quotes, the shell will correctly interpret the value you’re assigning to the alias, and the error should disappear.

[Fixed] Angular 4 – Failed: Can't resolve all parameters for ActivatedRoute: (?, ?, ?, ?, ?, ?, ?, ?) – Angular

Cannot infer type arguments for ResponseEntity<> – Java

© 2024 deycode.com

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Why does Zsh complain of my variable assignment as "command not found"?

When I try to write a Zsh script on macOS Big Sur, Version 11.5.1, I noticed that it keeps failing to recognize my variables as variables.

Instead, Zsh treats them as UNIX-like commands.

Screenshot of the problem on the Terminal Application - variable assignment problem for Zsh shell scripts

In the screenshot linked above, I did the following on the Terminal application.

• Showed the contents of the simple Zsh shell script.
• Used the "ls -l" UNIX-like command to indicate its file permissions, and show that it is an executable Zsh shell script.
• Executed the Zsh shell script, which shows that the Zsh script interpreter complains of how my variable name is a "command not found".

The source code for my Zsh shell script is provided as follows:

Can you please kindly let me know what am I missing, and what did I do wrong?

I just want to assign values to variables in my Zsh shell scripts.

Thank you so much, and have a great day! Ciao!

• macos-bigsur

The syntax to assign a value to a variable is foo=bar , not foo = bar . Whitespaces matter. The latter syntax is a command foo with arguments = and bar .

Few examples of how = is interpreted:

This is not specific to Zsh. The POSIX shell ( sh ) and POSIX-compliant shells behave this way. Zsh (while not being POSIX-compliant in general) also follows.

• My upvote can only be recorded but not cast, since my reputation score is low for the "Super User" site of Stack Exchange. That said, thank you so much! It makes a lot of sense now. –  Giovanni Aug 12, 2021 at 19:17

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged macos shell zsh macos-bigsur ..

• The Overflow Blog
• Net neutrality is in; TikTok and noncompetes are out
• Upcoming research at Stack Overflow
• Featured on Meta
• Testing a new version of Stack Overflow Jobs

Hot Network Questions

• Sort a file by lines, regardless of their content
• What is the difference of these MOSFET symbols?
• How does ls know how to output its results?
• Copying and pasting letters of recommendation
• Is it idiomatic to say "I have to race with time" to mean I have to do a thing very fast and finish it before something bad might happen?
• Can facio be used to express visiting someone?
• Horror/Monster movie shown on TV in Basic Instinct
• What is the DC of a Long Jump?
• Table Question: How do I stop the color in a cell from blocking a cline?
• How quickly can a percussionist switch from vibraphone to marimba?
• Efficient method of storing energy in a near-future, semi-hard sci-fi game
• How does complex conjugation act on the Hodge filtration?
• room light controller
• Struggling with PhD in Switzerland: should I transfer to a more favorable climate?
• Elliptic operators over noncompact manifold
• jacking up a car on "grass paving block" - how to secure jack and supports?
• Why does changing one's name to 'Vladimir' indicate allegiance to Moscow?
• Should I use an author's code made available on request to help retract their highly cited paper?
• Visually arrange multi-day events on a calendar
• Could a VTOL aircraft use a helipad for landing/taking off?
• What skills do algebra teachers wish their students had mastered before taking algebra?
• Fish Tank For Merfolk
• The use of the adjective fraught
• How can I use find paired with grep to delete files

SC2276 – ShellCheck Wiki

This is interpreted as a command name containing = . bad assignment or comparison, problematic code:, correct code:.

ShellCheck found a command name containing an unquoted equals sign = . This was likely intended as either a comparison or an assignment.

To compare two values, use e.g. [ "$var" = "42" ]

To assign a value, use e.g. var="42"

Exceptions:

None, though you can quote the = to make ShellCheck ignore it: "$var=42" .

Related resources:

• Help by adding links to BashFAQ, StackOverflow, man pages, POSIX, etc!

ShellCheck is a static analysis tool for shell scripts. This page is part of its documentation.

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

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

Bad Assignment Error #3458

christopherpickering commented Apr 2, 2020

jugglinmike commented Apr 6, 2020

Sorry, something went wrong.

christopherpickering commented Apr 7, 2020

Jugglinmike commented apr 12, 2020, christopherpickering commented apr 14, 2020.

No branches or pull requests

• Skip to main content
• Skip to search
• Skip to select language
• Sign up for free
• Português (do Brasil)

SyntaxError: invalid assignment left-hand side

The JavaScript exception "invalid assignment left-hand side" occurs when there was an unexpected assignment somewhere. It may be triggered when a single = sign was used instead of == or === .

SyntaxError or ReferenceError , depending on the syntax.

What went wrong?

There was an unexpected assignment somewhere. This might be due to a mismatch of an assignment operator and an equality operator , for example. While a single = sign assigns a value to a variable, the == or === operators compare a value.

Typical invalid assignments

In the if statement, you want to use an equality operator ( === ), and for the string concatenation, the plus ( + ) operator is needed.

Assignments producing ReferenceErrors

Invalid assignments don't always produce syntax errors. Sometimes the syntax is almost correct, but at runtime, the left hand side expression evaluates to a value instead of a reference , so the assignment is still invalid. Such errors occur later in execution, when the statement is actually executed.

Function calls, new calls, super() , and this are all values instead of references. If you want to use them on the left hand side, the assignment target needs to be a property of their produced values instead.

Note: In Firefox and Safari, the first example produces a ReferenceError in non-strict mode, and a SyntaxError in strict mode . Chrome throws a runtime ReferenceError for both strict and non-strict modes.

Using optional chaining as assignment target

Optional chaining is not a valid target of assignment.

Instead, you have to first guard the nullish case.

• Assignment operators
• Equality operators

• Contact Sales

Meraki Go - Bad IP Assignment Configuration

• Last updated
• Save as PDF

This message is  warning  or  informational  only. It can only be reported to the phone app if the device is actually online, and checking into the cloud controller. The below image is a representation of what the message may look like in the Meraki Go app:

This alert means a  bad static IP or an  incorrect VLAN tag with DHCP  is being assigned to the Go hardware. Typically, network hardware will simply not work if you assign a bad IP address to it. Meraki Go hardware, however, will automatically switch back to DHCP (automatic IP assignment) so that it can check in to the cloud and alert you about the problem if at all possible.

The most common causes of this error message are:

• The device has had a working static IP, but network changes have caused the IP address to become invalid.
• A typo or otherwise incorrect value while assigning a static IP in the app.
• The wrong VLAN tag is used for DHCP.

How to Troubleshoot

• Switch to DHCP - The error message can only be displayed if the Meraki Go hardware has found another working IP address. By switching the IP assignment to DHCP instead of static (only specify a VLAN tag if you know what it should be), the device will keep using the current addressing and the error will go away over time.
• GX: Typically the GX is connected to the internet. If you require a static IP, speak with the upstream provider to identify the correct IP address information. This can be updated in the app  or local status page .
• GS: Check the upstream router gateway IP address to use, and what the subnet mask should be. If you have a GX in your network, this should be one of the created wired networks (a VLAN) GX IP address as the gateway.
• GR: Treat static IP assignment on the GR similarly to the GS.
• Try a laptop or phone - A laptop using the static IP should be successful as well. If a laptop cannot use the IP address, or a phone, the Meraki Go hardware likely cannot use it as well.

Meraki Community

• Community Platform Help
• Contact Community Team
• Meraki Documentation
• Meraki DevNet Developer Hub
• Meraki System Status
• Technical Forums
• Security & SD-WAN

Meraki MX84 Error Bad IP assignment configuration

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Printer Friendly Page

• Mark as New
• Report Inappropriate Content
• All forum topics
• Previous Topic

• New April 30: Community Platform Update: Adjustments after our redesign
• April 22: [CONTEST CLOSED] Happy Earth Day! ‌🌎 ‌‌💙‌ 💚
• April 15: [SURVEY CLOSED] Share your feedback and snag some swag!
• 3rd Party VPN 141
• Auto VPN 266
• Client VPN 388
• Firewall 482
• Community guidelines
• Cisco privacy
• Khoros privacy
• Terms of service

• Français
• Español

• EtherNet/IP™ to DH+ Gateway
• DeviceNet Router/B
• Two-Port Building Automation Gateway

Bad Assignment error in Sycon software

• ProLinx 4000/5000
• PLX8x Gateways
• QuickServer
• PLX31/32 Gateways
• PLX35 Gateways
• AN-X / AN-X2
• PLX51 Gateways
• Rockwell In-chassis
• Schneider In-chassis
• Accessories
• Legacy Products
• Certifications
• Technical Support
• Miscellaneous
• Friday October 14 2016

When using Sycon software with a PDPM module, you will see a "bad assignment" in the network view menu. This does not indicate an error with the PDPM module communicating to the slave. Sycon software is a generic PROFIBUS master software that is used in many master applications. The bad assignment error relates to an OPC server functionality within Sycon. This feature of Sycon is not available when using Sycon with a ProLinx PDPM module, but rather is designed for when Sycon is being used with a PCI card that is installed in a PC and then takes that data to an OPC application (not a Prosoft product). The network view menu does not indicate status of your network with the ProLinx module. To view the status of the network with our ProLinx module you will want to do an online->start debug mode.

Related Keywords:

PDPM ProLinx modules Sycon software

Attachments

Related products.

• Automated Material Handling
• IIoT Solutions
• Mining and Metals
• Modernization
• Oil and Gas Solutions
• Secure Remote Connectivity
• Water & Wastewater
• Remote Access
• Rockwell Automation In-chassis
• Industrial Wireless
• ProSoft Software

Services & Support

• Knowledge Base
• Regional Technical Support
• Return Material Instructions

News & Events

• ProSoft Insights (Blog)
• Success Stories
• Press Releases
• ProSoft Magazine

Where to Buy

• Distributors
• Corporate Profile
• Quality & Environment
• Industry Recognition
• Affiliations

You're signed out

Sign in to ask questions, follow content, and engage with the Community

• Canvas Badges/Credentials
• Canvas Badges/Credentials Discussion
• Re: Error with badge and associated assignment
• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Printer Friendly Page

Error with badge and associated assignment

• Mark as New
• Report Inappropriate Content
• All forum topics

my badge is awarded to my email

Badgr no longer offering tls 1.2, credentials - how to update the footer of the plat..., unknown error - student reported an "unknown error..., organization v personal account badge awards, community help, view our top guides and resources:.

To participate in the Instructurer Community, you need to sign up or log in:

Cardinals Have 'No Date' Scheduled For Veteran's Return Raising Concern

St. Louis got some bad news about the All-Star slugger as he looks to return

• Author: Patrick McAvoy

In this story:

The St. Louis Cardinals have been navigating through injuries left and right this season and it sounds like one of their veterans may not be back any time soon.

St. Louis -- like many Major League Baseball clubs -- has been heavily impacted by injuries already this season. The Cardinals can't seem to catch a break and it sounds like they will not be getting one reinforcement back shortly unless something changes.

The Cardinals have been without the services of veteran slugger Matt Carpenter since the beginning of April as he's dealt with an oblique injury. It has seemed as though he was close to a return on multiple occasions but he has suffered setbacks in his recovery and at this point there is "no date" scheduled for a minor league assignment, according to MLB.com's John Denton.

"The Cardinals still have no date for when (designated hitter/first baseman) Matt Carpenter (strained oblique) will begin a minor league rehab assignment," Denton said. "Carpenter, who has been out since April 2, has taken (batting practice) on the field several times, but he was recently shut down after receiving a cortisone injection."

It seems as though he has made progress , but his oblique hasn't fully healed at this point. Carpenter may not be the All-Star he once was, but he still is an important piece for the Cardinals. He provides depth off the bench and can help fill in at first base. Plus, he is an important voice in the clubhouse and a leader for the club.

Hopefully, he can make his way back to the field soon.

More MLB: Important Cardinals Outfielder Finally Has Rehab Assignment Scheduled

Latest Cardinals News

Ex-Dodgers Veteran Could Be Much-Needed Depth Piece For Cardinals

Cardinals Surprisingly Mentioned As Option For Superstar Pitcher To Bolster Rotation

Cardinals Legend Reportedly Wants To Become MLB Manager In Near Future

Cardinals Star Sonny Gray Reportedly Makes Progress After Tough Injury

Cardinals' Elite Prospect Could End Up Making Big League Debut Thanks To Stellar Spring

Advertisement

Weinstein’s Conviction Is Overturned: 5 Takeaways

The Court of Appeals overturned Harvey Weinstein’s 2020 conviction on sex crimes charges in New York, but he is not a free man. Here’s what to know.

• Share full article

By Maria Cramer

• April 25, 2024

In a 4-to-3 decision on Thursday, New York’s highest court overturned Harvey Weinstein’s 2020 conviction on felony sex crime charges , a reversal that horrified and dismayed many of the women whose decision to speak out against Mr. Weinstein, a prominent Hollywood producer, accelerated the #MeToo movement.

The New York Court of Appeals agreed with Mr. Weinstein’s defense team that the trial judge who presided over the sex crimes case in Manhattan, Justice James Burke, made a critical error when he let prosecutors call as witnesses several women who testified that Mr. Weinstein had assaulted them, even though none of those allegations had led to charges.

The women became known as Molineux witnesses, a term that refers to trial witnesses who are allowed to testify about criminal acts that the defendant has not been charged with committing. In writing for the majority, Judge Jenny Rivera said permitting such testimony in Mr. Weinstein’s case had served to wrongly “diminish defendant’s character before the jury.”

The ruling, four years after Mr. Weinstein was convicted of forcibly performing oral sex on a production assistant and of raping an actress, did not surprise many legal analysts who had questioned whether prosecutors had taken too big a risk in their efforts to win over the jury.

The Harvey Weinstein Appeal Ruling, Annotated

Read the ruling from New York’s top court that overturned the 2020 conviction of Harvey Weinstein on felony sex crime charges in Manhattan, with context and explanation by New York Times journalists.

In its decision, the court came to the conclusion that prosecutors had done just that and, along with Justice Burke, had violated a central tenet of criminal trials: Defendants should be judged only on the charges against them.

Here are five takeaways from the court’s ruling:

The court cited “egregious errors.”

The court said the trial’s fairness had been compromised by two key prosecution strategies: the use of Molineux witnesses and the prosecutors’ disclosure that if Mr. Weinstein took the stand in his own defense, they would ask him about dozens of allegations of other crimes and boorish, frightening behavior.

Before the trial, during what is known as a Sandoval hearing, Justice Burke said he would let prosecutors question Mr. Weinstein about 28 allegations that included physically attacking his brother, threatening to cut off a colleague’s genitals with gardening shears, throwing a table of food, and screaming and cursing at hotel restaurant staff after they told him the kitchen was closed.

That threat made it impossible for Mr. Weinstein to take the stand even though he was “begging” to testify in his own defense, his lawyer, Arthur Aidala, said during oral arguments before the Court of Appeals in February.

In its majority opinion, the court agreed.

“The threat of a cross-examination highlighting these untested allegations undermined defendant’s right to testify,” Judge Rivera wrote. “The remedy for these egregious errors is a new trial.”

The three dissenting judges slammed the majority.

Three judges — Madeline Singas, Anthony Cannataro and Michael J. Garcia — dissented in a pair of scathing opinions that accused the majority of continuing “a disturbing trend of overturning juries’ guilty verdicts in cases involving sexual violence.”

The judges said the court had ignored evidence that the Molineux witnesses had established: that Mr. Weinstein had displayed a pattern of coercion and manipulation.

Judge Singas said the ruling would make it harder to use such witnesses in future sexual assault cases.

“Men who serially sexually exploit their power over women — especially the most vulnerable groups in society — will reap the benefit of today’s decision,” she wrote.

Judge Cannataro said the additional witnesses the prosecution had presented had helped upend the still-pervasive notion that a sexual assault must involve “the stereotypical stranger in a dark alley who isolates his victim or waits for her to be alone before launching a violent assault.”

The case clearly caused tension among the court, evident in a series of back-and-forth statements between the judges, with the majority defending itself against the dissenters’ claims that the ruling weakened the ability of accusers to push their cases through the criminal court system.

“We do not ‘shut eyes to the enduring effect of rape culture on notions of consent, and intent,’” Judge Rivera wrote, referring to part of Judge Singas’s dissent. “On the contrary, consistent with our judicial role, our analysis is grounded on bedrock principles of evidence and the defendant’s constitutional right to the presumption of innocence and a fair trial.”

Victims and activists are devastated but remain determined.

Dawn Dunning, one of the Molineux witnesses who testified against Mr. Weinstein, said she was asked after the ruling if she regretted testifying.

“My answer is a resounding ‘no,’” she said in a statement. “I am a stronger person for having done so, and I know that other women found strength and courage because I and other Weinstein survivors confronted him publicly. The culture has changed, and I am confident that there is no going back.”

She and others encouraged Alvin L. Bragg, the Manhattan district attorney, to retry the case. The 2020 case was tried under Cyrus R. Vance Jr., Mr. Bragg’s predecessor. Through a spokeswoman, Mr. Bragg said that he would retry the case.

Ashley Judd , the first actress to come forward with allegations against Mr. Weinstein, called the news “unfair to survivors.”

“We still live in our truth,” she said. “And we know what happened.”

Ms. Judd appeared with several other sexual assault survivors and activists on Thursday at a hastily arranged news conference on the 29th floor of the Millennium Hilton in Midtown.

Tarana Burke, the founder of #MeToo, said one of the overarching goals of the movement — to get the court system to take sexual assault cases more seriously — is “long, strategic and thoughtful.”

“The bad thing about survivors is there are so many of us,” she said. “But the good thing about survivors is that there are so many of us.”

Mr. Weinstein’s conviction in California still stands.

Mr. Weinstein, who had been serving a 23-year sentence at Mohawk Correctional Facility in upstate New York, learned about the decision after someone at the prison showed him a news report about the ruling, according to his lawyer, Mr. Aidala.

He talked to Mr. Aidala just after 10 a.m., about an hour after the ruling came down.

Mr. Aidala said Mr. Weinstein “wasn’t emotional, like crying,” but he was “very gracious, very grateful.”

Even with the conviction overturned, Mr. Weinstein is not a free man. He is still facing a 16-year sentence in California, where a jury convicted him in 2022 of raping a woman in a Beverly Hills hotel . He was to serve that term after his New York sentence. Now, he could be transferred to California, but he will most likely be transferred from state prison to Rikers Island, the jail complex in New York City, as he waits for Mr. Bragg to decide whether to push for another trial.

… But he will soon appeal it.

After Thursday’s decision came down, Mr. Weinstein’s lawyer in California, Jennifer Bonjean, said she expected the ruling to help him when he appeals his California conviction on May 20.

A jury in Los Angeles Superior Court deadlocked on charges of sexual battery by restraint, forcible oral copulation and forcible rape in December 2022. Those charges were related to accusations brought by Jennifer Siebel Newsom, a documentary filmmaker and the wife of Gov. Gavin Newsom of California, and Lauren Young, a model and screenwriter.

But the jury found Mr. Weinstein guilty on three other counts — rape, forcible oral sex and sexual penetration — involving an Italian actress who testified that he attacked her in a hotel room in 2013. The jury acquitted Mr. Weinstein of one count of sexual battery involving a massage therapist.

In that case, as in New York, prosecutors were allowed to use witnesses who accused Mr. Weinstein of sex crimes that he had not been charged with. However, the laws around such witnesses are different in California.

Jurors in the California trial were “overwhelmed with this bad character evidence that was not legitimate, that tainted the whole trial in California from our perspective,” Ms. Bonjean said.

Jodi Kantor , Jan Ransom , Chelsia Rose Marcius and Hurubie Meko contributed reporting.

Maria Cramer is a Times reporter covering the New York Police Department and crime in the city and surrounding areas. More about Maria Cramer