[issue30159] gdb autoloading python-gdb.py

[Дилян Палаузов]

Changes by Дилян Палаузов :


--
components: +Build

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30159] gdb autoloading python-gdb.py

[Дилян Палаузов]

Дилян Палаузов added the comment:

This is what I mean.  I asked at 
https://sourceware.org/bugzilla/show_bug.cgi?id=21465 how configure.ac is 
supposed to be tweaked.

diff --git a/Makefile.pre.in b/Makefile.pre.in
--- a/Makefile.pre.in
+++ b/Makefile.pre.in
@@ -1093,6 +1093,8 @@ $(DESTSHARED):
 
 # Install the interpreter with $(VERSION) affixed
 # This goes into $(exec_prefix)
+datadir=@datadir@
+GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=@GDB_AUTO_LOAD_SCRIPTS_DIRECTORY@
 altbininstall: $(BUILDPYTHON) @FRAMEWORKPYTHONW@
@for i in $(BINDIR) $(LIBDIR); \
do \
@@ -1118,6 +1120,11 @@ altbininstall: $(BUILDPYTHON) @FRAMEWORKPYTHONW@
$(INSTALL_SHARED) $(DLLLIBRARY) $(DESTDIR)$(BINDIR); \
else \
$(INSTALL_SHARED) $(LDLIBRARY) 
$(DESTDIR)$(LIBDIR)/$(INSTSONAME); \
+   if test ! -d 
$(DESTDIR)$(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY); then \
+   echo "Creating directory 
$(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY)"; \
+   $(INSTALL) -d -m $(DIRMODE) 
$(DESTDIR)$(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY)/$(LIBDIR); \
+   fi; \
+   $(INSTALL_SCRIPT) Tools/gdb/libpython.py 
$(DESTDIR)$(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY)/$(LIBDIR)/$(INSTSONAME)-gdb.py; \
if test $(LDLIBRARY) != $(INSTSONAME); then \
(cd $(DESTDIR)$(LIBDIR); $(LN) -sf 
$(INSTSONAME) $(LDLIBRARY)) \
fi \
diff --git a/configure.ac b/configure.ac
--- a/configure.ac
+++ b/configure.ac
@@ -5422,6 +5422,14 @@ if test "$have_getrandom" = yes; then
   [Define to 1 if the getrandom() function is available])
 fi
 
+AC_CHECK_PROG(gdb, gdb, found)
+if test $gdb = found; then
+  GDB_AUTO_LOAD_SCRIPTS_DIRECTORY=$(gdb -q -ex "show data-directory" -ex "show 
auto-load scripts-directory" -ex quit |sed "1d;2{N;s/\n//g; 
s/.*\"\(.*\)\".*:\(.*\)./\1 \2/}; /\$datadir/ {s/\(.*\) 
\$datadir\(.*\)/\1\2/;q}; s/.* \(.\)/\1/")
+else
+  GDB_AUTO_LOAD_SCRIPTS_DIRECTORY='${datadir}/gdb/auto-load'
+fi
+AC_SUBST(GDB_AUTO_LOAD_SCRIPTS_DIRECTORY)
+
 # generate output files
 AC_CONFIG_FILES(Makefile.pre Modules/Setup.config Misc/python.pc 
Misc/python-config.sh)
 AC_CONFIG_FILES([Modules/ld_so_aix], [chmod +x Modules/ld_so_aix])

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28087] macOS 12 poll syscall returns prematurely

[Gregory P. Smith]

Gregory P. Smith added the comment:

Do we need to work around this issue at all?

Apple appears to have fixed it already:
  
https://github.com/opensource-apple/xnu/commit/0cccba1c831cfe36f0d67d672f8aa67b4a7d4b6a#diff-e61c2932bb9d5cea2dd0732acd8ec626R1783

A comment in https://github.com/curl/curl/issues/1057 suggests Apple has 
shipped that change in 10.12.2.

If you still want to have Python deal with the 10.12.0 and 10.12.1 cases you 
could update your PR to check those versions, but given these are security fix 
releases as 10.12.4 is already current I think it is better to tell people just 
to apply their security updates and not bother with a workaround in Python.

--
versions: +Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26700] Make digest_size a class variable

[Gregory P. Smith]

Gregory P. Smith added the comment:

I'm rejecting this one as low value / infeasible.

--
assignee: gregory.p.smith -> 
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6931] dreadful performance in difflib: ndiff and HtmlDiff

[Gregory P. Smith]

Changes by Gregory P. Smith :


--
nosy:  -gregory.p.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6931] dreadful performance in difflib: ndiff and HtmlDiff

[Gregory P. Smith]

Changes by Gregory P. Smith :


--
assignee: gregory.p.smith -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30285] Optimize case-insensitive regular expressions

