koobs added the comment:
@Serhiy
If by "type of code at the time of commit" you mean upstream python code,
msg250163 contains a link to what bits we replace in fcntlmodule.c and that "I
-> k" has always been the same.
--
__
koobs added the comment:
@Martin, weird, I'm still not seeing any files/dirs matching 'rc3'.
I have refreshed properly (cache-control 0 + empty cache) and still getting a
similar listing.
Fresh fetch output on the index URL:
Python-3.5.0rc1.tar.xz 11-Aug-2015 01:00
14
koobs added the comment:
Was a bug, now fixed (adjust title/resolution to compensate)
Thanks Berker!
--
resolution: not a bug -> fixed
title: Missing 3.5.0 RC3 tarballs (FTP) -> Missing 3.5.0 RC3 tarballs (FTP) on
Fastly nodes
___
Python t
koobs added the comment:
@Serhiy If anyone can provide me some test code (I dont know how to test it)
I'm happy to test it on 'unpatched' 2.7 and 3.5 ports
--
___
Python tracker
<http://bugs.pyt
koobs added the comment:
The attached patch courtesy of Jan Beich @ FreeBSD minimally mimics (in the
python version), the --ldflags output of the shell version of
python-config(.sh).
The ideal scenario of course would be to use the shell script across all
versions, as per revision
koobs added the comment:
To clarify, the bug remains in all branches including default, but only 3.4+
use the .sh script, leaving 3.3, 3.2, 2.7 using the python implementation.
--
versions: +Python 3.6
___
Python tracker
<http://bugs.python.
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue25809>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Re-open for 3.4 merge
--
status: closed -> open
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/issue25809>
___
___
Py
koobs added the comment:
Just to note, the koobs-freebsd-current buildbot is still failing on 3.4, which
reminded me to re-open
--
___
Python tracker
<http://bugs.python.org/issue25
koobs added the comment:
Thank you all. A+++, would collaborate again.
--
___
Python tracker
<http://bugs.python.org/issue25809>
___
___
Python-bugs-list mailin
New submission from koobs:
It appears all HTTPS/SSL tests that use the remote host svn.python.org are
failing.
All branch builds (tests) are currently broken on koobs-freebsd-current. I
think it's the only bot that has run builds post 24th December so far.
http://buildbot.python.or
Changes by koobs :
--
priority: normal -> high
___
Python tracker
<http://bugs.python.org/issue25950>
___
___
Python-bugs-list mailing list
Unsubscrib
koobs added the comment:
I'm here from (duplicate) issue 25950
--
nosy: +koobs
priority: normal -> high
___
Python tracker
<http://bugs.python.org
Changes by koobs :
--
keywords: +easy, needs review
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue20767>
___
___
Python-bugs-list mailin
Changes by koobs :
--
keywords: +easy
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue20397>
___
___
Python-bugs-list mailing list
Unsub
koobs added the comment:
setuptools and therefore pip are also affected by this
--
___
Python tracker
<http://bugs.python.org/issue20397>
___
___
Python-bug
koobs added the comment:
Can't / Shouldn't these be mocked?
--
___
Python tracker
<http://bugs.python.org/issue25940>
___
___
Python-bugs-list mailing
koobs added the comment:
As many branches as we can muster, ideally all, at least 3.4, 3.5 default and
2.7 please. Back porting is a massive pain, and downstream OS's want to retain
integrity of tests to ensure quality of Python in their respective ecosy
Changes by koobs :
--
keywords: +needs review
___
Python tracker
<http://bugs.python.org/issue20397>
___
___
Python-bugs-list mailing list
Unsubscribe:
koobs added the comment:
This needs review, commit, merge.
We've back-ported and committed these patches against all of our FreeBSD Python
ports (27,32,33,34,35)
https://svnweb.freebsd.org/ports?view=revision&revision=405569
--
stage: needs patch -> patch review
versions:
koobs added the comment:
Wow. *thank you* Georg and Martin :)
--
___
Python tracker
<http://bugs.python.org/issue25940>
___
___
Python-bugs-list mailing list
Unsub
koobs added the comment:
This issue is becoming increasingly important as FreeBSD 11.0-RELEASE time
nears.
What remains to be done/identified/answers here to make progress?
--
versions: +Python 2.7, Python 3.5
___
Python tracker
<h
koobs added the comment:
OH THANK YOU!
If possible, add Months or Quarter (Q1-4) for the EoL's, if those are defined,
would be great.
We @ FreeBSD/Python would like to proactively (as early as possible) set
DEPRECATED dates in our ports to ensure our users have ample time to upgra
koobs added the comment:
It appears this change broke all FreeBSD builders (9: gcc, 10/11: clang) for
the 2.7 branch with:
koobs-freebsd-current (clang 3.7.x)
cc -pthread -c -fno-strict-aliasing -OPT:Olimit=0 -g -O2 -g -O0 -Wall
-Wstrict-prototypes -I. -IInclude -I./Include
Changes by koobs :
--
resolution: fixed ->
___
Python tracker
<http://bugs.python.org/issue22847>
___
___
Python-bugs-list mailing list
Unsubscrib
koobs added the comment:
@Victor, it would be nice if this test could instead use/fake/mock what it
needs in the build directory, or is this not possible because it needs an
'actual' user/group context to work?
--
nosy: +koobs
___
Pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue26566>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
For what it's worth, we've been running with patch 0001 on FreeBSD's Python 3.4
port for 8 months with no issues [1].
It allows downstreams like us to easily customise what modules gets built, and
offers substantial flexibility and benefits for va
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue7352>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Still an issue on 2.7, 3.2, 3.3. Updating Versions to reflect this fact and
assist downstreams in backporting a forthcoming fix to those versions that
won't get it due to security-fix only branches.
See Also:
Issue: https://bugs.freebsd.org/bugzilla/show_bug.c
koobs added the comment:
+nosy doko on ned_deily's advice
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue7352>
___
___
Python-bugs-list m
koobs added the comment:
FWIW, see #23042
--
___
Python tracker
<http://bugs.python.org/issue22521>
___
___
Python-bugs-list mailing list
Unsubscribe:
koobs added the comment:
@Marc, if upstream 3.2.1 also has the issue, then that would mean the current
FreeBSD Python ports, which use --use-system-ffi and the security/libffi port,
currently at version 3.2.1 [1], can reproduce the issue.
I'm not aware of reports that they fail in
koobs added the comment:
See also:
Issue: https://github.com/atgreen/libffi/issues/180
Title: OSX/i386 build is broken in v3.2.1
--
___
Python tracker
<http://bugs.python.org/issue23
koobs added the comment:
@marc I took a look at the code upstream and it does indeed appear to be the
same. It was introduced in 3.1 [1].
I cant explain however how or why our Python ports work with libffi 3.2.1.
See msg238767 for a link to another similar (same?) issue, with failure of OSX
koobs added the comment:
+1
--
stage: -> needs patch
type: -> enhancement
versions: +Python 2.7, Python 3.4, Python 3.5
___
Python tracker
<http://bugs.python.org/i
koobs added the comment:
@haypo, yes, absolutely and no
We will backport to security-only branches ourselves.
--
___
Python tracker
<http://bugs.python.org/issue23
koobs added the comment:
@doko, as per the original report by Joel, the issue is:
* Reproducible with --enable-shared (most downstream OS's / packages use this)
Additionally:
* in the python script, not the shell script (by default used by < 3.4)
* Is reproducible in all branches (i
koobs added the comment:
@haypo, if you could take care of the change in default, 3.4 and 2.7, we can
backport the rest downstream. Thank you :)
@bapt, can you create a separate issue to cover the "create foo.so.X' symlink"
request, so python@ (freebsd team) can work to patch
koobs added the comment:
@RAW, can you attach a patch against the default branch please so we can move
this forward?
--
___
Python tracker
<http://bugs.python.org/issue17
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue23485>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue22117>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue23863>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Changes by koobs :
--
components: +Tests
keywords: +needs review
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue15745>
___
_
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue16287>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from koobs:
The following test failure is observable in koobs-freebsd9 and koobs-freebsd10
buildbots, on the 3.4 and 3.x branches.
==
FAIL: test_utime (test.test_os.StatAttributeTests
koobs added the comment:
After running the latest builds, it appears 3.x is now green, leaving 3.4
failing
--
___
Python tracker
<http://bugs.python.org/issue24
Changes by koobs :
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue27904>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
koobs added the comment:
Re-open and assign for regressions. Observed in all koobs-freebsd* buildbots
(9/10/11) and build types. Issue is in default branch (add version 3.7)
First failing test run:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Non-Debug%203.x/builds/110
koobs added the comment:
YES, finally. Thanks :)
--
nosy: +koobs
___
Python tracker
<http://bugs.python.org/issue28027>
___
___
Python-bugs-list mailing list
Unsub
201 - 250 of 250 matches
Mail list logo
