On 17/06/2020 17:25, Guido van Rossum wrote:
I presume Jupyter also lets you import code from a file, which you edit
outside, Jupyter? Is,that not an option for you?
It's not the file that is the problem, but the lack of it. If I didn't
want to cover classes within the __main__ module, I
I presume Jupyter also lets you import code from a file, which you edit
outside, Jupyter? Is,that not an option for you?
On Wed, Jun 17, 2020 at 04:09 Thomas Viehmann wrote:
> On 16/06/2020 20:02, Guido van Rossum wrote:
> > Very few stars. This suggests not many people care about this problem,
On 16/06/2020 20:02, Guido van Rossum wrote:
Very few stars. This suggests not many people care about this problem, and
that in turn might explain the lukewarm response you find everywhere.
This seems to be the core, and combined with the cost of measuring
performance impacts of adding a new
On 2020-06-17 09:02, Serhiy Storchaka wrote:
16.06.20 21:02, Guido van Rossum пише:
It would certainly be much easier to get through the review process.
Adding a `__filename__` (why not `__file__`?) attribute to classes is
a major surgery, presumably requiring a PEP, and debating the pros and
16.06.20 21:02, Guido van Rossum пише:
It would certainly be much easier to get through the review process.
Adding a `__filename__` (why not `__file__`?) attribute to classes is a
major surgery, presumably requiring a PEP, and debating the pros and
cons and performance implications and fixing
On Tue, Jun 16, 2020 at 2:00 AM Thomas Viehmann wrote:
> Hello,
>
> thank you for your feedback!
> > I could think of a trick that inspect.getsource() might use if the class
> > contains at least one method: it could look at a method and try its
> > `__code__.co_filename` attribute (maybe only
Hello,
thank you for your feedback!
I could think of a trick that inspect.getsource() might use if the class
contains at least one method: it could look at a method and try its
`__code__.co_filename` attribute (maybe only if the `__file__` attribute
for the module found via the class's
On Mon, Jun 15, 2020 at 7:22 AM Thomas Viehmann <
tv.python-dev.python@beamnet.de> wrote:
> Hello,
>
> thank you for making Python and the neat inspect module.
>
> I would love to hear your opinion on the following aspect of inspect
> that I believe might be worth improving:
>
> Consider the