[Raymond Hettinger]

Raymond Hettinger added the comment:

This seems like a great idea.

--
nosy: +rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30195] writing non-ascii characters in xml file using python code embedded in C

[mahboubi]

Changes by mahboubi :


--
type: crash -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30267] Deprecate os.path.commonprefix

[Raymond Hettinger]

Raymond Hettinger added the comment:

The ``os.path.commonprefix`` function has been around for a very long time.  
Deprecating it will just cause unnecessary pain for users and make it harder to 
upgrade to Python 3.  The function isn't broken, the only issue here is that a 
new function was added with a similar name.

--
nosy: +rhettinger
priority: normal -> low

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30293] Peephole binops folding can lead to memory and bytecache ballooning

[Raymond Hettinger]

Raymond Hettinger added the comment:

A few thoughts:

* This is very unlikely to come up in real code. Accordingly, I've marked this 
a low priority -- the peepholer is over a decade old and seems to work-out fine 
in actual practice.

* The user explicitly asked for 1 << 5 to be computed.  At some point, 
either during compilation or during execution, a large object is going to be 
produced.

* The binops folding in peephole.c was originally much simpler and did not 
recursively combine results.  The patch that added the recursive application of 
constant folding added a lot of complexity, but it demonstrated very little 
real world benefit, and it opened the door to examples like this where the 
computer is being explicitly told to do a lot of work.  Perhaps constant 
folding should be reverted to its simpler state.

* We could do a size check after each folding step and abandon folding when the 
size hit some limit.  I'm not sure that is worth it though.  Someone can just 
add more zeros and then complain that the compilation step took a lot of time 
and memory without producing any benefit.

* We could try to detect an expensive computation before it is run, but in 
general that is hard to do right and it adds yet more complexity to something 
that started-out simple.

* One of the design objectives for the peephole transformations was to keep it 
fast and slim rather than trying to be all things to all people.  Burdening the 
optimizer with insanity checks just slows down the compilation of normal, sane 
code.

* With sum(), Guido and Alex took the position that users should be blocked 
from using it with list-of-strings, but we didn't do block other unfavorable 
possibilities like a list-of-lists.  The rationale was that the list-of-strings 
was too tempting and likely but that other cases weren't common or easy to 
detect.  Likewise for Tim and I, the early decision for the peephole optimized 
(the decision being second guessed by this issue) was that large strings were 
easy to detect and likely enough to warrant extra code but that numeric folding 
issues were much less likely and didn't warrant extra code. 

* Constant folding was introduced before the AST branch.  Once that branch 
landed, it has been a long standing objective to move constant folding out of 
the peepholer and into the AST stage.  Accordingly, we've tried to refrain from 
further build-outs of constant folding.  It is a pit of snakes.  If someone 
really cares about this, they should work on an AST transformation.

* Programming languages are different from applications.  Users are allowed to 
explicitly create code that tells the computer to do something resource 
intensive and there are a myriad of ways to do so. In general, it will be 
difficult to prevent the execution of such code without unduly burdening 
execution of normal code.

--
nosy: +rhettinger
priority: normal -> low
type:  -> resource usage
versions: +Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30291] Allow windows launcher to specify bit lengths with & without minor version

[Zachary Ware]

Changes by Zachary Ware :


--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.7 -Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 
3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24459] Mention PYTHONFAULTHANDLER in the man page

[Joshua Jay Herman]

Joshua Jay Herman added the comment:

Ping

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30262] Don't expose sqlite3 Cache and Statement

[R. David Murray]

R. David Murray added the comment:

They are not part of the API, that is why they are not documented.  The 
convention of "always" using _ prefixed names for non-API stuff is (relatively) 
recent.  It used to be we just didn't document the non-API stuff.

Your second argument is a good motivation.  Let's see what others think.

I thought the deprecation process was documented in a PEP, but I can't find it. 
 Basically, we introduce a deprecation warning (and a document the deprecation, 
but that isn't needed here) in the next release, and then the release after 
that we actually do the removal.  Or in many cases we don't do the removal at 
all, we just leave the deprecation warning in place until 2.7 is out of 
maintenance (but I don't think we need to worry about that in this case).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28087] macOS 12 poll syscall returns prematurely

[Gregory P. Smith]

Gregory P. Smith added the comment:

The only thing CPython should do is apply workarounds to any standard library 
internal uses of poll with 0 fds guarded by a MacOS platform check.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue28087] macOS 12 poll syscall returns prematurely

[Gregory P. Smith]

Gregory P. Smith added the comment:

Please DO NOT REMOVE select.poll() on MacOS.  It is still useful.

Apple needs to live with their bug that they refuse to acknowledge by forcing 
developers to learn the special case that it now breaks in (0 fds).  We should 
not pretend that poll() does not exist as a result.

For reference about the details of the MacOS change they were stupid enough to 
force upon the world, see this comment - which links to the source of their bug 
in the "open" source side of their OS.
  https://github.com/curl/curl/issues/1057#issuecomment-252286017

--
nosy: +gregory.p.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30293] Peephole binops folding can lead to memory and bytecache ballooning

