Élie Gouzien

You are right, I was thinking about the one from git. Lines like ``` -static void describe(struct commit *cmit, int last_one) ``` are not considered by diffr as a diff...

One remark, there is also LangugageTool checks for tikz node names, and path separations (`--`).

I totally agree it is the right way to do numerics, but my point is that it should be written in the documentation. For now the user have no way...

@JRD801 : not exactly, physicist don't "assume hbar = 1", but express their equations in a dimensionless way (said differently, they express the Hamiltonian in units of hbar). Once again,...

Hi, I've experienced similar bugg, without any pandas. Here is a minimal exemple : ```python class Bugger(object): def __init__(self, size=10000): """Create bigg data.""" self.big_data = [list(range(i)) for i in range(size)]...

### For the completion I've put `pdb.set_trace()` at the beginning of the `__repr__()` method and called the completion through `get_ipython().complete('test.ea')` . The result is that we end there because it's...

### For the completion @takluyver You are true there is a clear clash between those two jobs of `repr` (by the way I never understood why it's not `str` used...

### Completion I've filled an issue in jedi's repository : [Jedi issue #919](https://github.com/davidhalter/jedi/issues/919). ### Call tip For the call tip another solution would be rather than changing the default inspector...

The completion part is now fixed (in jedi dev branch, not yet released). For the call type part I tried to put a `detail_level=-1` at the right place but just...

Now I understand better how things work (by the way my question about `_call_tip` was because I failed to properly isolate my dev version). @Carreau You are completely true `detail_level=-1`...