Éric Araujo added the comment:
Broken links should obviously be fixed, either to their newer location if it
can be found or to Web Archive links.
I think that it’s a good thing to link to some outside articles and code from
the official docs; we acknowledge that the stdlib is not the whole
Changes by Éric Araujo :
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue6135>
___
___
Python-bugs-list mailing list
Unsubscribe:
Éric Araujo added the comment:
Nothing to say; waiting for a doc update.
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue13448>
___
___
Éric Araujo added the comment:
PEP 3155 is accepted and makes str(cls) and str(function) as well as repr(cls)
and repr(function) return the qualified name, which obsoletes part of this
request. I haven’t checked if it has the same problem with Python methods.
str(module) is not changed by
Éric Araujo added the comment:
+1 on refusing the temptation to guess and to be half-working for some cases by
accident.
--
___
Python tracker
<http://bugs.python.org/issue3
New submission from Éric Araujo :
Currently distutils2 has two classes and one function to perform 2to3
conversion in the build_py and build_scripts commands. The code is a bit messy
and also lack tests, for example for the conversion of doctests in text files.
I’ve started revamping it so
Éric Araujo added the comment:
Meador, maybe you would like to commit the tests (except for the one that’s the
object of this report) yourself? I don’t mind doing it, but as you have push
rights now maybe you prefer to have your name directly associated with your
work
Éric Araujo added the comment:
It’s a bit hard for me to isolate the distutils problem from the CDBS-specific
parts (maybe because I’m tired :). For years, sub-second resolution was not
supported by distutils, and things were okay as long as the build* commands did
the file creation and
Éric Araujo added the comment:
> Hmm, my initial reaction is that that specific wording is stronger than I had
> in mind -
> there's nothing really wrong with having a shebang line and execute bit set
> on a top level
> module and symlinking it from /usr/bin.
Okay. (
Éric Araujo added the comment:
+1 on grouping existing info into one or two files in the devguide
+1 to removing the wiki pages
+1 on keeping some basic directions in the main docs
--
___
Python tracker
<http://bugs.python.org/issue13
New submission from Éric Araujo :
In 288640098ea8, Jeremy fixed a bug in distutils2.config that prevented d2’s
own setup.py script from working. I had to revert that change because it
caused tests to fail. The bug needs to be identified exactly, then a test for
it is needed, and finally an
Changes by Éric Araujo :
--
priority: normal -> release blocker
___
Python tracker
<http://bugs.python.org/issue13009>
___
___
Python-bugs-list mailing list
Un
Éric Araujo added the comment:
Due to the same reason, it’s also not possible to run “pysetup3.1 metadata” in
the distutils2 repo, or “pysetup2.4 metadata” in the distutils2-python3 repo.
--
___
Python tracker
<http://bugs.python.org/issue12
Éric Araujo added the comment:
Making this a release blocker for d2 1.0a4.
--
priority: normal -> release blocker
___
Python tracker
<http://bugs.python.org/issu
Éric Araujo added the comment:
Do the changes to Python/Python-ast.c and Modules/_ctypes/libffi/src/x86/ffi.c
still apply? (libffi is an external project, but our copy is already edited so
we might as well do one more change).
--
___
Python
New submission from Éric Araujo :
The Quick Start section in the devguide does not tell people what they need to
install in order to compile Python. A short mention or a link to a section
with all info should be added.
I can contribute info for Debian and derivative systems: “aptitude build
Éric Araujo added the comment:
Mucking with your installed Python is probably a bad idea, and it may also be
an old version (compared to the current development version which has seen
hundreds of changes) where testing the patch would not give useful results.
Please see the devguide
Éric Araujo added the comment:
BTW Antoine, will you update the doc to mention __qualname__ or would you like
help?
--
___
Python tracker
<http://bugs.python.org/issue13
Éric Araujo added the comment:
Doc patch looks good.
--
___
Python tracker
<http://bugs.python.org/issue13448>
___
___
Python-bugs-list mailing list
Unsubscribe:
Éric Araujo added the comment:
And of course, right after I post this I look at my terminal and see the “Add
docs” commit. Ignore me.
--
___
Python tracker
<http://bugs.python.org/issue13
Changes by Éric Araujo :
--
Removed message: http://bugs.python.org/msg148253
___
Python tracker
<http://bugs.python.org/issue13448>
___
___
Python-bugs-list m
Changes by Éric Araujo :
--
Removed message: http://bugs.python.org/msg148252
___
Python tracker
<http://bugs.python.org/issue13448>
___
___
Python-bugs-list m
Éric Araujo added the comment:
This is a problem on my side, not in distutils2. My pysetupX.Y scripts are
just shell one-liners of this form:
PYTHONPATH=~/path/to/d2 pythonX.Y -m distutils2.run "$@"
Because of sys.path initialization, d2 tried to import docutils from th
New submission from Éric Araujo :
I recently changed packaging.util.byte_compile, the function used by the
build_py and install_lib commands, so that it can create .pyc and/or .pyo files
independently of the calling’s Python -O or -B flags (dad02a080bbc), but I
think I introduced a bug. To
Éric Araujo added the comment:
(For the reference, the bug I added is this:
http://hg.python.org/cpython/rev/c10946a17420#l6.45
p7g.util.byte_compile calls py_compile.compile with a filename ending in .pyc
or .pyo as appropriate, but the optimization level in the py_compile.compile
function
Changes by Éric Araujo :
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue2377>
___
___
Python-bugs-list mailing list
Unsubscribe:
Éric Araujo added the comment:
You are right, I misinterpreted “use”. I cloned the the PEP 3155 repo and ran
my test script (I’ll attach it for reference) and reprs/strs are indeed "" and ".strip at ...>", so this
request is not obsoleted.
I’ve updated my patch to us
Changes by Éric Araujo :
Added file: http://bugs.python.org/file23772/test-str-repr.py
___
Python tracker
<http://bugs.python.org/issue13224>
___
___
Python-bugs-list m
Changes by Éric Araujo :
Removed file: http://bugs.python.org/file23468/change-class-__str__.diff
___
Python tracker
<http://bugs.python.org/issue13224>
___
___
Python-bug
Changes by Éric Araujo :
Removed file: http://bugs.python.org/file23591/change-some-__str__.diff
___
Python tracker
<http://bugs.python.org/issue13224>
___
___
Python-bug
Changes by Éric Araujo :
--
title: Change str(x) to return only __qualname__ for some types -> Change
str(x) to return only the (qual)name for some types
___
Python tracker
<http://bugs.python.org/issu
Éric Araujo added the comment:
Thanks for the fixed links amk. I think they can be fixed in the repo right
now.
[Eli]
> I still think it's a bigger problem that the page discusses a module which
> is not available on Python 3.x - this means that a user following the page
> can&
Éric Araujo added the comment:
Okay. I just hope that people following the quick start and having build
issues will follow the link.
I followed it and the section only mentions zlib, I think it could be
exhaustive.
--
title: Quick Start in devguide doesn’t mention build
Éric Araujo added the comment:
Alternatively, make patchcheck could print “Did you build the docs?”, just as
it currently prints “Did you run the test suite?” if C or Python files were
modified. Building the docs would not check Misc/NEWS, the original motivation
for this request, but I’m
Éric Araujo added the comment:
> The manual just says "When operating in POSIX mode, shlex will try to be as
> close as
> possible to the POSIX shell parsing rules." but gives no reference to which
> authority it is
> following or what the rules are in either case.
Éric Araujo added the comment:
Thanks for the comments.
> There are really two cases in one bug.
> The first part is that the shell will split tokens at characters that shlex
> doesn't. The handling
> of &, |, ;, >, and < could be done by adjusting the definition
Éric Araujo added the comment:
> [...] The devguide is *already* too big. [...]
> The devguide was supposed to be something that you read quickly and easily,
> not an exhaustive
> reference of how development works. Or at least there should be a clear
> separation between the
&
Éric Araujo added the comment:
Good idea. The functions used are: compose, partial (which we have in
functools), flip, foldl.
I will disagree with “unhealthy”: I’m sure adding this link was a deliberate
exposure of an external module, to put a well-written solution to the spotlight
as a
Éric Araujo added the comment:
I need to fix this for distutils2’s next release (with #13463 and #5302), to
include distutils2/tests/fake_dists.
--
assignee: tarek -> eric.araujo
priority: high -> release blocker
title: Allow package_data globs match directories -> Allow pac
Changes by Éric Araujo :
--
dependencies: +Allow package_data specs/globs to match directories,
package_data only allows one glob per-package
___
Python tracker
<http://bugs.python.org/issue13
Éric Araujo added the comment:
I need this to package test files for distutils2’s own next release, so
pragmatism/compatibility will win for the short term :)
I’ll fix it together with #13463 and #5302.
--
priority: normal -> release bloc
Éric Araujo added the comment:
> Reading PEP 0249 I can see Gerhard is correct, this patch would violate the
> PEP.
Me too.
> I think that the PEP is slightly flawed in that users are encouraged to raise
> exceptions
> called "Warning". IMHO a Warning is never an
Éric Araujo added the comment:
The string in the test does not have mixed line endings, and the accompanying
comment talks about testing files with CRLF on Unix.
Terry, do you want to (update and) commit this?
--
___
Python tracker
<h
Éric Araujo added the comment:
Thanks for the patch. The examples in your message need to be converted to a
patch that applies to 3.2 or 2.7, so that we can reproduce the bug before
fixing it.
--
stage: -> test needed
versions: +Python 2.7, Python
Éric Araujo added the comment:
Patch looks good to me, but I’d like another review.
--
nosy: +ncoghlan
type: feature request -> behavior
versions: +Python 2.7, Python 3.3
___
Python tracker
<http://bugs.python.org/iss
Changes by Éric Araujo :
--
stage: patch review -> test needed
___
Python tracker
<http://bugs.python.org/issue12485>
___
___
Python-bugs-list mailing list
Un
Éric Araujo added the comment:
This is the bug I was thinking about: #7774. Adding some people from that
discussion to nosy.
--
nosy: +flox, haypo, pitrou, ronaldoussoren, schmir
___
Python tracker
<http://bugs.python.org/issue13
Éric Araujo added the comment:
The distutils changes will not happen, we’re under a feature freeze.
Cross-compilation support would need to be added to packaging, and we need to
port Python’s build process to packaging too for 3.4 or 3.5. Also, it’s very
hard to decide to accept one
Éric Araujo added the comment:
Thinking about this, build_py --compile clearly refers to byte-compilation of
Python modules, but the same option on the build command is more ambiguous: It
could be interpreted to mean “skip C compilation
Éric Araujo added the comment:
Because I don’t think anyone will have the time to try to port Python’s
setup.py to packaging, fix the bugs it founds and add the features it needs in
time for 3.3. On my own todo lists, there is much work still needed to define
the public API, add features we
Éric Araujo added the comment:
Just to avoid misunderstandings: The Subversion concept of trunk (or rather
py3k trunk) maps to the Mercurial branch named default, which is what you get
when you clone hg.python.org/cpython. This is 3.3
Éric Araujo added the comment:
Sorry to be of little help. I also have a problem with hashlib, but it’s with
Python 2.4 on Debian multiarch with linux3, so probably different from your
problem. You could try asking on the python-dev mailing list
Éric Araujo added the comment:
> Moreover these dependencies are optional, so there's no need to install them
> unless they are
> specifically needed
I think about it in the reverse: You want a featurefull library, and disable
some things (zlib, ssl, threads) only if you spec
Éric Araujo added the comment:
Okay, then stable branches need a doc/docstring patch to remove the statement
that SpooledTemporaryFile “operates exactly as TemporaryFile does”. Ryan,
would you like to do that patch too?
Antoine, will you commit
Éric Araujo added the comment:
I don’t understand all the issues and it’s too late for me to read all the
thread, but I hope these comments are helpful:
- If our goal is to help naïve users, then one or two new options wouldn’t help
(people want to run “python path/to/thing.py” and want it
Éric Araujo added the comment:
> Of course, that's how it's used. That's all it can do right now.
:) What I meant is that it is *meant* to be used in this way.
> I was was splitting and combining commands (using ;, &&, and ||) and then
> running the result
Éric Araujo added the comment:
Juste a note: currently, when a command sets one option from the value given to
another command, they have the same name, with two kinds of exceptions:
- build --build-lib becomes build_lib --build-dir (etc.)
- install --install-lib becomes install_lib --install
Éric Araujo added the comment:
Eric: Actually I posted my comments after reading only Nick’s message, not
yours, so no worry :)
Nick:
> the "just do the right thing" aspect is covered by PEP 395.
This is great. Thanks for clarifying.
> This is an orthogonal proposal that al
Éric Araujo added the comment:
When someone puts thought into a report or patch, they deserve to be in
Misc/ACKS. Just noticing one typo doesn’t qualify, but pretty much anything
above does. :)
--
nosy: +eric.araujo
versions: -Python 3.4
Éric Araujo added the comment:
python.org is not specific to CPython, but I agree with Antoine that
docs.python.org/devguide is. So I went and found the blog post that Frank
alludes to in the OP is here:
http://fwierzbicki.blogspot.com/2011/11/contributing-to-jython.html
Nick proposed
Éric Araujo added the comment:
Thanks, I’ll fix this.
--
assignee: docs@python -> eric.araujo
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issu
Éric Araujo added the comment:
I guess you’re suggesting adding a mention of -m in the section near the top
that says that a script file and code passed to -c are blocks? Makes sense.
The same commit could also improve the markup to link to the description of
script, -c and -m in using
Changes by Éric Araujo :
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue13477>
___
___
Python-bugs-list mailing list
Unsubscribe:
Éric Araujo added the comment:
__import__ and importlib in Python 3.3 already use repr (see c4361bab6914 and
9f9b7b656761):
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named 'string\n'
For other stdlib modules, see #87
Éric Araujo added the comment:
I read this report again a few days ago and saw you were right, so I fixed it.
Thanks!
(The peps repo is not hooked up to close bugs, because we don’t usually use the
bug tracker to discuss PEPs (we use mailing lists). The PEPs pages (not docs!
:) on
Éric Araujo added the comment:
Okay, I think it’s a valuable use case.
(Out of curiosity, why don’t you want byte-compiled files on your system? It
speeds up imports, and problems due to the presence of stray pyc files when the
py is deleted are gone in 3.2+. Maybe you have custom tools to
Changes by Éric Araujo :
Removed file: http://bugs.python.org/file23778/ref_shlex.py
___
Python tracker
<http://bugs.python.org/issue1521950>
___
___
Python-bugs-list m
Changes by Éric Araujo :
Removed file: http://bugs.python.org/file23779/test_shlex.diff
___
Python tracker
<http://bugs.python.org/issue1521950>
___
___
Python-bugs-list m
Éric Araujo added the comment:
Thanks for the diff and test. (I removed the older versions; there are “edit”
links in the list of files leading to pages where it’s possible to remove them,
if one has the required permissions.)
Your script passes with dash, which is probably the most POSIX
Éric Araujo added the comment:
> if a line ends with ";;", _pop_values() will call interpret() with an empty
> string. [...]
> it just means interpret() would return False, causing the line to be ignored,
> which is probably
> fine for that border case
Hm, I
Éric Araujo added the comment:
> I have a few arguments in favor of my position:
Hm, I said that people wanted a “feature-full library” but I was confused:
We’re talking about a Python built for contributing, not to develop your app,
so my argument does not apply. So, the devguide sho
Éric Araujo added the comment:
Latest patch looks good.
Looking at the examples with ';;' or even '--', I think that their role is
non-obvious. Even though the PEP and docs explained them, there is value in
using intuitive (“guessable”) markup. So if the constrain
Éric Araujo added the comment:
> I was just looking for a reference where I didn't have to sift through tons
> of documentation.
Sure :) That’s why I suggest using dash for quick tests and rely on the work
of other people who did read the POSIX spec. I’ll have to check it
Éric Araujo added the comment:
Please report troubles to the listmasters listed on the bottom of each mailing
list’s description page. Thanks.
--
components: -None
nosy: +eric.araujo
resolution: -> invalid
stage: -> committed/rejected
status: open -&g
Éric Araujo added the comment:
See http://bugs.python.org/issue12119#msg146943
--
___
Python tracker
<http://bugs.python.org/issue13473>
___
___
Python-bug
Éric Araujo added the comment:
> I suggest to not use "pyc" and "pyo" in options, because ".pyc" and ".pyo"
> filename extensions
> are specific to a subset of Python implementations. Jython uses "$py.class"
> filename extens
Changes by Éric Araujo :
--
nosy: +mhammond
___
Python tracker
<http://bugs.python.org/issue13486>
___
___
Python-bugs-list mailing list
Unsubscribe:
Éric Araujo added the comment:
> I have attached an updated patch with a unit test.
LGTM.
> Also, this is not an issue for Python 2.7. The 2.7 implementation assumes any
> directories mentioned in the path already exist.
Cool. The test can still be committed in that b
Éric Araujo added the comment:
1b7fed04108c should help make figure out that it needs to rebuild.
--
___
Python tracker
<http://bugs.python.org/issue12
Éric Araujo added the comment:
Rebuilt! (Another glitch: plain text PEPs really should have an HTML title.
If you have time.. :)
--
___
Python tracker
<http://bugs.python.org/issue12
Éric Araujo added the comment:
Is subprocess affected by PYTHONIOENCODING?
--
___
Python tracker
<http://bugs.python.org/issue6135>
___
___
Python-bugs-list m
Éric Araujo added the comment:
Can I removed the shebangs in the 3.3 stdlib or do I need to go through with
the PEP 8 patch on python-dev first?
--
versions: -Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/issue10
Éric Araujo added the comment:
It is very helpful that you review the docs. Some obvious fixes were made when
moving to Python 3 (print, etc.) but apparently the examples were not run.
Sphinx can let us run the code blocks in reST files as doctests, but it is
currently not done because the
Éric Araujo added the comment:
Maybe it can be caused by an installation happening during the loop. I agree
with Erik’s reading of the comment and patch, and don’t think a test is needed.
--
nosy: +eric.araujo
stage: -> patch review
type: -> behavior
versions: -Pyth
Changes by Éric Araujo :
--
components: -None
stage: -> test needed
title: using python embed on AIX 6.1,Modules import error! -> Import error with
embedded python on AIX 6.1
type: crash -> behavior
versions: +Python 2.7 -Python 2.6
_
Éric Araujo added the comment:
A tip to make Mercurial download only a subset of all the changesets in the
repo:
hg clone URI -r branch
or
hg clone URI#branch
(The difference is that in the second form, URI#branch will be recorded in the
.hg/hgrc file and subsequent pulls will only
Éric Araujo added the comment:
So the users can control the encoding, and this is a doc bug.
--
title: subprocess seems to use local 8-bit encoding and gives no choice ->
subprocess seems to use local encoding and give no choice
___
Python trac
Éric Araujo added the comment:
Thanks for the patch. It was reviewed on our code review tool; if you did not
get an email (there are glitches), follow the link on the right of your patch
in the list of files.
--
nosy: +eric.araujo
___
Python
Éric Araujo added the comment:
> Jython's *$py.class files are byte-compiled modules, not extension modules.
Thanks for the data point. Agreed distutils[2] should not say “pyc” and “pyo”
then.
> There should be a way to disable generation of *.pyo files on command line
> even
Éric Araujo added the comment:
> Please don't backport this change to distutils without backporting
> --no-compile options to
> "build" command in distutils (issue #13400).
The feature freeze on distutils rules this out.
> Otherwise users would lose possibility of
Éric Araujo added the comment:
Thanks for all the feedback! So, for anyone interested in contributing, two
patches are needed:
One that changes the existing options to use the new names and parsing behavior
(--no-compile, --compile[=0,1,2]) and adds tests for the erroneous
--compile=1,2
Éric Araujo added the comment:
.pyo files are used if sys.dont_write_bytecode is false and sys.flags.optimize
is >= 1 (IOW, true).
For Python 3.2 and 3.3, imp.cache_from_source should be used to get the right
paths (see PEP 3147).
Before you put more work into this, it would be nice to
Éric Araujo added the comment:
Thanks, I’ll adapt the code for older Pythons.
Bumped down, I won’t do this for d2 1.0a3.
--
priority: release blocker ->
___
Python tracker
<http://bugs.python.org/issu
Éric Araujo added the comment:
Is memory footprint something important enough to put in the doc? Ease of use
is IMO more important, but then it becomes subjective..
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue11
Éric Araujo added the comment:
Patch looks good to me. Ezio, do you have time to review too?
(I had forgotten that there were tests checking the exact HTML output. This
won’t be fun when we overhaul pydoc to make it generate sensible HTML.)
--
nosy: +eric.araujo
stage: test needed
Changes by Éric Araujo :
Removed file: http://bugs.python.org/file14760/unnamed
___
Python tracker
<http://bugs.python.org/issue6753>
___
___
Python-bugs-list mailin
Changes by Éric Araujo :
--
versions: +Python 2.7, Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/issue6899>
___
___
Python-bugs-list mailin
Éric Araujo added the comment:
More info on this thread:
http://mail.python.org/pipermail/python-dev/2006-December/070237.html
--
___
Python tracker
<http://bugs.python.org/issue9
Éric Araujo added the comment:
I did not found all these Google hist. Most of the links on the first page for
“link libpython” are bug reports which are rejected by maintainers. Related:
http://mail.python.org/pipermail/python-dev/2006-February/060549.html
So, what do people link with
Changes by Éric Araujo :
--
assignee: -> ezio.melotti
stage: test needed -> patch review
___
Python tracker
<http://bugs.python.org/issue12759>
___
___
Pyth
601 - 700 of 7440 matches
Mail list logo
