Alexis Metaireau added the comment:
Same here, cannot reproduce the issue. I wasn't able to reproduce it even
before Tarek's commit so I suppose his commit didnt changed anything regarding
this hash problem.
Antoine & Tarek, does the attached additional test reproduces the
Alexis Metaireau added the comment:
I'm +1 on applying this patch as well. Removing files in the tmp directory is
far better than letting the OS doing so.
--
___
Python tracker
<http://bugs.python.org/is
Alexis Metaireau added the comment:
Carl, I believe that's this one: http://wiki.python.org/moin/UsecasesOfDevelop
--
___
Python tracker
<http://bugs.python.org/i
New submission from Alexis Metaireau :
The example section of the timeit documentation still refers to "timeit.py",
and isn't using the "python -m timeit" syntax used above.
http://docs.python.org/library/timeit.html#examples
I'm not sure when and if the timeit.p
Changes by Alexis Metaireau :
--
nosy: +Boris.FELD
___
Python tracker
<http://bugs.python.org/issue12697>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
title: timeiot documention still refers to the timeit.py script -> timeit
documention still refers to the timeit.py script
___
Python tracker
<http://bugs.python.org/issu
Alexis Metaireau added the comment:
Maybe could it be useful to specify in the documentation that getlocale() is
not intended to be used to get information about what is the locale of the
system?
It's not explained currently and thus it's a bit weird to have getlocale
returning (
Alexis Metaireau added the comment:
I see two different things here:
1) the fact that getlocale() doesn't return (None, None) on some python
versions
2) the fact that having it returning (None, None) by default is a bit
misleading as users may think that getlocale() is tied to enviro
New submission from Alexis Metaireau :
The documentation about locale.getlocale() doesn't talk about the fact that the
locale isn't read from the system locale. Thus, it seemed strange to have
locale.getlocale() returning (None, None).
As it seems to be the expected behaviour, it se
Alexis Metaireau added the comment:
_run_setuptools_install is only intended to support setuptools setup.py,
converting .egg-info to .dist-info, internally. IMO, you should not care about
the differences between setuptools/distutils1/setuptools at this level, as it
should be taken care at
Alexis Metaireau added the comment:
IOW, in my opinion, support for setuptools develop command is not needed in
packaging core, and still be taken care directly be the users wanting to run
python setup.py develop: I don't see any reason to make it avaible on the
s
Alexis Metaireau added the comment:
Yep, packaging is not keeping the .egginfo directories, or at least does not
plan to keep them (It should be the case currently but I haven't checked
recently) in the upcoming release, so I would go on removing support for
setuptools' develop co
Alexis Metaireau added the comment:
On 08/18/2011 05:54 PM, higery wrote:
> Then do you also mean support that for setuptools install is also not
> necessary in packaging core?
setuptools install is only supported in packaging because it's a widely
used thing, and many python di
Alexis Metaireau added the comment:
Thanks Rémy,
About testing, I would go for modules with errors in it and check that when
imported trough this function it does what it is supposed to do.
IOW:
1. Create a test python module with errors in their definition (Throw an
exception would do
Alexis Metaireau added the comment:
Please, can you be a bit more precise about the missing features ? I'll be glad
to cover them.
--
___
Python tracker
<http://bugs.python.org/i
Alexis Metaireau added the comment:
Yes, all the functions are covered. By the way, I've covered all the functions
based on the pypi source code, not on the wiki.
I'll update the wiki page with some examples soon :)
--
___
Python trac
Alexis Metaireau added the comment:
Some nitpicks:
In mirrors.get_server_key, the documentation is not up to date with your last
changes (raises an error if there is a problem instead of returning None)
You do use the name 'package' while talking about distributions or projects.
Alexis Metaireau added the comment:
Antoine Pitrou on #python-dev made interesting remarks about the validation:
16:19 < __ap__> hmm the way the patch does validation is bogus
16:22 < __ap__> because it opens the URL a first time, validates it,
then opens it a second time with url
Alexis Metaireau added the comment:
This raises a concern about python specific python implementations
dependencies.
We probably could extend PEP 345 in order to support things such as
'platform.python_implementation == "cpython"'.
--
__
Alexis Metaireau added the comment:
On 29/04/2011 18:20, Daniel Holth wrote:
> New in version 2.6.
Yep that's it. We would need to backport it in the python2 port of
packaging (namely distutils2), but it would do the trick.
I just started a discussion about that on the fellow
Alexis Metaireau added the comment:
The MANIFEST.in is definitely gone in distutils2.
Can we close that? (don't have the rights to do so ‑ it can be handy on
distutils2 bugs)
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/i
Alexis Metaireau added the comment:
Has the patch been applied on distutils(1/2) ?
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue5243>
___
___
Alexis Metaireau added the comment:
I've applied the patch on distutils2. This can now be closed.
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/iss
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue6087>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexis Metaireau added the comment:
Have the patch been applied ? (the state is still open since last message)
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue2
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue7546>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexis Metaireau added the comment:
Still, the extra_path argument exists and can be used, it's worth to
have it documented somewhere, especially if someone have done it.
That's also true that apiref.rst is outdated in d2, and will need a
comple
Changes by Alexis Metaireau :
--
components: -Distutils2
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue1083299>
___
___
Python-bugs-list mailin
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue1597850>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue1294032>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue1092365>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue1635363>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue103>
___
___
Python-bugs-list mailing list
Unsubscribe:
Alexis Metaireau added the comment:
yeah, thanks for that !
--
___
Python tracker
<http://bugs.python.org/issue11213>
___
___
Python-bugs-list mailing list
Unsub
Alexis Metaireau added the comment:
Hi,
I was more thinking about something like: if the license is specified in the
"License" metadata, then check that it's not a well known license (which can
and must be provided by the classifiers instead).
At the end, the code you
Alexis Metaireau added the comment:
That's almost what the PEP says, or at least what I understand of it.
The platform and license fields should be used only if no matching classifier
exists for them.
--
___
Python tracker
<http://bugs.py
Changes by Alexis Metaireau :
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue14317>
___
___
Python-bugs-
Alexis Metaireau added the comment:
The APIs of distutils2 have changed. the "index" module is now named "pypi".
So, doing something like::
>>> from distutils2.pypi.simple import Crawler
should work.
--
Alexis Metaireau added the comment:
Hey, is there any news on this bug? Berker?
--
___
Python tracker
<http://bugs.python.org/issue11880>
___
___
Python-bug
Alexis Metaireau added the comment:
Thanks for reporting this Preston,
Could you be a bit more precise on this one? What is the input you are giving
(in the dist-info) and what is not being done? (what's the expected output and
what's what you have as a result
Alexis Metaireau added the comment:
Agreed on this one. That would avoid to have a new syntax for this
case, which seems to be very common.
--
___
Python tracker
<http://bugs.python.org/issue5
New submission from Alexis Metaireau :
I need to do some general cleanup on packaging/d2, and especially on this bit.
Currently, the implementation is way too complicated for what it does.
--
assignee: alexis
components: Distutils2
messages: 155903
nosy: alexis, tarek
priority: normal
Alexis Metaireau added the comment:
It is supposed to work already, but I'm not sure this is tested or complete.
I'll have a closer look on this. +1 on the general idea.
--
assignee: eric.araujo -> alexis
___
Python tracker
<http:/
Alexis Metaireau added the comment:
If no MD5 checksum is present on the crawled simple index, then we don't have
to check them. This means we introduce a potential security hole here (md5
checksums were added for a reason).
What could be done is to explicitely don't check them i
Changes by Alexis Metaireau :
--
dependencies: +Requirements are not properly copied into metatdata of dist-info
___
Python tracker
<http://bugs.python.org/issue14
Changes by Alexis Metaireau :
--
dependencies: -Requirements are not properly copied into metatdata of dist-info
___
Python tracker
<http://bugs.python.org/issue14
Alexis Metaireau added the comment:
Thanks for reporting this, Jan-Jaap,
I've marked this issue as easy, it's mostly a matter of looking at the passed
parameter and outputing the list in the generated file, respecting the PEP 345
format (http://www.python.org/dev/peps/pep-0345
Alexis Metaireau added the comment:
Right, I'll go for this then.
--
___
Python tracker
<http://bugs.python.org/issue14280>
___
___
Python-bugs-list m
Alexis Metaireau added the comment:
Oh, thanks for clarifying this.
I'll have a look at what the blockers are on this. I'm wondering if
"local files" can be considered a simple index or not. If not, we can
add another PyPI reader, which wo
Alexis Metaireau added the comment:
The supposed way to work, for OS packagers, is to ship this
sysconfig.cfg thing.
I'm not sure we should rely on a customized site-local configuration,
without defining any standard way of doing this (IOW: what are we
looking for in the site-local c
Alexis Metaireau added the comment:
Oh, a potential way to avoid this would be to check that the metadata
have the python 3 trove classifier in it.
We could also add a way to force the installation even if the right
classifier is not present with a special flag passed to the command
line
Alexis Metaireau added the comment:
Good catch,
One solution would be to have the pysetup script name suffixed by the
version of python is comes with. For instance, for python 3.3 it would
be "pysetup3.3" (that's how it is atm).
This means that "pysetup" would poin
Alexis Metaireau added the comment:
While I kind of agree with you, this field is proposed by the PEP 345
and had been approved as it is. It seems probably better to stick with
what's defined there mainly because any change to the PEP is a heavy
process and we won't have time to go
New submission from Alexis Metaireau :
The packaging tutorial currently talks about "pysetup run install_dist" and
"pysetup install" which aren't doing the same thing: one fetches the
dependencies while the other doesn't.
This should be stated clearly.
--
New submission from Alexis Metaireau :
The "packaging.install" module doesn't have a clear API defined and it's doing
a lot of indirections between all the functions to get metadata, fetch the
dependencies and install what's need to be installed.
We might be a
Alexis Metaireau added the comment:
Did someone changed anything in the codebase regarding this (or did it solved
itself magically?)
--
___
Python tracker
<http://bugs.python.org/issue12
Alexis Metaireau added the comment:
That would be helpful yep. I can add this in the docs if you've not done it
already.
--
___
Python tracker
<http://bugs.python.org/is
Alexis Metaireau added the comment:
I'm +1 on this. Having an "install" command, on a distribution, makes more
sense than having an "install_dist" one, because of course the object is a
distribution!
--
___
Python tracker
Changes by Alexis Metaireau :
--
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue13160>
___
___
Python-bugs-list mailing list
Unsubscri
Alexis Metaireau added the comment:
I think it could be helpful to have this work at least somewhere so we can work
on top of it. For instance if someone wants to do changes in the documentation,
then only thing it would do now would be to cause potential merge conflicts.
I'm okay to
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue14899>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Alexis Metaireau :
PyPI is the name of a particular index, whereas "index" is a generic term.
So ISTM that it would be better to use the latter, semantically-wise.
--
assignee: alexis
components: Distutils2
messages: 162027
nosy: alexis, tarek
priori
Alexis Metaireau added the comment:
We are all calling these indexes quite everywhere. We are talking about
a Python Package Index and even the mirroring infrastructure is talking
about indexes. Because that's under the "packaging" namespace, it's
kind of obvious that thi
Alexis Metaireau added the comment:
The problem is that PyPI isn't a good name since it's the name of ONE
index.
Westley, do you have any other idea?
Otherwise, I think we should stick to "index", which is a good name for
something that's named "index" q
Alexis Metaireau added the comment:
> Alexis, you introduced the client/crawler naming after reading some book;
> what do you think now?
Making the distinction between a crawler and a client is probably not a
good idea since it introduces two concepts instead of one simple one.
W
Alexis Metaireau added the comment:
Attaching a work in progress file which intend to replace the current
install.py file. The implementation isn't finished yet but the overall design
is here.
It comes with four classes:
- Installer which manages the overall installation procedur
Changes by Alexis Metaireau :
--
nosy: -alexis
___
Python tracker
<http://bugs.python.org/issue3754>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue1596321>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue8190>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Alexis Metaireau :
--
nosy: +alexis
___
Python tracker
<http://bugs.python.org/issue4908>
___
___
Python-bugs-list mailing list
Unsubscribe:
70 matches
Mail list logo