They shouldn't—Lacy has no business being started in any leagues this week, even if he does play.
So what's the latest status on the young runner? We start with Ian Rapoport of NFL.com:
Unlikely to play. That doesn't sound promising. Bleacher Report's Will Carroll has more on the Lacy front:
There are plenty of reasons to assume the Packers will keep Lacy on the bench for this game. For one, the team has a bye in Week 4, meaning Lacy could be given two weeks of rest and a full week of practice before returning to the field.
For another, the Cincinnati Bengals are allowing just 62.5 rushing yards per game, sixth-best in the NFL. One would guess the game plan would be to attack Cincy through the air, a pretty wise decision given the way Aaron Rodgers, Jordy Nelson, Randall Cobb, James Jones and Jermichael Finley have opened the season.
Besides, James Starks ran 20 times last week for 132 yards and a touchdown—he's a viable starter this week. There really is no upside to rushing Lacy back and risking a second concussion in as many weeks.
And even if he does suit up, Lacy didn't practice all week. It seems highly likely that if he does take the field, it will be in a full timeshare with Starks or as a limited backup, killing the value of each player for fantasy purposes. While you might not worry about a veteran playing after not practicing, a rookie is far more likely to show rust in that situation.
Taken from every angle, there really isn't a reason to have Lacy in your lineup. He's probably not going to play, but even if he does, you have to think he'll be limited. What's worse, if you are handcuffing him with Starks, the thought of both of them sharing time kills the value of each.
It's a lose-lose situation. Keep Lacy firmly planted on your bench this week.
Hit me up on Twitter—I'll answer your fantasy lineup questions, make ill-fated NFL predictions and tweet cheesy jokes. It's basically a party, you guys.