Phil Thompson added the comment:
Is this likely to be fixed for v3.10? At the very least a wheel should have the
correct platform tag.
--
___
Python tracker
<https://bugs.python.org/issue44
Phil Thompson added the comment:
Another aspect of this is when building a Python v3.10 C extension on macOS
v10.15 (Catalina) with SDK 10.15, the wheel has the 'universal2' platform tag
when it actually only contains an x86_64 implementation
New submission from Phil Thompson :
I am running macOS v11 (Big Sur) and using Xcode v12.1 (because this is the
latest that includes SDK v10.15 rather than v11) to build a C extension. I'm
using the older SDK because of 3rd party libraries that are not tested against
the newer SDK
Change by Will Thompson :
--
nosy: -Will Thompson
___
Python tracker
<https://bugs.python.org/issue29708>
___
___
Python-bugs-list mailing list
Unsubscribe:
Henry S. Thompson added the comment:
[One year and 2 days later... :-[
Is this fixed in 3.9? If not, the Versions list above should be updated.
The failure of lower() to preserve 'alpha-ness' is a serious bug, it causes
significant failures in e.g. Turkish NLP, and it's _not_ just
Michael Thompson added the comment:
Thanks. I found 3.6 works for me.
--Mike
On Tue, Dec 10, 2019 at 5:10 PM Mark Dickinson
wrote:
>
> Mark Dickinson added the comment:
>
> I think this was already fixed in 3.5, but the fix would have gone in
> later than the 3.5.2 rel
New submission from Michael Thompson :
Version 3.5.2, the "rand string seed" is not deterministic in code sample below
across multiple invocations of the program. Python 3.6.8 works fine.
#!/usr/bin/env python3
import random
lis = '94'
random.seed(lis, version=1)
w = random.rand
Phil Thompson added the comment:
>> Which is why I protect the initialisation with #if PY_VERSION_HEX <
> 0x0309
>
> It is your specific case. We can not assume people do it, or even you
> never forget it. So this is not the "right thing" we can recommen
Phil Thompson added the comment:
On 19/07/2019 11:37, Jeroen Demeyer wrote:
> Jeroen Demeyer added the comment:
>
>> We have some reserved/deprecated/unused fields. Setting 0 to them
>> makes forward incompatible code.
>
> Good point. tp_print is removed in 3.9
Phil Thompson added the comment:
I am not "touching" tp_print. I am simply defining it as 0 to avoid the missing
initialiser warning. My point is that it should be possible to write code that
doesn't trigger warnings (whether or not you sup
New submission from Phil Thompson :
I have a number of static PyTypeObject declarations. In order to avoid compiler
warnings about missing field initialisers I always provide explicit 0 values
for unused fields (protected by #if PY_HEX_VERSION >= ...). However with v3.8b2
this triggers
Phil Thompson added the comment:
A clarification...
It seems the suffix is added when configured as VC-WIN64A but omitted when
configured as VC-WIN64A-masm.
...still not a Python problem.
--
___
Python tracker
<https://bugs.python.
Phil Thompson added the comment:
I think I was incorrect in saying the suffix was the default when building
v1.1.1 from source, so any problem I have (trying to share the DLL with
different pre-built packages) is not a Python problem. Sorry for the noise.
--
resolution
New submission from Phil Thompson :
In the 3.8b1 64-bit Windows installer the names of the OpenSSL DLLs do not have
the -x64 suffix which seems to be the convention (and is the default when
building OpenSSL from source). The convention is followed in the 3.7.0 to 3.7.3
installers. I haven't
Henry S. Thompson added the comment:
This issue is also implicated in a failure of isalpha and friends.
Easy way to see this is to compare
>>> isalpha('İ')
True
>>> isalpha('İ'.lower())
False
This results from the use of a combining character to encode lower-case Turkish
do
Mike Thompson added the comment:
I am a teacher, and this feature would really help me teach Python to my
students. Especially when I am teaching the course remotely.
--
nosy: +mthompsonwhs
___
Python tracker
<https://bugs.python.org/issue17
Will Thompson <thomp...@endlessm.com> added the comment:
For what it's worth, in Endless OS we still saw slight variations between
builds in the .pyc files, even with all the source files' mtimes set to the
epoch (ie. equivalent to setting & supporting SOURCE_DATE_EPOCH, I believe)
New submission from Phil Thompson <p...@riverbankcomputing.com>:
When configure searches for a C compiler on macOS it fails to handle spaces in
directory name on PATH. The fix is to enclose $as_dir in quotes.
--
components: Build
messages: 307004
nosy: philthompson10
priority:
Luther Thompson <luther...@gmail.com> added the comment:
Thanks, done: https://github.com/pypa/python-packaging-user-guide/issues/397
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
New submission from Luther Thompson <luther...@gmail.com>:
I wrote my own distribution package with only one module, but the module file
was not being installed along with the dist info file. I found by looking up
the code for the `six` module that `setup` has a `py_modules` parameter
New submission from Phil Thompson:
posixmodule.c needs to #include to get the declaration of ctermid().
On most platforms this happens as a side effect of including other .h files but
does not on Android.
--
components: Library (Lib)
messages: 266561
nosy: philthompson10
priority
Phil Thompson added the comment:
At the moment my importer does the same as zipimport and gets added to
sys.path_hooks rather than sys.meta_path.
While waiting for the PEP, how about a table of (externally modifiable)
importer installers that is worked through where _PyImportZip_Init
Phil Thompson added the comment:
Understood, but the only promise here is to call a function (with no arguments,
and returning no result).
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Phil Thompson added the comment:
I don't see why it would be hard to test. The change suggested wouldn't alter
the default behaviour at all.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Phil Thompson added the comment:
Yes, preventing the filesystem being used for imports would be another way of
expressing the issue.
Regarding the title I specifically didn't want to suggest a solution as I'm not
expert enough to know what the best solution might be.
If, as Paul implies
Phil Thompson added the comment:
The problem is the import of the encodings module in _PyCodecRegistry_Init().
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Phil Thompson:
The use case is a packaging tool that can create a single executable for a
Python application. Like similar tools it embeds frozen Python code (including
the standard library) and is linked (often statically) against the interpreter
library.
Executables
New submission from Andrew Thompson draft1...@gmail.com:
I could not get Python3 to build on my OSX 10.6.8 box as per the instructions
on the website (or those in the README). It configures , but does not make
:
snip
IOError: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.4 but 10.5 during
Changes by Andrew Thompson draft1...@gmail.com:
--
assignee: - ronaldoussoren
components: +Macintosh
nosy: +ronaldoussoren
type: - compile error
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14602
New submission from Phil Thompson p...@riverbankcomputing.com:
The old unaccelerated ETree XMLParser accepts input from a io.StringIO, but the
accelerated version does not. Any code that relies on this is broken by Python
v3.3.
--
components: XML
messages: 155301
nosy: philthompson10
Phil Thompson p...@riverbankcomputing.com added the comment:
This variation of your test doesn't...
---
import io
from xml.etree.ElementTree import parse
stream = io.StringIO()
stream.write('''?xml version=1.0?
site
/site
''')
stream.seek(0)
parsed
New submission from Steve Thompson steve.f.thomp...@gmail.com:
Consider the following:
import ctypes
class struct1( ctypes.Structure ):
_pack_ = 1
_fields_ = [
( first, ctypes.c_uint8, 1 ),
( second, ctypes.c_uint8, 1
Steve Thompson steve.f.thomp...@gmail.com added the comment:
So, knowing there's a potential cross platform inconsistency here, is there
a proposed way to deal with this that doesn't involve modifying the real c
code I'm interfacing with? That's not always an option.
On Mon, Apr 25, 2011 at 2
New submission from Steve Thompson steve.f.thomp...@gmail.com:
Consider the following:
python code:
class my_array( ctypes.Array ):
_type_= ctypes.c_uint8
_length_ = 256
class my_array2( my_array ):
pass
Output:
class my_array2( my_array ):
AttributeError: class must define
New submission from Phil Thompson p...@riverbankcomputing.com:
In Python v3.2b1 the type of the first argument of PySlice_GetIndices() and
PySlice_GetIndicesEx() has changed from PySliceObject* to PyObject*.
The documentation does not reflect this change.
Which is correct, the source code
Phil Thompson p...@riverbankcomputing.com added the comment:
You might want to add a Changed in Python v3.2 because as it is an
incompatible change.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10681
Phil Thompson p...@riverbankcomputing.com added the comment:
It's source level incompatible - my extension modules compiled fine with v3.2a
but failed with v3.2b1.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10681
New submission from Steve Thompson steve.f.thomp...@gmail.com:
I'm running pythong 2.6.1 on Windows XP SP3.
On many occasions I have ran into cases where I've installed a new package via
the package's setup.py (pylint, logilab-common, etc) and new .pyc files don't
get generated when I attempt
Steve Thompson steve.f.thomp...@gmail.com added the comment:
Setup.py install. We've also seen this happen when checking our python
files out of our version control system. Also seen a .pyc get used when the
.py no longer exists, but I could see that being intentional behavior.
On Sep 3, 2010
Steve Thompson steve.f.thomp...@gmail.com added the comment:
Hmmm... this definitely sounds like the issue for version controlled files,
but does not explain the issue when installing packages from source.
On Sep 3, 2010 3:16 PM, Amaury Forgeot dapos;Arc rep...@bugs.python.org
wrote:
Amaury
Steve Thompson steve.f.thomp...@gmail.com added the comment:
So what's the current status of this on Windows Platforms?
--
nosy: +Steve.Thompson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6074
Steve Thompson steve.f.thomp...@gmail.com added the comment:
Any idea if this will be fixed (at all) and/or back ported to 2.6.x or
2.7.x?
On Fri, Sep 3, 2010 at 3:36 PM, Amaury Forgeot d'Arc rep...@bugs.python.org
wrote:
Amaury Forgeot d'Arc amaur...@gmail.com added the comment
Phil Thompson p...@riverbankcomputing.com added the comment:
Yes I can update the patch, but it might be a while before I get the time.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1337876
43 matches
Mail list logo
