Search Criteria
Package Details: python2-scandir 1.10.0-8
Package Actions
Git Clone URL: | https://aur.archlinux.org/python2-scandir.git (read-only, click to copy) |
---|---|
Package Base: | python2-scandir |
Description: | Better directory iterator and faster os.walk() alternative |
Upstream URL: | https://github.com/benhoyt/scandir |
Licenses: | BSD |
Submitter: | hexd |
Maintainer: | hexd |
Last Packager: | hexd |
Votes: | 4 |
Popularity: | 0.015848 |
First Submitted: | 2022-06-12 05:39 (UTC) |
Last Updated: | 2022-06-18 04:43 (UTC) |
Dependencies (2)
- python2AUR (python2-binAUR)
- python2-setuptoolsAUR (make)
Latest Comments
« First ‹ Previous 1 2 3
MarsSeed commented on 2022-06-15 06:58 (UTC)
@ravenblackdusk, yes, I guess so.
And the tests still failed after that?
If yes, could you try to build with the following and report if there is any difference?
ravenblackdusk commented on 2022-06-15 05:54 (UTC)
@MarsSeed I did this and still the same error:
I assume the first line does the purging that you mention?
MarsSeed commented on 2022-06-14 20:26 (UTC) (edited on 2022-06-14 20:27 (UTC) by MarsSeed)
@ravenblackdusk I have tested the build with
makepkg
,yay
andparu
, both with and without definingLC_ALL=C
on the command line. And in every case the build was succesful.Though between the build runs, I've made sure I clean my build dirs (restore them to the original state as cloned from AUR git).
Did you also purge your build caches?
(Btw I've never used Pamac for AUR build, so I cannot help you investigate issues specific to that.)
ravenblackdusk commented on 2022-06-14 13:32 (UTC)
@hexd, installing version 1.10.0-6 I still have the same issue:
hexd commented on 2022-06-13 23:05 (UTC)
@MarsSeed, using
LC_ALL=C
indeed makes it break for me the way @jfk described. I've replacedLC_CTYPE
byLC_ALL
when calling the tests, I hope this fixed the issue.MarsSeed commented on 2022-06-13 22:25 (UTC) (edited on 2022-06-13 22:26 (UTC) by MarsSeed)
@hexd, I've also encountered the same error as @jfk quoted, and your latest fix didn't help.
And also just found the root of the problem: running
makepkg
oryay/paru
etc. withLC_ALL=C
overrides these modules' use ofutf-8
encoding. I've read that originally Python 2's default encoding wasascii
, but modules can explicitly set their environment to use utf-8. (Also CPython is typically built with Unicode support nowadays even for Python 2.7; so not sure if Arch's python2 defaults to utf-8 or just some Python2.7 modules do.)I guess forcing
LC_ALL=C
overrides utf-8 configuration and makes thepython2
runtime environment fall back toascii
e.g. when usingsys.getfilesystemencoding()
.Similar test failures (
UnicodeEncodeError: 'ascii' codec can't encode ...'
) happened when usingLC_ALL=C
while building my newly uploaded python2-pyopenssl module. I fixed it by settingLC_ALL=en_US.UTF-8
in a subshell withincheck()
for running the tests.(The subshell might not be necessary for this though. Arch repo's pyopenssl PKGBUILD that I imported already used the subshell for testing the module, so I just kept it.)
Note; only setting
LC_ALL
to an UTF-8 encoding helped; but none of the following alternatives worked when I tried them either separately or in combination:hexd commented on 2022-06-13 20:23 (UTC)
@jfk, the first error is the reason for all the next ones. I've updated the PKGBUILD to clean up the mess, so that the next checking would start in a clean state, but I still don't know the reason for the first error in your system. If the error is still happening for you, please let me know:
What's your locale? (You can run
env | grep -E '^(LANG|LC_)' | sort
to get all the information I need about your locale);What's the file system type and mounting options? (You can run
findmnt -T ~/.cache/yay/python2-scandir
to get this information).tpaniaki commented on 2022-06-13 13:09 (UTC) (edited on 2022-06-13 13:11 (UTC) by tpaniaki)
Bunch of errors with lateste update (building with yay):
« First ‹ Previous 1 2 3