Re: [Python-Dev] Wordcode: new regular bytecode using 16-bit units
Oh nice. Did you see my recent "bytecode" project? http://bytecode.readthedocs.io/ Victor Le 5 mai 2016 8:30 PM, a écrit : > Here is something I wrote because I was also unsatisfied with byteplay's > API: https://github.com/zachariahreed/byteasm. Maybe it's useful in a > discussion of "minimum viable" api for bytecode manipulation. > > > > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Anyone want to lead the sprints at PyCon US 2016?
On 6 May 2016, at 14:38, Brett Cannon wrote: On Fri, 6 May 2016 at 14:14 Camilla wrote: I was thinking about holding a Patch Review Party/Sprint, which would provide people unfamiliar with the Python dev process a way to contribute to the project and get familiar with running tests, applying patches and so forth. I have a list of easy-ish patches that I wanted to take a look at and I could expand that and use those as a starting for people who don't have any particular bug tracker issues in mind. I'm not a patch review guru by any means, though. Also not sure if this is a good idea or if this is just late night caffeine talking. I have absolutely no problem if you want to pitch this idea to new contributors who show up at the sprints! -Brett Camilla, I would be happy to support your effort. I find it a wonderful idea! Carol Carol Willing Research Software Engineer, Project Jupyter @ Cal Poly Director, Python Software Foundation 2016-04-28 20:07 GMT+01:00 Brett Cannon : No one stepped forward to lead the sprints this year, so I will put myself as the sprint leader and lean on everyone else who appears to help. :) On Tue, 5 Apr 2016 at 09:36 Brett Cannon wrote: The call has started to go out for sprint groups to list themselves online. Anyone want to specifically lead the core sprint this year? If no one specifically does then I will sign us up and do my usual thing of pointing people at the devguide and encourage people to ask questions but not do a lot of hand-holding (I'm expecting to be busy either working on GitHub migration stuff or doing other things that I have been neglecting due to my GitHub migration work). -- Forwarded message - From: Ewa Jodlowska Date: Mon, 4 Apr 2016 at 07:14 Subject: [PSF-Community] Sprinting at PyCon US 2016 To: Are you coming to PyCon US? Have you thought about sprinting? The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) of coding with many Python projects and their maintainers. And if you're coming to PyCon, taking part in the Sprints is easy! You don’t need to change your registration* to join the Sprints. There’s no additional registration fee, and you even get lunch. You do need to cover the additional lodging and other meals, but that’s it. If you’ve booked a room through the PyCon registration system, you'll need to contact the registration team at pycon2...@cteusa.com as soon as possible to request the extra nights. The sprinting itself (along with lunch every day) is free, so your only expenses are your room and other meals. If you're interested in what projects will be sprinting, just keep an eye on the sprints page on the PyCon web site at https://us.pycon.org/2016/community/sprints/ Be sure to check back, as groups are being added all the time. If you haven't sprinted before, or if you just need to brush up on sprinting tools and techniques, there will again be an 'Intro to Sprinting' session the evening of June 1, lead by Shauna Gordon-McKeon and other members of Python community. To grab a free ticket for this session, just visit https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-tickets-22435151141 . *Please note that conference registration is sold out, but you do not need a conference registration to come to the Sprints. ___ PSF-Community mailing list psf-commun...@python.org https://mail.python.org/mailman/listinfo/psf-community ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/camillamon%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/willingc%40willingconsulting.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Anyone want to lead the sprints at PyCon US 2016?
On Fri, 6 May 2016 at 14:14 Camilla wrote: > I was thinking about holding a Patch Review Party/Sprint, which would > provide people unfamiliar with the Python dev process a way to contribute > to the project and get familiar with running tests, applying patches and so > forth. I have a list of easy-ish patches that I wanted to take a look at > and I could expand that and use those as a starting for people who don't > have any particular bug tracker issues in mind. > I'm not a patch review guru by any means, though. Also not sure if this is > a good idea or if this is just late night caffeine talking. > I have absolutely no problem if you want to pitch this idea to new contributors who show up at the sprints! -Brett > > > 2016-04-28 20:07 GMT+01:00 Brett Cannon : > >> No one stepped forward to lead the sprints this year, so I will put >> myself as the sprint leader and lean on everyone else who appears to help. >> :) >> >> >> On Tue, 5 Apr 2016 at 09:36 Brett Cannon wrote: >> >>> The call has started to go out for sprint groups to list themselves >>> online. Anyone want to specifically lead the core sprint this year? If no >>> one specifically does then I will sign us up and do my usual thing of >>> pointing people at the devguide and encourage people to ask questions but >>> not do a lot of hand-holding (I'm expecting to be busy either working on >>> GitHub migration stuff or doing other things that I have been neglecting >>> due to my GitHub migration work). >>> >>> -- Forwarded message - >>> From: Ewa Jodlowska >>> Date: Mon, 4 Apr 2016 at 07:14 >>> Subject: [PSF-Community] Sprinting at PyCon US 2016 >>> To: >>> >>> >>> Are you coming to PyCon US? Have you thought about sprinting? >>> >>> The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) >>> of coding with many Python projects and their maintainers. And if you're >>> coming to PyCon, taking part in the Sprints is easy! >>> >>> You don’t need to change your registration* to join the Sprints. There’s >>> no additional registration fee, and you even get lunch. You do need to >>> cover the additional lodging and other meals, but that’s it. If you’ve >>> booked a room through the PyCon registration system, you'll need to contact >>> the registration team at pycon2...@cteusa.com as soon as possible to >>> request the extra nights. The sprinting itself (along with lunch every day) >>> is free, so your only expenses are your room and other meals. >>> >>> If you're interested in what projects will be sprinting, just keep an >>> eye on the sprints page on the PyCon web site at >>> https://us.pycon.org/2016/community/sprints/ Be sure to check back, as >>> groups are being added all the time. >>> >>> If you haven't sprinted before, or if you just need to brush up on >>> sprinting tools and techniques, there will again be an 'Intro to Sprinting' >>> session the evening of June 1, lead by Shauna Gordon-McKeon and other >>> members of Python community. To grab a free ticket for this session, just >>> visit >>> https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-tickets-22435151141 >>> . >>> >>> *Please note that conference registration is sold out, but you do not >>> need a conference registration to come to the Sprints. >>> >>> ___ >>> PSF-Community mailing list >>> psf-commun...@python.org >>> https://mail.python.org/mailman/listinfo/psf-community >>> >> >> ___ >> Python-Dev mailing list >> Python-Dev@python.org >> https://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: >> https://mail.python.org/mailman/options/python-dev/camillamon%40gmail.com >> >> > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Anyone want to lead the sprints at PyCon US 2016?
I was thinking about holding a Patch Review Party/Sprint, which would provide people unfamiliar with the Python dev process a way to contribute to the project and get familiar with running tests, applying patches and so forth. I have a list of easy-ish patches that I wanted to take a look at and I could expand that and use those as a starting for people who don't have any particular bug tracker issues in mind. I'm not a patch review guru by any means, though. Also not sure if this is a good idea or if this is just late night caffeine talking. 2016-04-28 20:07 GMT+01:00 Brett Cannon : > No one stepped forward to lead the sprints this year, so I will put myself > as the sprint leader and lean on everyone else who appears to help. :) > > > On Tue, 5 Apr 2016 at 09:36 Brett Cannon wrote: > >> The call has started to go out for sprint groups to list themselves >> online. Anyone want to specifically lead the core sprint this year? If no >> one specifically does then I will sign us up and do my usual thing of >> pointing people at the devguide and encourage people to ask questions but >> not do a lot of hand-holding (I'm expecting to be busy either working on >> GitHub migration stuff or doing other things that I have been neglecting >> due to my GitHub migration work). >> >> -- Forwarded message - >> From: Ewa Jodlowska >> Date: Mon, 4 Apr 2016 at 07:14 >> Subject: [PSF-Community] Sprinting at PyCon US 2016 >> To: >> >> >> Are you coming to PyCon US? Have you thought about sprinting? >> >> The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) >> of coding with many Python projects and their maintainers. And if you're >> coming to PyCon, taking part in the Sprints is easy! >> >> You don’t need to change your registration* to join the Sprints. There’s >> no additional registration fee, and you even get lunch. You do need to >> cover the additional lodging and other meals, but that’s it. If you’ve >> booked a room through the PyCon registration system, you'll need to contact >> the registration team at pycon2...@cteusa.com as soon as possible to >> request the extra nights. The sprinting itself (along with lunch every day) >> is free, so your only expenses are your room and other meals. >> >> If you're interested in what projects will be sprinting, just keep an eye >> on the sprints page on the PyCon web site at >> https://us.pycon.org/2016/community/sprints/ Be sure to check back, as >> groups are being added all the time. >> >> If you haven't sprinted before, or if you just need to brush up on >> sprinting tools and techniques, there will again be an 'Intro to Sprinting' >> session the evening of June 1, lead by Shauna Gordon-McKeon and other >> members of Python community. To grab a free ticket for this session, just >> visit >> https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-tickets-22435151141 >> . >> >> *Please note that conference registration is sold out, but you do not >> need a conference registration to come to the Sprints. >> >> ___ >> PSF-Community mailing list >> psf-commun...@python.org >> https://mail.python.org/mailman/listinfo/psf-community >> > > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/camillamon%40gmail.com > > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Yearly PyPI breakage
> On May 6, 2016, at 1:11 PM, A.M. Kuchling wrote: > > On Thu, May 05, 2016 at 10:31:48PM -0400, Donald Stufft wrote: >> I don't believe we've ever told someone that something can't happen because >> of >> Warehouse, only that *I* won't implement something until after Warehouse. >> That >> often times means that something won't happen until after Warehouse because >> of >> the severe shortage of people with enough time and motivation to work on this >> stuff but if someone did step up more things would get done. > > Could the PSF help with this, whether by paying for Donald's (or a > consultant's) time to whatever do final implementation, polishing, > testing, or sysadmin work is required? Personally, my time is already paid for by HPE to work on this stuff but I’m only one person. The PSF could pay for others to help with that though. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA signature.asc Description: Message signed with OpenPGP using GPGMail ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Wrong OSX platform in sysconfig.py causing installation problems
Then I have found the right list to post on, for my problem is a bug in the Python 3.5.1 distribution. Albeit one which will only manifest in certain situations. The presence of numerous `-isysroot /Developer/SDKs/MacOSX10.6.sdk` directives in the following file /Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/_sysconfigdata.py Will cause errors for people who have kept around the old /Developer directory tree, and old SDKs like 10.6, for building backwards compatible old code. Newer versions of the SDKs are now kept inside the Xcode application itself. And then they will only have a problem when trying to install a package with C extensions, which in my case was Persistence, a dependency of ZODB. And even more so, ONLY when trying to pip install said package into a virtual environment created by 3.5’s pyvenv command, if installing the package into the system wide Python there will be no error. Such is this corner-case hell I have found myself, until I decided to dump my older /Developer directory tree and SDKs, as those were for a project long defunct. You see the -isysroot flag has the unusual behavior where instead of reporting an error when it cannot find the newly specified system root it simply has no effect. So if you don’t have the SDK specified in the location specified then the flag does nothing, as I assume is the case for 99% of people. I understand the need to make Python 3.5 backwards compatible, but doing it this way would appear to have the side effect of breaking the ability to install packages using C extensions in virtual environments, or at least it did for me. Joseph Nunn josephn...@gmail.com joseph.n...@uci.edu > On May 06 , 2016, at 4:20 AM, Ned Deily wrote: > > > On May 6, 2016, at 05:42, Joseph Nunn wrote: >> Hello Everyone, my first post. I would also like to subscribe but >> haven't seen how yet. >> >> So I've an issue with how the 3.5.1 OSX >> package installs on OSX. The problem was first made apparent >> when trying to create a virtual environment and `pip install ZODB`, >> which failed as clang and the linker could not find either the >> include or lib directories for a dependency. By adding a -v option >> to the compiler options I was able to see in the compiler flags >> the following: >> >> -isysroot /Developer/SDKs/MacOSX10.6.sdk >> >> Which was not present in the compiler flags of other people >> who I was talking with. [...] > > Hi Joseph! > > Welcome! Note this list is for the development of Python itself, not for > usage or installation issues. The Python Developer's Guide > (https://docs.python.org/devguide/) including its FAQ gives information about > mailing lists and other support forums to get help with general Python > issues. That said, without more information, it would be difficult to know > exactly what problem you are running into but, since you mention missing > headers, my guess is that you need to install Apple's Command Line Tools as > described here: > > https://docs.python.org/devguide/setup.html#build-dependencies > > Installing Xcode by itself is not sufficient. The sysroot and flag values > you note in _sysconfigdata.py are normal and there for compatibility with > installing on older versions of OS X; they should not cause a problem on > newer releases. For what it's worth, I was able to install ZODB with the > current python.org 3.5.1 on OS X 10.11.4 using either venv or virtualenv. > > Good luck! > > --Ned > > P.S. Mailing list info is available here: https://mail.python.org. The bug > tracker is here: https://bugs.python.org > > -- > Ned Deily > n...@python.org -- [] > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Yearly PyPI breakage
On Thu, May 05, 2016 at 10:31:48PM -0400, Donald Stufft wrote: > I don't believe we've ever told someone that something can't happen because of > Warehouse, only that *I* won't implement something until after Warehouse. That > often times means that something won't happen until after Warehouse because of > the severe shortage of people with enough time and motivation to work on this > stuff but if someone did step up more things would get done. Could the PSF help with this, whether by paying for Donald's (or a consultant's) time to whatever do final implementation, polishing, testing, or sysadmin work is required? --amk ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2016-04-29 - 2016-05-06) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open5504 (+29) closed 33223 (+56) total 38727 (+85) Open issues with patches: 2388 Issues opened (58) == #24225: Idlelib: changing file names http://bugs.python.org/issue24225 reopened by serhiy.storchaka #26156: Bad name into power operator syntax http://bugs.python.org/issue26156 reopened by r.david.murray #26163: FAIL: test_hash_effectiveness (test.test_set.TestFrozenSet) http://bugs.python.org/issue26163 reopened by berker.peksag #26888: Multiple memory leaks after raw Py_Initialize and Py_Finalize. http://bugs.python.org/issue26888 opened by Aleksander Gajewski #26889: Improve Doc/library/xmlrpc.client.rst http://bugs.python.org/issue26889 opened by serhiy.storchaka #26890: inspect.getsource gets source copy on disk even when module ha http://bugs.python.org/issue26890 opened by sebastien.bourdeauducq #26891: CPython doesn't work when you disable refcounting http://bugs.python.org/issue26891 opened by larry #26892: debuglevel not honored in urllib http://bugs.python.org/issue26892 opened by Chi Hsuan Yen #26894: Readline not aborting line edition on sigint http://bugs.python.org/issue26894 opened by memeplex #26896: mix-up with the terms 'importer', 'finder', 'loader' in the im http://bugs.python.org/issue26896 opened by Oren Milman #26897: Clarify Popen stdin, stdout, stderr http://bugs.python.org/issue26897 opened by Yclept.Nemo #26899: struct.pack_into(), struct.unpack_from() don't document suppor http://bugs.python.org/issue26899 opened by pfalcon #26900: Exclude the private API from the stable API http://bugs.python.org/issue26900 opened by serhiy.storchaka #26901: Argument Clinic test is broken http://bugs.python.org/issue26901 opened by serhiy.storchaka #26903: ProcessPoolExecutor(max_workers=64) crashes on Windows http://bugs.python.org/issue26903 opened by diogocp #26904: Difflib quick_ratio() could use Counter() http://bugs.python.org/issue26904 opened by Michael Cuthbert #26906: format(object.__reduce__) fails intermittently http://bugs.python.org/issue26906 opened by ztane #26907: Add missing getsockopt constants http://bugs.python.org/issue26907 opened by christian.heimes #26909: Serious performance loss (10 times) when NOT using .drain() http://bugs.python.org/issue26909 opened by mmarkk #26911: lib2to3/tests/pytree_idempotency.py has a broken import http://bugs.python.org/issue26911 opened by imz #26912: test/test_email/torture_test.py (and test_asian_codecs.py) has http://bugs.python.org/issue26912 opened by imz #26917: unicodedata.normalize(): bug in Hangul Composition http://bugs.python.org/issue26917 opened by arigo #26919: android: test_cmd_line fails http://bugs.python.org/issue26919 opened by xdegaye #26920: android: test_sys fails http://bugs.python.org/issue26920 opened by xdegaye #26923: asyncio.gather drops cancellation http://bugs.python.org/issue26923 opened by JohannesEbke #26924: android: test_concurrent_futures fails http://bugs.python.org/issue26924 opened by xdegaye #26925: android: test_multiprocessing_main_handling fails http://bugs.python.org/issue26925 opened by xdegaye #26926: Large files are not supported on Android http://bugs.python.org/issue26926 opened by xdegaye #26928: android: test_site fails http://bugs.python.org/issue26928 opened by xdegaye #26929: android: test_strptime fails http://bugs.python.org/issue26929 opened by xdegaye #26930: Upgrade installers to OpenSSL 1.0.2h http://bugs.python.org/issue26930 opened by alex #26931: android: test_distutils fails http://bugs.python.org/issue26931 opened by xdegaye #26934: android: test_faulthandler fails http://bugs.python.org/issue26934 opened by xdegaye #26935: android: test_os fails http://bugs.python.org/issue26935 opened by xdegaye #26936: android: test_socket fails http://bugs.python.org/issue26936 opened by xdegaye #26937: android: test_tarfile fails http://bugs.python.org/issue26937 opened by xdegaye #26938: android: test_concurrent_futures hangs on armv7 http://bugs.python.org/issue26938 opened by xdegaye #26939: android: test_functools hangs on armv7 http://bugs.python.org/issue26939 opened by xdegaye #26940: android: test_importlib hangs on armv7 http://bugs.python.org/issue26940 opened by xdegaye #26941: android: test_threading hangs on armv7 http://bugs.python.org/issue26941 opened by xdegaye #26942: android: test_ctypes crashes on armv7 http://bugs.python.org/issue26942 opened by xdegaye #26944: android: test_posix fails http://bugs.python.org/issue26944 opened by xdegaye #26945: difflib.HtmlDiff().make_file() treat few change as whole line http://bugs.python.org/issue26945 opened by Fairuz Zack #26947: Documentation improvement needed http://bugs.python.org/issu
[Python-Dev] 3.4.5 Release Schedule (not 3.4.4, whoops)
On 05/06/2016 08:34 AM, Larry Hastings wrote: That's perfectly cromulent! I'm going to piggyback on that for 3.4. Therefore, 3.4.4 rc1 will be on June 11th, and 3.4.4 final will be on June 25. Whoops, a whole bunch of off-by-one bugs. First, I'll be releasing 3.4.5 in June. 3.4.4 was released in December 2015. D'oh! Second, Benjamin and I have slightly different approaches--I like to tag on Saturday and release on Sunday. Therefore 3.4.5 rc1 will be released June 12th, and 3.4.5 final will be released June 26th. (3.4.5 rc1 will be tagged Saturday June 11, 3.4.5 final will be tagged June 25th.) The release schedule PEP has all the correct numbers and dates and such. That'll teach me to send these emails while half-asleep, //arry/ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 3.4.4 Release Schedule
On 05/03/2016 09:07 AM, Benjamin Peterson wrote: 2.7.12rc1 will be on June 11th, and the final will be on June 25. That's perfectly cromulent! I'm going to piggyback on that for 3.4. Therefore, 3.4.4 rc1 will be on June 11th, and 3.4.4 final will be on June 25. Reminder: 3.4.4 will be a source-only release. June's coming up Python, //arry/ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Wrong OSX platform in sysconfig.py causing installation problems
On May 6, 2016, at 05:42, Joseph Nunn wrote: > Hello Everyone, my first post. I would also like to subscribe but > haven't seen how yet. > > So I've an issue with how the 3.5.1 OSX > package installs on OSX. The problem was first made apparent > when trying to create a virtual environment and `pip install ZODB`, > which failed as clang and the linker could not find either the > include or lib directories for a dependency. By adding a -v option > to the compiler options I was able to see in the compiler flags > the following: > > -isysroot /Developer/SDKs/MacOSX10.6.sdk > > Which was not present in the compiler flags of other people > who I was talking with. [...] Hi Joseph! Welcome! Note this list is for the development of Python itself, not for usage or installation issues. The Python Developer's Guide (https://docs.python.org/devguide/) including its FAQ gives information about mailing lists and other support forums to get help with general Python issues. That said, without more information, it would be difficult to know exactly what problem you are running into but, since you mention missing headers, my guess is that you need to install Apple's Command Line Tools as described here: https://docs.python.org/devguide/setup.html#build-dependencies Installing Xcode by itself is not sufficient. The sysroot and flag values you note in _sysconfigdata.py are normal and there for compatibility with installing on older versions of OS X; they should not cause a problem on newer releases. For what it's worth, I was able to install ZODB with the current python.org 3.5.1 on OS X 10.11.4 using either venv or virtualenv. Good luck! --Ned P.S. Mailing list info is available here: https://mail.python.org. The bug tracker is here: https://bugs.python.org -- Ned Deily n...@python.org -- [] ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Wrong OSX platform in sysconfig.py causing installation problems
Hello Everyone, my first post. I would also like to subscribe but haven't seen how yet. So I've an issue with how the 3.5.1 OSX package installs on OSX. The problem was first made apparent when trying to create a virtual environment and `pip install ZODB`, which failed as clang and the linker could not find either the include or lib directories for a dependency. By adding a -v option to the compiler options I was able to see in the compiler flags the following: -isysroot /Developer/SDKs/MacOSX10.6.sdk Which was not present in the compiler flags of other people who I was talking with. The isysroot flag changes the location of includes and libs from the system default, which would be why they can't be found. After grepping around a bit I found this file: /Library/Frameworks/Python.framework/Versions/3.5 /lib/python3.5/_sysconfigdata.py Within which are many mentions of this flag, as so: 'CONFIGURE_CFLAGS': '-arch i386 -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.6.sdk -g', 'CONFIGURE_CFLAGS_NODIST': '-Werror=declaration-after -statement', 'CONFIGURE_CPPFLAGS': '-isysroot /Developer/SDKs/MacOSX10.6.sdk', 'CONFIGURE_LDFLAGS': '-arch i386 -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.6.sdk -g', 'CONFIG_ARGS': "'-C' '--enable-framework' '--enable- universalsdk=/Developer/SDKs/MacOSX10.6.sdk' '--with-universal-archs=intel' '--with-computed-gotos' '--without-ensurepip' 'LDFLAGS=-g' 'CFLAGS=-g' 'CC=gcc-4.2'", among others. By running Python 3.5's sysconfig.py as a module, via `python -m sysconfig`, I see the following at the beginning of the output: Platform: "macosx-10.6-intel" Python version: "3.5" Current installation scheme: "posix_prefix" And when I simply go into python interactive mode, import sysconfig, and type sysconfig.get_platform() it returns macosx-10.6-intel. I believe somehow the platform being reported is incorrect, but looking at my environment, I do not have any kind of compiler flags or anything else like that set in my bash init files. Can someone who has a working OSX 3.5 installation check their reported platform to see what it is and if anyone has an idea as to how this information is getting into the installation and where I might change it please let me know. Sincerely, Joseph josephn...@gmail.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com