Graham Dumpleton added the comment:
These days I have no idea who is active on Django.
--
___
Python tracker
<https://bugs.python.org/issue46761>
___
___
Pytho
Graham Dumpleton added the comment:
Another example in Django, albeit in a test harness.
*
https://github.com/django/django/blob/7119f40c9881666b6f9b5cf7df09ee1d21cc8344/tests/urlpatterns_reverse/views.py#L65
--
___
Python tracker
<ht
Graham Dumpleton added the comment:
It is Django I would worry about and look at closely as they do stuff with
decorators on instance methods that uses partials.
https://github.com/django/django/blob/7119f40c9881666b6f9b5cf7df09ee1d21cc8344/django/utils/decorators.py#L43
```
def
Change by Graham Dumpleton :
--
nosy: +grahamd
___
Python tracker
<https://bugs.python.org/issue46846>
___
___
Python-bugs-list mailing list
Unsubscribe:
Graham Dumpleton added the comment:
I am still working through this and thinking about implications, but my first
impression is that the functools.partial object should provide an attribute
(property) __signature__ which yields the correct result.
When you think about it, any user who wants
Graham Dumpleton added the comment:
My vague recollection was that I identified some time back that partial()
didn't behave correctly regards introspection for some use case I was trying to
apply it to in the wrapt implementation. As a result I ended up creating my own
Graham Dumpleton added the comment:
Let me try and summarise what I do understand about this.
The existing wrapt code as written and its tests, work fine for Python 2.7 and
3.6-3.11. No special case handling is done in tests related to checking
annotations that I can remember.
The only
Graham Dumpleton added the comment:
I don't know about the comment "he has far more experience than I do with this
sort of object proxying wizardry". I read what you said and my brain melted. I
am getting too old for this and trying to understand how anything works anymore
tak
Graham Dumpleton added the comment:
Too much to grok right now.
There is already a convention for what a decorator wraps. It is __wrapped__.
https://github.com/python/cpython/blob/3405792b024e9c6b70c0d2355c55a23ac84e1e67/Lib/functools.py#L70
Don't use __func__ as that has other defined
New submission from Graham Inggs :
py_compile fails to read a list of filenames to be compiled from standard
input. This is a regression in 3.10.
example
files-to-compile.txt is a text file containing hello.py and goodbye.py on
separate lines. hello.py and goodbye.py must exist
Change by Graham Dumpleton :
--
nosy: +grahamd
___
Python tracker
<https://bugs.python.org/issue45319>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Graham Dumpleton :
The Python standard library has two effective implementations of helpers for
the ABCMeta class. A C implementation, and a pure Python version which is only
used if the C implementation isn't available (perhaps for PyPy).
* https://github.com/python
New submission from Graham Oliver :
Here is the text
https://docs.python.org/3.6/distutils/apiref.html#distutils.util.strtobool
Convert a string representation of truth to true (1) or false (0).
True values are y, yes, t, true, on and 1; false values are n, no, f, false,
off and 0. Raises
Graham Dumpleton added the comment:
For the record. Since virtualenv 20.0.0 (or there about) switched to the python
-m venv style virtual environment structure, the C API for embedding when using
a virtual environment is now completely broken on Windows. The same workaround
used on UNIX
Graham Dumpleton added the comment:
Just to make few things clear. It isn't mod_wsgi itself that relies on daemon
threads, it is going to be users WSGI applications (or the things they need)
that do.
As a concrete example of things that would stop working are monitoring systems
such as New
Graham Coster added the comment:
This may be a silly question, however, does SpooledTemporaryFile need to exist
at all?
>From some testing on macOS, SpooledTemporaryFile appeared to never have a
>performance advantage over OS file caching, but with max_size greater than
Graham Coster added the comment:
This may be a silly question, however, does SpooledTemporaryFile need to exist
at all?
>From some testing on macOS, SpooledTemporaryFile appeared to never have a
>performance advantage over OS file caching, but with max_size greater than
New submission from Graham Coster :
Hi there,
As demonstrated in the attached script, I found that a StopIteration exception
occurs once a SpooledTemporaryFile has been rolled over from memory to disk,
even though seek(0) had move the file position to the top of the file.
I had previously
Change by Graham Coster :
--
components: Library (Lib)
files: spooled-temp-file-does-not-seek-correctly-after-being-rolled.py
nosy: Gary Fernie, James Hennessy, graham.coster, inada.naoki, martin.panter,
nubirstein, r.david.murray, serhiy.storchaka, terry.reedy
priority: normal
Graham Dumpleton added the comment:
FWIW, this was occurring on macOS. Not been able to test on other platforms.
--
type: -> crash
___
Python tracker
<https://bugs.python.org/issu
New submission from Graham Dumpleton :
The code:
#include
int
main(int argc, char *argv[])
{
FILE *fp = NULL;
PyObject *co = NULL;
struct _node *n = NULL;
const char * filename = "/dev/null";
Py_Initialize();
fprintf(stderr, "START\n");
fp
Graham Wideman added the comment:
Demonstration:
print("x" + r' \' ' + "x") produces
x \' x
Where is this behavior _ever_ useful?
Or if there is some use case for this, how frequent is it compared to the
frequency of users expecting either that backslash
Graham Wideman added the comment:
Let us be clear here that this is NOT a case where the backslash escapes the
subsequent quote. If it WAS such a case, then the sequence \' would leave only
the quote in the output string. But it doesn't; it leaves the complete
2-character \' in the output
Change by Tim Graham :
--
pull_requests: +9424
___
Python tracker
<https://bugs.python.org/issue33899>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Tim Graham :
--
pull_requests: +9423
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issue31047>
___
___
Python-
Change by Tim Graham :
--
pull_requests: +9415
___
Python tracker
<https://bugs.python.org/issue33899>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Graham added the comment:
I think this caused a behavior change:
Before (Python 3.6.6):
>>> from os.path import abspath
>>> abspath('/abc/')
'C:\\abc'
After (Python 3.6.7):
>>> abspath('/abc/')
'C:\\abc\\'
This causes a test failure in Django's safe_join() fu
Tim Graham <timogra...@gmail.com> added the comment:
Okay, I created #32775.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
New submission from Tim Graham <timogra...@gmail.com>:
As discussed in issue30349#msg311684, fnmatch.translate() can produce a pattern
which emits a nested set warning:
>>> import fnmatch, re
>>> re.compile(fnmatch.translate('[[]foo]'))
__main__:1: FutureWarn
Tim Graham <timogra...@gmail.com> added the comment:
It might be worth adding part of the problematic regex to the warning message.
For Django's tests, I see an error like "FutureWarning: Possible nested set at
position 17 return re.compile(res).match". It took some effo
Tim Graham <timogra...@gmail.com> added the comment:
The last commit that added the deprecation warning needs to be added to the 3.7
branch.
--
nosy: +Tim.Graham
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Tim Graham <timogra...@gmail.com> added the comment:
This is appearing as a backwards incompatible change for Django because test
case class attributes are now evaluated at load time before setUpClass runs
(which initializes some things that those class attributes use). It's possible
to
Graham Dumpleton <graham.dumple...@gmail.com> added the comment:
FWIW, that atexit callbacks were not called for sub interpreters ever was a
pain point for mod_wsgi.
What mod_wsgi does is override the destruction sequence so that it will first
go through each sub interpreter when and sh
Tim Graham <timogra...@gmail.com> added the comment:
Perhaps the reason for the undeprecation could use some clarification. In a
Python 3 only world (where Django's master branch is), I believe there's still
usefulness for inspect.getfullargspec() -- see
https://github.com/django/
Tim Graham added the comment:
Thanks, I'm not sure what that means exactly but I added the note to
https://github.com/numpy/numpy/issues/9391. Perhaps a note in the Python
release notes is warranted?
--
___
Python tracker <rep...@bugs.python.
Tim Graham added the comment:
Hi, I observed an error while trying to install numpy after
6969eaf4682beb01bc95eeb14f5ce6c01312e297.
gcc: numpy/random/mtrand/mtrand.c
numpy/random/mtrand/mtrand.c: In function ‘__Pyx_PyCFunction_FastCall’:
numpy/random/mtrand/mtrand.c:44374:5: error: too
Tim Graham added the comment:
Does it seems likely that getfullargspec() will be deprecated after Python 2 is
EOL? Django is currently reimplementing getargspec():
https://github.com/django/django/blob/8ab7ce8558792f41637d6f87f2a8a117e169dd18/django/utils/inspect.py#L4-L24
A pull request
Tim Graham added the comment:
I sent a pull request for this issue's dependency (issue 27657) and added a
second commit there with this patch. A test added in the first commit
demonstrates that removing this code no longer results in the behavior change
described in msg238254
Tim Graham added the comment:
Based on discussion in issue 16932, I agree that reverting the parsing
decisions from issue 754016 (as Martin suggested in msg271719) seems
appropriate. I created a pull request that does that.
--
nosy: +Tim.Graham
Changes by Tim Graham <timogra...@gmail.com>:
--
pull_requests: +543
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27657>
___
_
Changes by Tim Graham <timogra...@gmail.com>:
--
pull_requests: +544
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue754016>
___
_
Changes by Tim Graham <timogra...@gmail.com>:
--
pull_requests: +542
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16932>
___
_
Graham Dumpleton added the comment:
@surajd Why aren't you using the Python S2I builders for OpenShift?
When you run anything under OpenShift, it will assign your project a UID which
any containers are forced to run under. The OpenShift containers include a
mechanism using a package call
Tim Graham added the comment:
Thanks Nick. Your suggestion does fix the issue for Django:
https://github.com/django/django/pull/7653.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Tim Graham added the comment:
Hi, this causes a regression in Django and I'm not sure if Django or cpython is
at fault. For a simple model that uses super() rather than super(Model self) in
save():
from django.db import models
class Model(models.Model):
def save(self, *args, **kwargs
Tim Graham added the comment:
Yes, that fixes the second test. Current warning (with stacklevel=3):
/home/tim/code/cpython/Lib/gettext.py:454: DeprecationWarning: Plural value
must be an integer, got 1.29
tmsg = self._catalog[(msgid1, self.plural(n))]
Possibly the stacklevel should instead
Tim Graham added the comment:
Thanks, that does fix that first test. There is one more that still fails:
$ python -Wall tests/runtests.py
humanize_tests.tests.HumanizeTests.test_i18n_intword
Testing against Django installed in '/home/tim/code/django/django' with up to 3
processes
Creating
Tim Graham added the comment:
Hi, this broke a couple tests with Django because it's passing number as a
float rather than an integer. For example:
==
ERROR: test_localized_formats
Tim Graham added the comment:
The patch is working well to identify warnings when running Django's test
suite. Thanks!
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Graham Dumpleton added the comment:
I always use PyImport_GetModuleDict(). So long as that isn't going away I
should be good.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Tim Graham added the comment:
As far as I can tell, this isn't an issue on Python 3. Can this be closed since
Python 2 is only receiving bug fixes now?
--
nosy: +Tim.Graham
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Tim Graham added the comment:
Based on the usage output, it looks like the subcommand is required, but I'm
not sure if there are cases where a subcommand could be optional. David, can
you advise?
usage: test_argparse.py [-h] command ...
--
nosy: +r.david.murray
Tim Graham added the comment:
Here's the patch if we make the change in Django instead:
https://github.com/cjerdonek/django/commit/9c8d162f3f616e9d9768659a06fcf27bb389214b
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Tim Graham added the comment:
Is there opposition to changing the default output as outlined in the first
comment? If so, then I think this ticket should be closed or retitled to
reflect the intent.
--
nosy: +Tim.Graham
___
Python tracker <
Tim Graham added the comment:
The behavior change is from #10424. Do you believe the new behavior is
incorrect?
--
nosy: +Tim.Graham
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Tim Graham:
As requested by Nick [0], this is a usability issue against CPython 3.6 to
provide a better chained TypeError in this case:
class _TokenType(tuple):
parent = None
def __getattr__(self, name):
new = _TokenType(self + (name,))
setattr(self
Tim Graham added the comment:
Yes, I found that Django needs an update to support that syntax in URLpatterns.
Thanks.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Tim Graham added the comment:
Eric, your patch was good enough to allow me to easily identify and fix all the
warnings in Django: https://github.com/django/django/pull/7254. Thanks!
--
___
Python tracker <rep...@bugs.python.org>
Tim Graham added the comment:
Adding an updated patch.
I guess the (?i:CaseInsensitive) syntax isn't merged yet? I tried it but it
didn't work. It might be premature to proceed with this deprecation if that
alternative isn't already present. Is there an issue for it?
--
Added file
Tim Graham added the comment:
I hope the message can be improved for Python 3.6 as the warnings I see when
running Django's test suite are rather useless to help find and fix the issues:
cpython/Lib/importlib/_bootstrap.py:205: DeprecationWarning: invalid escape
sequence '\:'
Grepping
Tim Graham added the comment:
Looks like we could remove the '^', but it doesn't resolve the deprecation
warnings. The inline flags in `pattern` still need to be moved before `_prefix`.
--
___
Python tracker <rep...@bugs.python.org>
Tim Graham added the comment:
And on further investigation, I'm not sure how to fix the deprecation warnings
in Django. We have a urlpattern like this:
url(r'^(?i)CaseInsensitive/(\w+)', empty_view, name="insensitive"),
The regex string r'^(?i)CaseInsensitive/(\w+)' is later s
Tim Graham added the comment:
Could we include the offending pattern in the deprecation message? I'm
attaching a proposed patch. With that patch I can more easily find the
offending pattern, whereas before I had no idea:
django/django/urls/resolvers.py:101: DeprecationWarning: Flags
New submission from Tim Graham:
Python 2.7:
>>> from email.header import Header
>>> Header(' ').encode()
''
Python 3.2+ (I didn't check older versions of Python 3):
>>> Header(' ').encode()
Traceback (most recent call last):
File "", line 1, in
F
Changes by Tim Graham <timogra...@gmail.com>:
--
nosy: +Tim.Graham
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27498>
___
_
Tim Graham added the comment:
I'll echo what Peter said and say that this breaks 5 tests in Django's test
suite which are checking error messages. If it stays, perhaps it could be added
to the release notes instead of just NEWS.
--
nosy: +Tim.Graham
Graham Dumpleton added the comment:
If someone is going to try and do anything in the area of better proxy object
support, I hope you will also look at all the work I have done on that before
for wrapt (https://github.com/GrahamDumpleton/wrapt).
Two related issue this has already found
Graham Dumpleton added the comment:
Double back slashes would possibly be an artefact of the some mess that happens
when logging out through the Apache error log.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Graham Dumpleton added the comment:
What I get in Apache for:
http://127.0.0.1:8000/a=тест
in Safari browser is:
'REQUEST_URI': '/a=%D1%82%D0%B5%D1%81%D1%82',
'PATH_INFO': '/a=\xc3\x91\\x82\xc3\x90\xc2\xb5\xc3\x91\\x81\xc3\x91\\x82',
Where as for curl see:
'REQUEST_URI': '/a=\xc3\x91\\x82
Graham Dumpleton added the comment:
This gets even weirder.
Gunicorn behaves same as wsgiref.
However, it turns out they both only show the unexpected result if using curl.
If you use safari they are both fine.
Waitress blows up altogether on it with an exception when you use curl as
client
Graham Dumpleton added the comment:
As I commented on Issue 26808, it actually looks to me like the QUERY_STRING is
processed fine and it is actually PATH_INFO that is not. I am confused at this
point. I hate dealing with these WSGI level details now
Graham Dumpleton added the comment:
There does appear to be something wrong with wsgiref, because with that
rewritten code you should for:
curl http://127.0.0.1:8000/тест
get:
pi:
/тест
qs:
{}
and for:
curl http://127.0.0.1:8000/?a=тест
get:
pi:
/
qs:
{'a': ['тест']}
The PATH_INFO case
Graham Dumpleton added the comment:
Your code should be written as:
res = """\
e:
{}
pi:
{}
qs:
{}
""".format(
pprint.pformat(e),
urllib.parse.unquote(e['PATH_INFO'].encode('Latin-1').decode('UTF-8')),
urllib.parse.parse_qs(urllib
Changes by Graham Dumpleton <graham.dumple...@gmail.com>:
--
nosy: +grahamd
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue23990>
___
Changes by Tim Graham <timogra...@gmail.com>:
--
nosy: +Tim.Graham
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25935>
___
_
Tim Graham added the comment:
Given the inactivity here, I guess the patch won't be applied before Python 3.2
is end-of-life so I'm going to close the ticket.
--
resolution: -> wont fix
status: open -> closed
___
Python tracke
Tim Graham added the comment:
Yes, when I have some time.
By the way, did you intentionally remove all the "Python 3.X" versions on the
issue?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.py
Tim Graham added the comment:
I had already proposed a test, see cookie-bracket-quotes-test.diff. What I
meant was that the fix and the test should be combined into a single patch.
--
___
Python tracker <rep...@bugs.python.org>
Tim Graham added the comment:
Could you please integrate my unit test into your patch?
You also need to sign the PSF Contributor Agreement:
https://www.python.org/psf/contrib/contrib-form/
--
___
Python tracker <rep...@bugs.python.org>
Tim Graham added the comment:
Sure, feel free to propose a patch.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25228>
___
___
Tim Graham added the comment:
It might be a case of issue22983. I'll try to look into the details and offer a
patch next week.
For what it's worth, there are other regressions in Python 3.2 cookie parsing
that makes the latest patch release (3.2.6) unusable with Django (issue22758),
so from
New submission from Tim Graham:
Regression in https://hg.python.org/cpython/rev/9e765e65e5cb (affects 2.7 and
3.2+), similar to issue22931 where inserting an invalid cookie value can cause
the rest of the cookie to be ignored. A test is attached, and here's a quick
demo:
Old:
>>
Tim Graham added the comment:
It's fine with me.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25137>
___
___
Python-bugs-list
Tim Graham added the comment:
We can use an alternate approach in Django, if appropriate:
https://github.com/django/django/pull/5294
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Tim Graham <timogra...@gmail.com>:
--
nosy: +Tim.Graham
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25137>
___
_
Changes by Tim Graham timogra...@gmail.com:
--
nosy: -Tim.Graham
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14373
___
___
Python-bugs-list
Graham Dumpleton added the comment:
That GC happens on an object in the wrong interpreter in this case is the
problem as it can result in used code execution against the wrong interpreter
context.
If you are saying this can happen anytime in the life of a sub interpreter and
not just
Graham Dumpleton added the comment:
If this issue with GC can't be addressed and sub interpreters isolated better,
then there is no point pursing then the idea that has been raised at the
language summit of giving each sub interpreter its own GIL and then provide
mechanisms to allow code
Graham Dumpleton added the comment:
Right now mod_wsgi is the main user of sub interpreters. I wasn't even aware of
this issue until Jesse found it. Thus in 7+ years, it never presented a problem
in practice, possibly because in mod_wsgi sub interpreters are only ever
destroyed on process
Tim Graham added the comment:
Thanks, that does resolve the issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14373
___
___
Python-bugs-list
Tim Graham added the comment:
This changed caused a problem in Django's test suite (bisected to
0d0989359bbb0).
File /home/tim/code/django/django/db/models/options.py, line 709, in
_populate_directed_relation_graph
all_models = self.apps.get_models(include_auto_created=True)
TypeError
New submission from Graham Oliver:
I noticed that when I created an issue in this Bug Tracjer all of the
associated emails were ending up in my gmail spam. '...in violation of Google's
recommended email sender guidelines.' An explanatory link sends me to
https://support.google.com/mail/answer
Tim Graham added the comment:
Unfortunately, the revert wasn't merged to the 2.7 branch until after the
release of 2.7.10. I guess this regression wouldn't be considered serious
enough to warrant a 2.7.11 soon, correct?
--
___
Python tracker rep
Graham Klyne added the comment:
Oops, (RETURN) submitted before comments done...
I think the example interactive python script is self-explanatory.
I know my version of Python is a bit out of date, but I couldn't see anything
in the issue list that indicated this problem had been seen
Graham Klyne added the comment:
I just tried the same on a Python 2.7.5 installation and it worked as expected
(no crash). So I now assume this is fixed. Sorry for the noise.
--
resolution: - out of date
status: open - closed
___
Python tracker
New submission from Graham Klyne:
conina:~ graham$ python
Python 2.7.3 (v2.7.3:70274d53c1dd, Apr 9 2012, 20:52:43)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type help, copyright, credits or license for more information.
dict({'a':'aa'},b='bb')
{'a': 'aa', 'b': 'bb'}
dict({'a':'aa
According to this https://docs.python.org/3.4/library/venv.html#module-venv
'Each virtual environment has its own Python binary (allowing creation of
environments with various Python versions)'
So how would I create a virtual environment using the venv module that has a
Python 2.7 binary?
tia
Graham Oliver added the comment:
See also
https://groups.google.com/d/msg/comp.lang.python/BUmyc_hzAsA/Nx5QgT1gzYEJ
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24356
On Tuesday, 2 June 2015 09:43:37 UTC+12, Carl Meyer wrote:
On 06/01/2015 03:33 PM, orotau wrote:
According to this
https://docs.python.org/3.4/library/venv.html#module-venv 'Each
virtual environment has its own Python binary (allowing creation of
environments with various Python
New submission from Graham Oliver:
See my question here
https://groups.google.com/forum/#!topic/comp.lang.python/BUmyc_hzAsA
In particular Carl Meyer's response
https://groups.google.com/d/msg/comp.lang.python/BUmyc_hzAsA/-cT-N-g_LL4J
I am not sure what is possible with venv but I would suggest
1 - 100 of 563 matches
Mail list logo
