[issue12619] Automatically regenerate platform-specific modules

Zachary Ware added the comment: The platform-specific modules have been removed. -- nosy: +zach.ware resolution: -> out of date stage: -> resolved status: open -> closed superseder: -> Remove Lib/plat-*/* files ___ Python tracker

[issue12619] Automatically regenerate platform-specific modules

Changes by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue12619] Automatically regenerate platform-specific modules

Stefan Krah added the comment: See also #19554. -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12619] Automatically regenerate platform-specific modules

Ramchandra Apte added the comment: +1 for this. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue12619] Automatically regenerate platform-specific modules

Roundup Robot added the comment: New changeset 6159311f0f44 by Victor Stinner in branch 'default': Issue #12619: Expose socket.SO_BINDTODEVICE constant http://hg.python.org/cpython/rev/6159311f0f44 -- ___ Python tracker

[issue12619] Automatically regenerate platform-specific modules

STINNER Victor added the comment: For Freevo: yes, it uses the CDROM module. But this module doesn't look to be perfect because Freevo has a fallback for FreeBSD and another for... Linux (because of missing CDROM.CDROM_DRIVE_STATUS?): - try: from CDROM import *

[issue12619] Automatically regenerate platform-specific modules

Jakub Wilk added the comment: * STINNER Victor , 2011-10-19, 22:55: >>FYI, in Debian we have at least: >>one package using the CDROM module, >Is it cdsuite? (http://offog.org/code/cdsuite.html) No, Freevo . >>3 packages using the IN module, >I found policykit (i

[issue12619] Automatically regenerate platform-specific modules

Changes by Petri Lehtinen : -- nosy: -petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue12619] Automatically regenerate platform-specific modules

STINNER Victor added the comment: > FYI, in Debian we have at least: > one package using the CDROM module, Is it cdsuite? (http://offog.org/code/cdsuite.html) > 3 packages using the IN module, I found policykit (it uses IN.INT_MAX). What are the 2 others? Which constants are used? > 14 pack

[issue12619] Automatically regenerate platform-specific modules

STINNER Victor added the comment: > > There are differents examples: > > - LONG_MAX is 9223372036854775807 even on 32 bits system > > - On Mac OS X, FAT programs contains 32 and 64 binaries, whereas > > constants are changed for 32 or 64 bits > > That's because the h2py.py script doesn't kno

[issue12619] Automatically regenerate platform-specific modules

STINNER Victor added the comment: I created the issue #13226 to provide RTLD_* constants on all platforms (not only on Linux and sunos5). -- ___ Python tracker ___

[issue12619] Automatically regenerate platform-specific modules

Marc-Andre Lemburg added the comment: STINNER Victor wrote: > > STINNER Victor added the comment: > >> you should make a case by example > > Did you read comments of this issue and my email thread on python-dev? No. > There are differents examples: > > - LONG_MAX is 9223372036854775807 e

[issue12619] Automatically regenerate platform-specific modules

Jakub Wilk added the comment: FYI, in Debian we have at least: one package using the CDROM module, 3 packages using the IN module, 14 packages using the DLFCN module. -- ___ Python tracker

[issue12619] Automatically regenerate platform-specific modules

Antoine Pitrou added the comment: > If they don't hurt, why remove them? Bogus constants don't hurt? -- ___ Python tracker ___ ___ P

[issue12619] Automatically regenerate platform-specific modules

Martin v. Löwis added the comment: Victor, please accept that this entire infrastructure was originally added because there was a need for it, and the need did not go away. It's probably relevant only for a minority of applications, but you would make this minority's lifes much more complicat

[issue12619] Automatically regenerate platform-specific modules

STINNER Victor added the comment: > you should make a case by example Did you read comments of this issue and my email thread on python-dev? There are differents examples: - LONG_MAX is 9223372036854775807 even on 32 bits system - On Mac OS X, FAT programs contains 32 and 64 binaries, where

[issue12619] Automatically regenerate platform-specific modules

Marc-Andre Lemburg added the comment: I don't see why these modules should be auto-generated. The constants in the modules hardly ever change and are also not affected by architecture differences (e.g. Mac OS X, Solaris, etc.) AFAICT. If you think they need to be auto-generated, you should make

[issue12619] Automatically regenerate platform-specific modules

Charles-François Natali added the comment: > Related : #1565071 and #3990 . There is no reason to keep plat-xxx files if > cannot be managed properly. +1 -- ___ Python tracker _

[issue12619] Automatically regenerate platform-specific modules

Ned Deily added the comment: What do you do for platforms like OS X where we support one set of binary files that contain multi-architecture C-files that can run as Intel-64, Intel-32 or PPC-32 on the same machine at user option at run time? For example, the Apple-suppled system Python on OS

[issue12619] Automatically regenerate platform-specific modules

Roumen Petrov added the comment: Related : #1565071 and #3990 . There is no reason to keep plat-xxx files if cannot be managed properly. -- nosy: +rpetrov ___ Python tracker

[issue12619] Automatically regenerate platform-specific modules

Arfrever Frehtes Taifersar Arahesis added the comment: Regeneration of platform-specific modules fixes concerns about their outdateness and architecture differences (32-bit vs 64-bit, big endian vs little endian). Regeneration of given module could be performed only when corresponding header

[issue12619] Automatically regenerate platform-specific modules

Martin v. Löwis added the comment: -1 on auto-building. The header needed may not be available on the build platform, if it is not normally needed to build Python. -- ___ Python tracker __

[issue12619] Automatically regenerate platform-specific modules

STINNER Victor added the comment: > is auto-generation wanted? For example, Lib/plat-linux/IN.py was regenerated at Nov 23 12:09:28 2002 (revision c2604d69aa5d) for the last time, and nobody complained. These modules are inconsistent. For example, the IN module contains constants of 64 bits

[issue12619] Automatically regenerate platform-specific modules

Changes by Arfrever Frehtes Taifersar Arahesis : Added file: http://bugs.python.org/file23423/python-regenerate_platdir.patch ___ Python tracker ___ _

[issue12619] Automatically regenerate platform-specific modules

Changes by Arfrever Frehtes Taifersar Arahesis : Removed file: http://bugs.python.org/file22726/python-regenerate_platdir.patch ___ Python tracker ___ ___

[issue12619] Automatically regenerate platform-specific modules

Changes by Jesus Rivero : -- nosy: +Neurogeek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue12619] Automatically regenerate platform-specific modules

Changes by Arfrever Frehtes Taifersar Arahesis : Removed file: http://bugs.python.org/file22723/python-regenerate_platdir.patch ___ Python tracker ___ ___

[issue12619] Automatically regenerate platform-specific modules

Arfrever Frehtes Taifersar Arahesis added the comment: The new patch creates platform-specific modules at build time and verifies their syntax. -- Added file: http://bugs.python.org/file22726/python-regenerate_platdir.patch ___ Python tracker

[issue12619] Automatically regenerate platform-specific modules

Matthias Klose added the comment: is auto-generation wanted? are you sure that you can't end up with bad syntax? -- ___ Python tracker ___ __

[issue12619] Automatically regenerate platform-specific modules

Arfrever Frehtes Taifersar Arahesis added the comment: I don't care when they will be regenerated. -- ___ Python tracker ___ ___ Pyth

[issue12619] Automatically regenerate platform-specific modules

Éric Araujo added the comment: (Autotools/make newbie here) Why during install and not build? -- ___ Python tracker ___ ___ Python-bu

[issue12619] Automatically regenerate platform-specific modules

New submission from Arfrever Frehtes Taifersar Arahesis : I suggest that platform-specific modules be automatically regenerated during installation. I'm attaching a patch. -- files: python-regenerate_platdir.patch keywords: patch messages: 140952 nosy: Arfrever, amaury.forgeotdarc, djc