mathurinm

My take: To support both classic Quadratic and weighted Quadratic in one class I see only two options: - have a `Quadratic.weights` attribute, which is `None` if no weights are...

#245 is stalled, you can start a separate PR. You can even start from it, to reuse existing work. To do so first fetch the PR branch, then switch to...

@sujay-pandit are you working on this ? Some people asked for it offline so if you have not started already, I will implement it. But if you're working on this...

This was implemented in #258 through a `WeightedQuadratic` class :rocket: @sujay-pandit thanks one more time for the work, we look forward to hearing some feedback from you. Please spread the...

Agreed ! @PascalCarrivain do you feel like giving a try to migrating from the furo theme to the Book theme for our doc ?

Looks nice @PABannier, this will definitely improve UX! From an API point of view, shouldn't this check be delegated to each solver? This way we don't have one big function,...

This would be a nice addition if we can ship it in the 0.3 release @Badr-MOUFAD , given that we added a few datafits, penalties and solvers !

@Badr-MOUFAD the issue popped up in #188, do you have time to take this over ? A simple check, at the beginning of each solver, that the datafit and penalty...

Requires #191 to be implemented fit to allow for better checks

Trying to revive this to release `v0.4`. Some comments for discussion @QB3 @Badr-MOUFAD - I feel strongly against having both `solver.solve()` and `solver()`. "There should be one-- **and preferably only...