[Martijn Pieters]

New submission from Martijn Pieters:

The following expression produces 127MB in constants in `co_consts` due to two 
63.5MB integer objects produced when folding:

((200*200 - 2) & ((1 << 5) - 1)) + ((200*200 - 2) >> 5)

The optimizer already does not store optimized *sequences* of more than 20 
elements to avoid making bytecode files too large:

   If the new constant is a sequence, only folds when the size
   is below a threshold value.  That keeps pyc files from
   becoming large in the presence of code like:  (None,)*1000.

Perhaps the same should be extended to number objects?

Context: 
https://stackoverflow.com/questions/43823807/why-does-using-arguments-make-this-function-so-much-slower

--
messages: 293167
nosy: mjpieters
priority: normal
severity: normal
status: open
title: Peephole binops folding can lead to memory and bytecache ballooning

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30262] Don't expose sqlite3 Cache and Statement

[Aviv Palivoda]

Aviv Palivoda added the comment:

I have 3 argument for the motivation for this change:
1. Cleaner API - Both objects are internal implementation details. I think that 
we can look on exposing them as a bug.
2. Easier development - When you remove these objects from the API you can 
change them without any concern. I for one think that I can make the sqlite3 
module faster by changing them from Python objects to simple C structs.
3. Documentation - Currently both objects are part of the API. Thus they should 
be documented but how would you document the Statement class? Do we really want 
to have a generic Cache class in the sqlite3 module?

I have less experience with cpython then you. Do you think that maybe the Cache 
class should be moved to more appropriate place (maybe collections) and be used 
by others?

> At a minimum there would need to be a deprecation period, 

Is there a place that document the deprecation process? I will update the patch.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30220] Why are custom messages for ValueError, TypeError suppressed in argparse?

[paul j3]

paul j3 added the comment:

I didn't mean to question the use of value tests in the 'type' callable.  The 
ArgumentTypeError example in the documentation does that kind of test.

Argparse is using the term 'type' loosely.  It just means any kind of 
conversion and/or test that can be applied to a string.

I doubt if _get_value() ever traps a TypeError.  That error complains about the 
type of the input argument. As in, for example 'int([])'.  But 'int(astring)' 
only produces a ValueError.  If the callable issues a TypeError when given a 
string, it shouldn't be used as a 'type' parameter.

If your prewritten test produces a ValueError, and you don't like the 
standardization, you can just wrap it in simple function reraises the 'custom' 
message as an ArgumentTypeError.  There's no other way of identifying a 
'custom' message.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12077] Harmonizing descriptor protocol documentation

[Raymond Hettinger]

Raymond Hettinger added the comment:

I will have a chance to work on this before long.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25435] Wrong function calls and referring to not removed concepts in descriptor HowTo (documentation)

[Raymond Hettinger]

Raymond Hettinger added the comment:

I will have a chance to work on this before long.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12870] Regex object should have introspection methods

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
status: open -> pending

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25435] Wrong function calls and referring to not removed concepts in descriptor HowTo (documentation)

[Mariatta Wijaya]

Changes by Mariatta Wijaya :


--
versions: +Python 3.7 -Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25435] Wrong function calls and referring to not removed concepts in descriptor HowTo (documentation)

[Martin Panter]

Martin Panter added the comment:

Raymond I suggest you unassign this and let others work on it.

--
stage: patch review -> needs patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30292] Why is there a concept "unbound method" in python3 version?

[Martin Panter]

Changes by Martin Panter :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> docs.python.org/3/howto/descriptor.html still refers to 
"unbound methods"

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12077] Harmonizing descriptor protocol documentation

[Martin Panter]

Martin Panter added the comment:

See Issue 23702 specifically about unbound methods in Python 3, and Issue 25435 
about general problems with the how-to in Python 3.

--
nosy: +martin.panter

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30292] Why is there a concept "unbound method" in python3 version?

[debuggy]

New submission from debuggy:

When I read  (python 3.6.1 version), I found there is a 
concept of 'unbound method' in some places. However, when I referred to , it said the concept of “unbound methods” has been removed 
from the language.

So I wondered if there should be a change in  python3 
version?

For instance, in this code example of the guide:

>>> class D(object):
... def f(self, x):
... return x
...
>>> d = D()
>>> D.__dict__['f']  # Stored internally as a function

>>> D.f  # Get from a class becomes an unbound method
 
>>> d.f  # Get from an instance becomes a bound method
>

When I tested myself, the result of statement "D.f" should be  not 
.

