Re: Recompilation of Python3.6.x
On 03/23/2017 12:23 AM, Jon Ribbens wrote: On 2017-03-22, Grant Edwards wrote: On 2017-03-22, Thomas Nyberg wrote: On 03/22/2017 03:22 PM, Jon Ribbens wrote: A simple table with a list of the library names, the debian package names, and the rpm names would provide the information in a way that would be useful to everyone. A _simple_ table would be useful. However, a _simple_ table is not possible. I definitely agree, but it would be kind of difficult to maintain. I mean if you supported debian and redhat (should others be considered?), And you would need table for each _version_ of each distribution (libraries sometimes get combined/renamed/split). Not really, that's why I suggested one of the fields in the table would be the standard library name - people should always be able to use that to find the appropriate package for their distribution (if there is one, otherwise they'll need to compile from source). And you would need tables showing which libraires are required for which Python features: tkinter is optional, crypto is optional (or at least used to be), etc. That's a good idea - that would make the simple table have 4 columns: name, deb, rpm, python module (or "essential"). The information must be somewhere because Python must have been compiled frequently and correctly for the various (important) OSs before making it available to the public. And I do not think that it is left up to "your luck" that the required packages and libraries are present. -- K.D.J. -- https://mail.python.org/mailman/listinfo/python-list
PyDev 5.6.0 Released
PyDev 5.6.0 Release Highlights - *Important* PyDev now requires Java 8 and Eclipse 4.6 (Neon) onwards. - PyDev 5.2.0 is the last release supporting Eclipse 4.5 (Mars). - *Debugger* - *Performance* enhancements on the *debugger* (which should be *60%-100%* faster now). - The *debugger* now only supports *Python 2.6 onwards* (keep on PyDev 5.5.0 for Python 2.5 or below). - Properly displaying variables when the *interactive console* is connected to a *debug session*. *#PyDev-776* - Providing a way for the debugger to support a user-specified version of Qt for debugging QThreads (*preferences > PyDev > Debug > Qt Threads*). - Fixed issue where a *native Qt signal is not callable* message was raised when connecting a signal to QThread.started. - Fixed issue in displaying variable (with *Ctrl+Shift+D*) when debugging. - Debug view toolbar icons no longer appearing stretched due to Set Next Statement icon having a different size. - *Code completion* - *super* is now properly recognized (code completion and find definition). - *pytest fixtures* are now properly recognized (code completion and find definition). - Suppress invalid completions on literals numbers (patch by Jonah Graham) - *Others* - It's now possible to save the PyUnit preferences to the project or user settings. - Upgraded *pep8* to the latest *pycodestyle*. - Upgraded to latest *autopep8*. - Fixed issue in Django shell if version >= 1.10 *#PyDev-752*. - Add support for *coverage 4.x* (minimum supported version is now 4.3). *#PyDev-691* - Syntax highlighting for *matmul operator* (was being considered a decorator). *#PyDev-771* - Making *PyLint* use the same thread pool used for code analysis. - String index out of range while reading buffer in AbstractShell. *#PyDev-768* What is PyDev? PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and IronPython development. It comes with goodies such as code completion, syntax highlighting, syntax analysis, code analysis, refactor, debug, interactive console, etc. Details on PyDev: http://pydev.org Details on its development: http://pydev.blogspot.com What is LiClipse? LiClipse is a PyDev standalone with goodies such as support for Multiple cursors, theming, TextMate bundles and a number of other languages such as Django Templates, Jinja2, Kivy Language, Mako Templates, Html, Javascript, etc. It's also a commercial counterpart which helps supporting the development of PyDev. Details on LiClipse: http://www.liclipse.com/ Cheers, -- Fabio Zadrozny -- Software Developer LiClipse http://www.liclipse.com PyDev - Python Development Environment for Eclipse http://pydev.org http://pydev.blogspot.com PyVmMonitor - Python Profiler http://www.pyvmmonitor.com/ -- https://mail.python.org/mailman/listinfo/python-list
Re: Recompilation of Python3.6.x
On 03/23/2017 01:45 AM, Klaus Jantzen wrote: > The information must be somewhere because Python must have been compiled > frequently and correctly for the various (important) OSs before making > it available to the public. And I do not think that it is left up to > "your luck" that the required packages and libraries are present. The information is essentially present in the recipe files that create the binary packages. As new versions come out, the distro maintainers modify the recipe file (in the RPM world, that's a SPEC file, distributed with the SRPM packages) when needed, based on trial and error, and also on the release notes for the upstream project. In SRPM spec files, there is a list of "build-requires" that list what packages (usually -devel). For Debian, as you've been told a while back, apt has a command to install the dependencies needed to build something: apt build-dep python3 After that, you can download the latest Python 3 debian source package, and then modify it to build the newer tarball. https://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.en.html So to answer your question, the list of what's required to build something is built into the distro package system, and that's where it's also maintained. Also the default build options for packages are set there as well. -- https://mail.python.org/mailman/listinfo/python-list
Re: Recompilation of Python3.6.x
On 03/23/2017 03:45 AM, Klaus Jantzen wrote: The information must be somewhere because Python must have been compiled frequently and correctly for the various (important) OSs before making it available to the public. And I do not think that it is left up to "your luck" that the required packages and libraries are present. Of course it's true that people don't just compile things by luck, but it's also true that the issue is kind of beyond cpython. The best you could really expect is for cpython to say the following libraries with the following major numbers are required (possibly with links to the websites for the sources). It's out of the cpython programmers control how these libraries are made available on the many different systems and distributions that python is used on. If you use it on distro a and you want to compile it, it's basically your responsibility to figure out how to get the libraries. So really the main conclusion is that you should probably figure out how to use your distribution wisely to find this information. For any systems providing something similar to apt-get build-dep it's pretty easy (which _is_ your situation and hence you have already solved your problem). For others...well if you choose to use such a system it's your responsibility. As much as it was irritating not learning these tricks earlier, you do now know them and should be fine going forward... Cheers, Thomas -- https://mail.python.org/mailman/listinfo/python-list
Re: Recompilation of Python3.6.x
On 2017-03-23, Klaus Jantzen wrote: >>> And you would need tables showing which libraires are required for >>> which Python features: tkinter is optional, crypto is optional (or >>> at least used to be), etc. >> >> That's a good idea - that would make the simple table have 4 >> columns: name, deb, rpm, python module (or "essential"). > > The information must be somewhere because Python must have been > compiled frequently and correctly for the various (important) OSs > before making it available to the public. For CPython, the information about what libraries are required is in the autoconf input files (e.g. configure.ac) in the CPython sources. http://www.gnu.org/software/autoconf/autoconf.html How you locate information about what _packages_ those libraries are in varies depending on which distro and packaging system are in use. > And I do not think that it is left up to "your luck" that the > required packages and libraries are present. When CPython is packaged for a Linux distro, those options and library depdencies are figured out and then encoded into the build scripts that are used for the distros respective packaging systems (the .ebuild file for Portage, the .spec file for RPM, the files inthe ./debian directory in a .deb package). If you're building CPython, you have two choices: 1) Use your distro's packaging system to build it. That will insure that all the required libraries are built/installed. 2) Build it using the normal untar-configure-make steps. It may take many tries at the 'configure' step as you install required libraries until the configure script is happy. _Usually_ once the configure step is done, the make shouldn't uncover any more missing libraries. -- Grant Edwards grant.b.edwardsYow! When you get your at PH.D. will you get able to gmail.comwork at BURGER KING? -- https://mail.python.org/mailman/listinfo/python-list
Re: Manager for project templates, that allows "incremental" feature addition
On Wednesday, 22 March 2017 09:41:21 UTC, Lele Gaifax wrote: > This what I wrote and heavily use > > https://pypi.python.org/pypi/metapensiero.tool.tinject > > It seems to fit some, but not all, of your requested features. Thanks - it looks like it could be very useful. I'll certainly give it a try! Paul -- https://mail.python.org/mailman/listinfo/python-list
Re: Manager for project templates, that allows "incremental" feature addition
On Thursday, 23 March 2017 15:56:43 UTC, Paul Moore wrote: > On Wednesday, 22 March 2017 09:41:21 UTC, Lele Gaifax wrote: > > This what I wrote and heavily use > > > > https://pypi.python.org/pypi/metapensiero.tool.tinject > > > > It seems to fit some, but not all, of your requested features. > > Thanks - it looks like it could be very useful. I'll certainly give it a try! Sadly, it doesn't support Windows, which is what I use. The "inquirer" dependency is the problem - it has a pinned dependency on an old version of readchar that has a bug (since fixed) on Windows, and it depends on blessings, which needs curses, which isn't in the stdlib on Windows, although I could get a 3rd party version. Pity, as it looked very interesting. Thanks anyway for the suggestion. Paul -- https://mail.python.org/mailman/listinfo/python-list
Re: Manager for project templates, that allows "incremental" feature addition
Paul Moore writes: > Sadly, it doesn't support Windows, which is what I use. I'm sorry, there is little I can do on that front, but if you come up with an alternative library, please let me know. ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. l...@metapensiero.it | -- Fortunato Depero, 1929. -- https://mail.python.org/mailman/listinfo/python-list
SNMP
What is easiest way to read and write SNMP values with Python? -- https://mail.python.org/mailman/listinfo/python-list
