Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +19167
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/19850
___
Python tracker
<https://bugs.python.org/issu
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue29753>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
Éric's assessment seems correct.
libffi-3.2 (which provided libffi.so.6) got dropped as a dependency from libffi
a few weeks ago.
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/libffi=edbab26c1cbebe62bb9a5ef55a5e0eaf3481a399
Add 2
Filipe Laíns added the comment:
typo: does the default installation not worlK
*does the default installation not work?
--
___
Python tracker
<https://bugs.python.org/issue40
Filipe Laíns added the comment:
Nevermind! I ran it with my system python binary, which is patched to against
this.
--
___
Python tracker
<https://bugs.python.org/issue38
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue40485>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
Can this be closed? I can't reproduce.
$ python -c 'from library.a.a import go; go()'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/a/a/__init__.py", line 2, in go
raise AssertionError('dummy')
AssertionErro
Filipe Laíns added the comment:
My patches should resolve this fully. Please test it to make sure I did not
miss any corner case.
https://github.com/python/cpython/pull/19850
--
___
Python tracker
<https://bugs.python.org/issue29
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue19113>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue40470>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
keywords: +patch
nosy: +FFY00
nosy_count: 2.0 -> 3.0
pull_requests: +19184
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/19871
___
Python tracker
<https://bugs.python.org/i
Filipe Laíns added the comment:
typing.get_type_hints can be used for this, it resolves the annotation string.
>>> def foo(bar: 'int') -> 'bool': pass
...
>>> typing.get_type_hints(foo)
{'bar': , 'return': }
--
nosy: +FFY00
_
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +19185
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/19874
___
Python tracker
<https://bugs.python.org/issu
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue33453>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue40495>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
Right, forgot about that. We can get the first argument name from
inspect.signature and then fetch it from the get_type_hints dictionary, I don't
know a better way to do it.
--
___
Python tracker
<ht
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue37496>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue40536>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
pull_requests: +19473
pull_request: https://github.com/python/cpython/pull/20164
___
Python tracker
<https://bugs.python.org/issue40
Change by Filipe Laíns :
--
pull_requests: +19402
pull_request: https://github.com/python/cpython/pull/20097
___
Python tracker
<https://bugs.python.org/issue40
Filipe Laíns added the comment:
> Just like Travis, Github actions also automatically rebases pull requests
> onto the latest master. As you can see from a recent workflow run, it uses
> the special ref: "refs/remote/pull/20047/merge"
> https://github.com/python/cpy
New submission from Filipe Laíns :
Let's imagine this scenario:
(master history)
abcd - some commit
hijk - change something
(pull request history)
abcd - some commit
defg - add feature
master pull request
abcd - some commit --- defg
Filipe Laíns added the comment:
> * And only then try to skip documentation-only changes
Done :)
--
___
Python tracker
<https://bugs.python.org/issu
Filipe Laíns added the comment:
The workaround presented at
https://github.community/t5/GitHub-Actions/Feature-request-conditional-required-checks/m-p/51344/highlight/true#M8157
seems pretty reasonable. And it seems like travis is alerady doing the same
thing as it doesn't have native
Change by Filipe Laíns :
--
pull_requests: +19299
pull_request: https://github.com/python/cpython/pull/19983
___
Python tracker
<https://bugs.python.org/issue40
Filipe Laíns added the comment:
This is the backtrace I get:
Traceback (most recent call last):
File "/home/anubis/test/multiprocessing-error.py", line 16, in
proc.terminate()
File "/home/anubis/git/cpython/Lib/subprocess.py", line 2069, in terminate
Filipe Laíns added the comment:
Which error are you getting? libffi is provided by your distribution.
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue40
Filipe Laíns added the comment:
I tracked this down to zipimporter. I have one untested patch, when I run
python from my development tree for some reason the zipimport definition at
Lib/zipimport.py is not used. I assume something weird is going on because of
the frozen circular imports. I
Filipe Laíns added the comment:
I submitted a patch. As explained above, this only mitigates the
time-of-check/time-of-action issue in case the process doesn't exist, it *is
not* a proper fix for the issue. But don't see any way to properly fix
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +19321
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/20010
___
Python tracker
<https://bugs.python.org/issu
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue40425>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
This is a simple time-of-check - time-of-action issue, which is why I suggested
that it shouldn't be fixed. I was not aware send_signal did have this check,
which tells us it is supposed to be suported(?). Anyway, to fix it we need to
catch the exception
Filipe Laíns added the comment:
> * Travis-CI, at least, does test against "merge commit", not HEAD of PR
> branch.
Where? https://github.com/python/cpython/blob/master/.travis.yml
> * As you said already, master branch grow after PR is created anyway.
> This issu
Filipe Laíns added the comment:
> "Rather than build the commits that have been pushed to the branch the
pull request is from, we build the merge between the source branch and
the upstream branch."
Okay, great. But this still only happens for Linux. And still has the same
probl
Filipe Laíns added the comment:
> re-trigger the CI, to make everything works correctly with master.
*re-trigger the CI, to make *sure* everything works correctly with master.
--
___
Python tracker
<https://bugs.python.org/issu
Change by Filipe Laíns :
--
keywords: +patch
nosy: +FFY00
nosy_count: 2.0 -> 3.0
pull_requests: +19195
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/19883
___
Python tracker
<https://bugs.python.org/i
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +21206
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22122
___
Python tracker
<https://bugs.python.org/issu
New submission from Filipe Laíns :
As discussed in https://github.com/python/cpython/pull/20441, these tests could
be improved by using the same format of the b32hex{encode,decode} tests.
--
components: Tests
messages: 376468
nosy: FFY00, p-ganssle
priority: normal
severity: normal
Filipe Laíns added the comment:
Yes, it is not needed, but it does provide a fair bit of enhancement. Using
subtests makes more clear what failed when something fails.
I am a bit confused, in PR 20441 I first just copied the current
b32{encode,decode} tests but was given feedback which
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue41990>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
This error most likely happens because sys.path isn't being set properly and
the standard library isn't being included.
We need more information about the specific environment this is triggering.
Which CPython build are you using? The one from Github Actions
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue41977>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue41282>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
Well, actually the environment variables /should/ not matter as -I implies -E.
--
___
Python tracker
<https://bugs.python.org/issue42
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue39679>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Filipe Laíns :
Some Linux distributions, such as Debian, have guidelines against shipping
things like prebuilt wheels.
Taking Debian as an example, they remove the pip and setuptools wheels and
consequently break ensurepip. This also has some implications in the venv
Change by Filipe Laíns :
--
nosy: +FFY00, dstufft, ncoghlan, pradyunsg
___
Python tracker
<https://bugs.python.org/issue42050>
___
___
Python-bugs-list mailin
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue42057>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
nosy: +FFY00
nosy_count: 6.0 -> 7.0
pull_requests: +19697
pull_request: https://github.com/python/cpython/pull/20441
___
Python tracker
<https://bugs.python.org/issu
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue42129>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
Paul, the PR is now merged :). Can you close the bug?
--
nosy: +p-ganssle
___
Python tracker
<https://bugs.python.org/issue16
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue40897>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
pull_requests: +19947
pull_request: https://github.com/python/cpython/pull/20740
___
Python tracker
<https://bugs.python.org/issue40
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue41554>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
Friendly ping on this.
--
___
Python tracker
<https://bugs.python.org/issue41734>
___
___
Python-bugs-list mailing list
Unsub
New submission from Filipe Laíns :
https://github.com/python/core-workflow/issues/380
--
___
Python tracker
<https://bugs.python.org/issue42212>
___
___
Python-bug
Change by Filipe Laíns :
--
nosy: FFY00, vstinner
priority: normal
severity: normal
status: open
title: Check if generated files are up-to-date in Github Actions
___
Python tracker
<https://bugs.python.org/issue42
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +21961
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23042
___
Python tracker
<https://bugs.python.org/issu
Filipe Laíns added the comment:
Ammar, could you confirm the issue is now solved?
--
___
Python tracker
<https://bugs.python.org/issue42773>
___
___
Python-bug
Filipe Laíns added the comment:
Yes, I will look into it. Do we have a time schedule for when this should be
ready, so that I can organize myself?
--
___
Python tracker
<https://bugs.python.org/issue42
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +22846
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24004
___
Python tracker
<https://bugs.python.org/issu
Filipe Laíns added the comment:
This is due to a typo, I commented on the original PR and opened a PR fixing
it. Cheers :)
--
___
Python tracker
<https://bugs.python.org/issue42
Filipe Laíns added the comment:
There is type() to get the runtime type.
https://docs.python.org/3/library/functions.html#type
```python
>>> foo = 1
>>> type(foo)
```
Keep in mind that in Python using type hints does not enforce anything at
runtime. You can say `foo:
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue44340>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue44395>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
keywords: +patch
nosy: +FFY00
nosy_count: 4.0 -> 5.0
pull_requests: +25366
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26781
___
Python tracker
<https://bugs.python.org/i
Filipe Laíns added the comment:
I bissected this to 088a15c49d99ecb4c3bef93f8f40dd513c6cae3b and submitted a
patch making traceback.FrameSummary take into consideration that lineno might
be None, I believe this is probably the correct fix
Change by Filipe Laíns :
--
nosy: +iritkatriel
___
Python tracker
<https://bugs.python.org/issue6>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Filipe Laíns :
During the distutils deprecation, we have identified that there is no good
replacement for the distutils `headers` install path. This path defines where
packages are supposed to install headers on the system.
The setuptools equivalent would be `include
Filipe Laíns added the comment:
Upon further investigation, there are actually two issues here. The first would
be the one I identified already, traceback.FrameSummary not being prepared for
lineno being None, but there is also a regression in lineno being invalid in
this situation
Change by Filipe Laíns :
--
pull_requests: +25367
pull_request: https://github.com/python/cpython/pull/26782
___
Python tracker
<https://bugs.python.org/issue44
Filipe Laíns added the comment:
Both importlib_metadata and importlib_resources have dropped support for Python
2.7 and 3.5, this should now be unblocked.
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue38
Filipe Laíns added the comment:
This was fixed in https://github.com/python/cpython/pull/22915. It can be
closed now.
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue44
Filipe Laíns added the comment:
For references, this was fixed in
https://github.com/python/importlib_resources/commit/9822338e8de57e99aa3c26275ebdbf8925af7bc8#diff-811ea42dba2528e9a6cbedc91e993dc2a9d4b65626ad364c6ded7b03e0d0a1fa
and should go into CPython in the next code sync
Filipe Laíns added the comment:
The supress(FileNotFoundError) context manager now is only active when fetching
the file, not during importlib.resources.path. _path_from_resource_path is not
longer a generator, so supress(FileNotFoundError) is promptly closed after the
return, preventing its
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue42516>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Filipe Laíns :
It would be good to explain what constitutes a resource in the
importlib.resources documentation.
As per the current implementation, they should be defined as arbitrary files
contained in the package. Is this correct?
--
assignee: docs@python
Filipe Laíns added the comment:
Yes, it would be good to properly define resources in the current docs. Though,
I am left questioning if that definition is still correct, I assume so given
the implementation. I will open a new bug regarding the documentation of what
is considered a resource
Filipe Laíns added the comment:
Directories are not resources, the reason it previously worked was purely
accidental.
I assume you already found a solution in
https://github.com/python/importlib_resources/issues/85, which would be
importlib.resources.files(__package__) / 'dir'
Can
Filipe Laíns added the comment:
Another idea, would it be possible to add a flag to turn on reproducibility,
sacrificing performance? This flag could be set when generating bytecode, where
the performance hit shouldn't be that relevant
New submission from Filipe Laíns :
errors should be supported by Traversable.open and is currently supported in
importlib.resources.open_text, but Traversable.read_text cannot do it, making
it an unsuitable replacement for open_text.
--
messages: 394088
nosy: FFY00, brett.cannon
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue25625>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Filipe Laíns :
The files()/Traversable api is meant to replace ResourceReader api, but it
falls short in one dimension, tying the abstraction to a file system path.
I propose to document that Traversable users *should* implement __fspath__ if
the Traversable represents
Change by Filipe Laíns :
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
___
Python tracker
<https://bugs.python.org/issu
Filipe Laíns added the comment:
I am gonna wait until/if GH-26272 (#44196) gets merged because this would
conflict with that.
--
___
Python tracker
<https://bugs.python.org/issue44
Filipe Laíns added the comment:
I am gonna wait until/if GH-26272 (#44196) gets merged to submit a PR because
it will conflict with that.
--
components: +Library (Lib)
versions: +Python 3.11
___
Python tracker
<https://bugs.python.org/issue44
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +24886
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26280
___
Python tracker
<https://bugs.python.org/issu
Filipe Laíns added the comment:
Closing as the new --with-wheel-pkg-dir option provides an alternative
mechanism.
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Filipe Laíns :
--
pull_requests: +24877
pull_request: https://github.com/python/cpython/pull/26272
___
Python tracker
<https://bugs.python.org/issue44
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +24878
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26272
___
Python tracker
<https://bugs.python.org/issu
Change by Filipe Laíns :
--
keywords: +patch
pull_requests: +24876
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26271
___
Python tracker
<https://bugs.python.org/issu
New submission from Filipe Laíns :
7f7e706d78ab968a1221c6179dfdba714860bd12 introduced the files() api and
documented a importlib.abc.TraversableReader protocol, but it did not implement
it.
This class is documented and marked as introduced in 3.9, but it's actually
missing
New submission from Filipe Laíns :
ResourceReader used to have this requirement, Traversable does not. We cannot
add a requirement as there might be users not doing this, but we can ask new
users to do so.
We should document that FileNotFoundError should be raised if a file is not
found
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue43066>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue42112>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
The annotations will effectively become strings, instead of object references,
in Python 3.11, which solves this issue.
You can enable this behavior in holder Python version with `from __future__
import annotations`, see PEP 563[1].
>>> c
Filipe Laíns added the comment:
That would not stay true to its meaning. AFAIK there are no implied exceptions
in file objects. Given the meaning of ValueError, I'd say it is appropriate
here.
--
nosy: +FFY00
___
Python tracker
<ht
Filipe Laíns added the comment:
This can be closed now.
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue42043>
___
___
Python-bugs-list mailin
Change by Filipe Laíns :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue42654>
___
___
Python-bugs-list mailing list
Unsubscribe:
Filipe Laíns added the comment:
s/holder/older/
Sorry, my dyslexia is acting up.
--
___
Python tracker
<https://bugs.python.org/issue44192>
___
___
Python-bug
1 - 100 of 249 matches
Mail list logo