--
assignee: docs@python
components: Documentation
messages: 293160
nosy: debuggy, docs@python
priority: normal
severity: normal
status: open
title: Why is there a concept "unbound method" in  
python3 version?
type: enhancement
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29094] Regression in zipfile writing in 2.7.13

[Serhiy Storchaka]

Serhiy Storchaka added the comment:


New changeset c8faabce6ef318f3b425c6defd846e274d61e2ef by Serhiy Storchaka in 
branch '3.5':
[3.5] Revert bpo-26293 for zipfile breakage. See also bpo-29094. (GH-1484). 
(#1486)
https://github.com/python/cpython/commit/c8faabce6ef318f3b425c6defd846e274d61e2ef


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26293] Embedded zipfile fields dependent on absolute position

[Serhiy Storchaka]

Serhiy Storchaka added the comment:


New changeset c8faabce6ef318f3b425c6defd846e274d61e2ef by Serhiy Storchaka in 
branch '3.5':
[3.5] Revert bpo-26293 for zipfile breakage. See also bpo-29094. (GH-1484). 
(#1486)
https://github.com/python/cpython/commit/c8faabce6ef318f3b425c6defd846e274d61e2ef


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29094] Regression in zipfile writing in 2.7.13

[Serhiy Storchaka]

Serhiy Storchaka added the comment:


New changeset 70dc6a7a0b7f104d87512556fca242c2ca96a010 by Serhiy Storchaka in 
branch '3.6':
[3.6] Revert bpo-26293 for zipfile breakage. See also bpo-29094. (GH-1484). 
(#1485)
https://github.com/python/cpython/commit/70dc6a7a0b7f104d87512556fca242c2ca96a010


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26293] Embedded zipfile fields dependent on absolute position

[Serhiy Storchaka]

Serhiy Storchaka added the comment:


New changeset 70dc6a7a0b7f104d87512556fca242c2ca96a010 by Serhiy Storchaka in 
branch '3.6':
[3.6] Revert bpo-26293 for zipfile breakage. See also bpo-29094. (GH-1484). 
(#1485)
https://github.com/python/cpython/commit/70dc6a7a0b7f104d87512556fca242c2ca96a010


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26293] Embedded zipfile fields dependent on absolute position

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +1588

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29094] Regression in zipfile writing in 2.7.13

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +1589

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26293] Embedded zipfile fields dependent on absolute position

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +1586

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29094] Regression in zipfile writing in 2.7.13

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +1587

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26293] Embedded zipfile fields dependent on absolute position

[Serhiy Storchaka]

Serhiy Storchaka added the comment:


New changeset 3763ea865cee5bbabcce11cd577811135e0fc747 by Serhiy Storchaka in 
branch 'master':
Revert bpo-26293 for zipfile breakage. See also bpo-29094. (#1484)
https://github.com/python/cpython/commit/3763ea865cee5bbabcce11cd577811135e0fc747


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29094] Regression in zipfile writing in 2.7.13

[Serhiy Storchaka]

Serhiy Storchaka added the comment:


New changeset 3763ea865cee5bbabcce11cd577811135e0fc747 by Serhiy Storchaka in 
branch 'master':
Revert bpo-26293 for zipfile breakage. See also bpo-29094. (#1484)
https://github.com/python/cpython/commit/3763ea865cee5bbabcce11cd577811135e0fc747


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29094] Regression in zipfile writing in 2.7.13

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +1585

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26293] Embedded zipfile fields dependent on absolute position

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +1584

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30291] Allow windows launcher to specify bit lengths with & without minor version

[Steve Barnes]

New submission from Steve Barnes:

Currently you can use, assuming all are installed:

py -2 # gets the latest python 2 with 64 bit as the default
py -2.7 # gets python 2.7 with 64 bit as the default
py -2.7-32 # gets -32 bit python 2.7
py -3 # gets the latest python 3 with 64 bit as the default
py -3.5 # gets python 3.5 with 64 bit as the default
py -3.5-32 # gets -32 bit python 3.5

But you cannot use:

py -2-32 # Usage Error but would be handy for the latest 32 bit python 2
py -3-32 # Usage Error but would be handy for the latest 32 bit python 3

Note that you also cannot use:
py -3.5-64  # Unknown option: -3 would be handy for testing with I need 64 bit 
python 3.5 with an error if it doesn't exist currently -3.5 defaults to 3.5 64 
bit if available 32 bit otherwise.

For testing packages and programs it would be very useful to be able to specify 
any of:

 - Latest available 32 bit python 2 or 3
 - 64 bit python 3 fail if unavailable.

--
messages: 293153
nosy: Steve Barnes
priority: normal
severity: normal
status: open
title: Allow windows launcher to specify bit lengths with & without minor 
version
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com