Displaying 20 results from an estimated 10000 matches similar to: "Python 3.3 for CentOS-6"
2013 May 12
1
OpenStack Grizzly on CentOS-6.4
Hello,
setting up the newest OpenStack Grizzly release seems to be really straight-forward.
Red Hat has put together all support for this at http://openstack.redhat.com/.
I've documented installation, post-install config tweaks, how to add a few
ready-to-use guest images and links to a few gotchas on the following wiki page:
http://jur-linux.org/testwiki/index.php/CloudLinux/OpenStack
2011 Dec 10
0
RHEL6.2 kernel
Hello,
until a more official rebuild shows up, I have recomppiled the
RHEL 6.2 kernel src.rpm and copied the binary rpms to:
http://jur-linux.org/download/redhat-kernel/6/220.el6/
This is running happily on a dozen machines now.
best regards,
Florian La Roche
2013 Feb 26
3
Did anybody do a dovecot update on centos 5.x?
Hi,
dose anybody did a dovecot update from the original 1.0.7 to e.g. 1.1 or
1.2 from atrpms repository?
We dont have any special settings; Each user one mbox mailbox. About 500
imap/pop3 accounts, 400GB data.
Any suggestions and comments are welcome.
Regards . G. Reinicke
--
G?tz Reinicke - IT-Koordinator - Filmakademie Baden-W?rttemberg GmbH
2018 Feb 01
0
Migrate utils/ Python 2 scripts to Python 3
On 2018-01-31, Chris Matthews wrote:
>The suggested way to do this on OSX is using env:
>
>#!/usr/bin/env python3
Sorry, I use `#!/usr/bin/env python3` in my patch but used #!/usr/bin/python3 in the email :)
>
>> On Jan 31, 2018, at 10:48 AM, Adrian Prantl <aprantl at apple.com> wrote:
>>
>>
>>
>>> On Jan 31, 2018, at 10:04 AM, Fāng-ruì Sòng via
2019 Nov 29
2
[PATCH] tests: rhv-upload: Require nbdkit python plugin
With recent nbdkit the skip test fails the rhv-upload test skip:
$ nbdkit python3 --version
nbdkit: error: cannot open plugin 'python3':
/usr/local/lib/nbdkit/plugins/nbdkit-python3-plugin.so: cannot open
shared object file: No such file or directory
It seems that the python plugin is always installed as
nbdkit-python-plugin.so, so the correct test now is:
nbdkit
2020 Oct 13
2
[RFC] Python 2 / Python 3 status, final step(s)
Hi Folks,
Now that LLVM 11.0.0 has been released, it's time to prepare for the final step
envisionned in the previous RFC named *[RFC] Python 2 / Python 3 status* [0],
ie. requiring Python3.6 for LLVM 12.0.0, to be released in 2021.
At least Fedora already only ships Python3 and we didn't have much bugs reported
wrt. Python compatibility for the LLVM toolchain.
Indeed, all Python scripts
2019 Dec 17
2
Python 2 compatibility for utility scripts
On Tue, Dec 17, 2019 at 12:55 PM Nico Weber <thakis at chromium.org> wrote:
> On Tue, Dec 17, 2019 at 12:41 PM James Y Knight <jyknight at google.com>
> wrote:
>
>> It sounds like you ran into a bug in the test infrastructure's code to
>> determine if python3 is supported. Fixing that might be harder, but it only
>> needs to be fixed once no matter how
2017 Jun 12
0
xen4centos kernel version / debuginfo
On 06/12/2017 05:17 PM, Sarah Newman wrote:
> Is there any problem moving to 4.9.31? This contains upstream commits f2e767bb5d6ee0d9 for mpt3sas and
> 69861e0a52f87333 for dom0 memory mappings.
4.9.31-27 is tagged for testing presently along with updated firmware.
I have it running on one hypervisor on Xen-44 and it has been stable for
3 days so far. We could probably use some more testing
2016 Feb 12
1
Re: [PATCH] python: tests: use more targeted assert*() functions/checks
On Friday 12 February 2016 17:13:17 Richard W.M. Jones wrote:
> On Fri, Feb 12, 2016 at 06:04:47PM +0100, Pino Toscano wrote:
> > - use assertIsInstance, assertNotEqual, and assertIsNotNone as more
> > specific checks (will produce better logging)
> > - use assertRaises when expecting exceptions being thrown
> > - when testing internal_test_rhashtable, instead of
2012 Jul 30
1
Accents and special character using hwriter (on Windows)
Hello,
I have a problem with special characters such as "?" or "?" when using
hwriter. This only happens when I use windows, it works fine on mac. If I
do:
print(datosdv)
"Ciencias Sociales y Jur?dicas n:74 | 33.94%"
but:
hwrite(datosdv, p, br=TRUE)
"Ciencias Sociales y Jur?dicas n:74 | 33.94%"
The bad sign is in the code, is not a problem of the
2019 Dec 17
2
Python 2 compatibility for utility scripts
It sounds like you ran into a bug in the test infrastructure's code to
determine if python3 is supported. Fixing that might be harder, but it only
needs to be fixed once no matter how much more python3 development there
will be.
Right now, most of our scripts were originally written for python 2, so
certainly it's easy for them to support python 2. But, it was a lot of work
by various
2015 Feb 18
1
debuginfo versioning tools?
On Tue, February 17, 2015 15:20, Les Mikesell wrote:
> Are there any tools to help assemble libraries and debuginfo to
> examine core dumps that happened on another host where the versions
> don't match? Something like mock but build-version specific and with
> the debuginfo packages pulled in?
>
I am not sure that I understand your question so if this answer is
totally
2012 Dec 04
0
[LLVMdev] Minimum Python Version
> several people already asked what are the concrete benefits of breaking support for end-of-life python versions?
Generally I think the only compelling argument is "for a given level
of maintenance effort, you either sacrifice support for old-dead
versions, or new versions", and obviously new versions should be
preferred. The question is how much does it cost to interoperate.
On
2020 Oct 14
0
Re: libivrt client using python on windows
On 10/12/20 9:47 PM, Talha Jawaid wrote:
> Hello,
>
> I want to run a python script on Windows to remotely control libvirt
> running on a (Linux) server. This was all working fine while prototyping
> stuff on the server but now I am having some trouble installing the
> python module on windows (“pip install” fails). I struggled through
> getting it to COMPILE but then ran
2018 Feb 01
1
Migrate utils/ Python 2 scripts to Python 3
Nope.
Regarding "python" potentially pointing to python3:
Arch Linux has done that for years. That unilateral decision on their part
was widely-decried as a mistake at the time, and spawned the python doc you
reference saying that shouldn't be done. However, Fedora is now making
noises about doing the same, in a few years, after driving a change in the
upstream recommendation.
2012 Dec 04
0
[LLVMdev] Minimum Python Version
On Mon, Dec 3, 2012 at 8:49 PM, Duncan Sands <baldrick at free.fr> wrote:
> Lenny came out in 2009, and
> was the latest stable Debian release until 6 months ago, so it's not even
> that
> old.
To put that in perspective, Lenny was released around r64555. That's pretty old.
On Mon, Dec 3, 2012 at 8:49 PM, Duncan Sands <baldrick at free.fr> wrote:
> What is the
2019 Mar 16
0
ANNOUNCE: Oz 0.17.0 release
All,
I'm pleased to announce release 0.17.0 of Oz. Oz is a program for
doing automated installation of guest operating systems with limited
input from the user. Release 0.17.0 switches Oz to be python3 only,
since Python 2 support is ending soon. There are also some minor fixes
in here, along with the addition of support for some new OSs.
A tarball and zipfile of this release is
2018 Jan 29
0
Re: python 3 bindings on libguestfs
The logs here:
> checking for python... /opt/python/x86_64/3.1.1/bin/python3
> checking Python version... 3.1
> checking for PYTHON... no
> checking for PYTHON... no
> checking Python prefix... /opt/python/x86_64/3.1.1
> checking for Python site-packages path... /opt/python/x86_64/3.1.1/lib/python3.1/site-packages
> checking for Python extension suffix (PEP-3149)... .so
>
2018 Jan 31
0
Migrate utils/ Python 2 scripts to Python 3
The suggested way to do this on OSX is using env:
#!/usr/bin/env python3
> On Jan 31, 2018, at 10:48 AM, Adrian Prantl <aprantl at apple.com> wrote:
>
>
>
>> On Jan 31, 2018, at 10:04 AM, Fāng-ruì Sòng via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> Thanks for the information. Then how about standalone scripts (many
>> one-file) like
2018 Feb 01
0
Migrate utils/ Python 2 scripts to Python 3
As mentioned in https://docs.python.org/3/using/unix.html#miscellaneous, for Python 3 the shebang line should be:
#!/usr/bin/env python3
For Python 2 the shebang line should probably be:
#!/usr/bin/env python2
but as Python 3 should never install its executable under the name "python", you could also let it stay at:
#!/usr/bin/env python
instead.
-Dimitry
> On 1 Feb 2018, at